Token导航 LogoToken导航TokenDH.com
研究检索执行命令github未标认证来源可访问许可证需确认审计提醒

opened-daily-newsletter-writer开设每日通讯作家

Agent Skill

opened-daily-newsletter-writer 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

447

周安装

19

GitHub Stars

4

下载量

157
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:opened-daily-newsletter-writer(开设每日通讯作家)
来源仓库:https://github.com/cdeistopened/opened-vault
仓库路径:skills/opened-daily-newsletter-writer
安装命令:
npx skills add https://github.com/cdeistopened/opened-vault --skill opened-daily-newsletter-writer
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/cdeistopened/opened-vault --skill opened-daily-newsletter-writer

简介

opened-daily-newsletter-writer 用于查找、检索和筛选相关信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词、任务场景或来源线索快速定位候选结果。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装使用。
  • 安装前需确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

OpenEd Daily Newsletter Writer

Creates Monday-Thursday daily newsletters (500-800 words) that challenge standardized education with contrarian angles and authentic voice.

Not for: Friday Weekly digests (use weekly-newsletter-workflow), social media only, or blog posts.


Required References

For full newsletters (Phase 3+): Load references/opening-letter-patterns.md before writing the opening letter. It contains 12+ real examples organized by pattern type (Milestone, Contrarian, Story, Humorous, Anxiety, Timely) plus full segment examples showing the Substance→Take rhythm in action. These are more detailed than the quick examples below and produce better results.

For segment techniques: references/pirate-wires-segment-techniques.md has 7 techniques with full before/after examples and TTT application tables. Load when struggling with a specific segment.

Voice Priming (Read First)

Before writing, read these examples. They're from Charlie's actual published OpenEd Daily newsletters. Internalize the rhythm - the sentence length variation, the parenthetical asides, the "I just noticed this" energy. Then write in this voice.


Example 1: Data vs. Headlines (Calling Out the Obvious)

Homeschool students outperform public school peers in science, math, history, English, the ACT, and the SAT. He's citing data from HSLDA's 2009 Progress Report, a nationwide study of nearly 12,000 homeschooled students conducted by Dr. Brian D. Ray. That study found homeschoolers scoring 34-39 percentile points above national averages. More than 78% of peer-reviewed studies since have shown the same pattern, and the advantage holds regardless of family income or parental education level. I mean, this isn't obscure research. It's been replicated for decades. So why doesn't the coverage match the data? (Rhetorical question. We all know why.)

What works here: Long factual sentence, then short punch. The "I mean" before stating what should be obvious. Parenthetical that says what everyone's thinking.


Example 2: Institutional Critique (Gatto Deep Dive)

In 1991, John Taylor Gatto did something that shocked the education world. Just months after being named New York State Teacher of the Year, he quit. Not quietly into retirement, but loudly, with a scathing *Wall Street Journal* op-ed announcing: "I can't teach this way any longer. If you hear of a job where I don't have to hurt kids to make a living, let me know." "Schooling is a form of adoption," Gatto later wrote. "You give your kid away at his most plastic years to a group of strangers."

What works here: Narrative setup with specific detail (1991, NYS Teacher of the Year). The quote does the heavy lifting - no need to editorialize.


Example 3: The Reframe (Design Over Delivery)

There's a question parents keep asking about online learning: "Is it good or bad?" Wrong question. Michael Horn took two online courses at Harvard. Same platform. Same student. Same year. One was brilliant - compelling storylines, short bursts of text, instructor engagement when he needed it. The other was a wall of dense paragraphs with no support. He could barely stay awake. The variable wasn't "online." It was design.

What works here: Sets up the common framing, kills it with two words ("Wrong question."), then proves it with a specific anecdote. The last line is a tight reframe.


Example 4: Tool Segment with Personality (Printers)

You're probably hemorrhaging money on printer ink right now. Most homeschool families are. The math is brutal: that $50 inkjet printer costs $500 a year in cartridges. Meanwhile, an ink tank printer costs more upfront but pennies per page. Do the math over three years and the "expensive" printer saves you hundreds. The rule: never buy cartridges again. Ink tanks or laser. Everything else is a trap.

What works here: Direct address ("You're probably..."), concrete math, ends with a firm opinion stated as fact. No hedging, no "consider" or "might want to."


Example 5: Opening Letter with Hook

There's a question hiding under a lot of today's education coverage: Can parents be trusted? Every time a big outlet runs a story about a homeschooled student who "fell behind," the implication is the same: when families are left to themselves, kids get shortchanged. These pieces follow a familiar pattern. Spotlight an anecdote. Quietly generalize it into a warning label. Skip the part that would actually help readers think clearly: what the broader data says.

What works here: Opens with a quiet observation, escalates to the bold question, then dissects the media pattern. Confident, analytical, not angry.


Voice Patterns (Derived from Charlie's Writing)

Rhythm:

  • Long factual/narrative sentences (30-40 words) followed by short punches (4-8 words)
  • "I mean, obviously..." before stating what should be self-evident
  • Parenthetical asides that say what everyone's thinking: "(Rhetorical question. We all know why.)"
  • Let the quote do the work. Don't editorialize after a strong quote.

Tone:

  • Curious > Accusatory - Notice gaps, don't blame
  • Confident - State opinions as observations, not suggestions
  • Specific - Real names, real numbers, real sources
  • "I just noticed this" energy - Write like you're thinking in real time, not presenting a finished argument

Anti-patterns:

  • Staccato fragments: "100,000 tutors. 90+ languages. Results." → Write flowing sentences
  • ALL correlative constructions: "X isn't just Y - it's Z" / "doesn't mean X. It means Y." → Find another way. Just state the positive claim.
  • Performative emotional narration: "stuck with me" / "hit me hard" → Present, don't narrate your feelings about it
  • Scaffolding: "A few things that jumped out" / "Here's what's interesting" → Cut. Go straight to content.
  • Fake questions: "What if schools actually taught kids to think?" → Just tell them
  • Hedging: "might," "could," "possibly" → Be confident
  • Over-editorializing after quotes → Let the quote land
  • Dramatic inflation: "unthinkable" / "shocking" / "game-changing" → Understated, detached, let data do the work

Content Workflow Order

Full content drop order of operations:

  1. Draft social media assets (use newsletter-to-social)
  2. Publish blog post on Webflow
  3. Share social media with blog link where appropriate
  4. Newsletter last (use hubspot-email-draft skill)

The newsletter often links to the blog post and social content, so it goes last.


Newsletter Workflow

Phase 1: Source + Format      → Source_Material.md (identify social formats FIRST)
Phase 2: Angles + Checkpoint  → Checkpoint_1.md (USER APPROVAL REQUIRED)
Phase 3: Newsletter Writing   → Newsletter_DRAFT.md
Phase 4: Social Spin-offs     → Social posts from newsletter content
Phase 5: Subject Lines        → Spawn `newsletter-subject-lines` sub-agent (REQUIRED)
Phase 6: QA & Archive         → Newsletter_FINAL.md
Phase 7: HubSpot Draft        → hubspot-email-draft skill → one-click publish

Key insight: Identify which snippets have natural social formats BEFORE writing the newsletter. Social constraints produce tighter angles.


Phase 1: Content Curation

Pull Staging Content

Primary source: Studio/Newsletter Studio/staging/ — curated articles with YAML frontmatter (title, source, url, nugget, status: staged). These are pre-scored articles ready for newsletter use.

Podcast database: Published Content/Podcasts/ — 131 episodes with full transcripts. Search for relevant guest quotes, episode links to reference. When a staged article connects to a past episode, link back to it.

Primary source rule: When possible, link to the original source (e.g., 50can.org for 50CAN's survey) rather than secondary coverage (e.g., The 74's write-up). Give credit to the people doing the work.

Segment Types

  • THOUGHT: A take. An observation. The "I wish I'd thought of that" moment. Named individuals + direct quotes work best. The reader should come away with a reframe or a new way to see something familiar. A THOUGHT is an idea, not data. If it reads like a report, it's a TREND.
  • TREND: Data, movements, what's happening. Numbers, surveys, policy shifts, institutional changes. A TREND can have a take attached to it, but the core is evidence of something changing.
  • TOOL: A practical resource readers can use. Must be concrete - a product, a technique, a tax strategy, a program. If a parent can't act on it, it's not a TOOL.

Standard order: THOUGHT → TREND → TOOL (always this order)

Optional 4th segment: A short bonus segment after the main three. Proven patterns:

  • Word of the Day - A term from classical education, learning science, or alternative education. Format: *noun/verb* - definition, etymology, why it matters. Can include an image. Ties the issue together thematically without adding another full segment.
  • Bonus link - A short pointer to something worth reading, with 2-3 sentences of context.

Each segment: ~100-150 words.

Orthogonality rule: If two segments feel like they're telling the same story, one of them needs to change. THOUGHT = why something is broken. TREND = what's happening. TOOL = what you can do. If TREND and TOOL overlap (e.g., both about the same product), swap the TREND for something genuinely different - even from a different topic area.

Sourcing Rules

TOOLs:

  • Primary: Tool Database
  • Must have concrete detail (stats, quotes, specific features)

THOUGHTs:

  • Named individuals + direct quotes work best
  • "Happy, not Fortune 500" > generic philosophy

TRENDs:

  • Vary topics — avoid repeating "enrollment surge" every issue
  • Look for: learning science, tech/AI, parent behavior, international comparisons
  • Specific numbers + authoritative sources

Avoid:

  • Heavy ESA/school choice policy content
  • Federal tax programs
  • State-specific policy details (unless story transcends the state)

Create Working Folder

mkdir "Studio/Newsletter Studio/[YYYY-MM-DD] - [Brief Theme]/"

Create Source_Material.md with:

  • URLs and key quotes
  • For each piece: what's the core insight? (one sentence)
  • Format fit: X one-liner, Instagram carousel, LinkedIn story, or newsletter segment?

Social-first check: If a snippet has an obvious social format, note it. You may draft that version first - social constraints often reveal the strongest angle.

Snippet TypeNatural Format
Single stat + interpretationX one-liner
Comparison/contrastInstagram carousel
Transformation arcLinkedIn story
Counterintuitive claimX paradox

Phase 2: Angle Development

🛑 CHECKPOINT 1 - Do not proceed to Phase 3 without user approval.

Create Checkpoint_1_Angles.md with:

For Each Segment (3-4 angle options)

Ask yourself:

  • What's the contrarian but obviously true take?
  • How does this challenge standardized education?
  • Would Sarah (our One True Fan) forward this?

Subject Lines (10 options, 8-10 words max)

  • 3-4 Curiosity-Based
  • 3-4 Specificity-Based
  • 2-3 Hybrid

Preview Text

Formula: [Specific claim]. [Context]. [Gap/tension]. PLUS: [bonus]

Example: "Students who test themselves retain 80% more. Researchers have known this since the 1900s. Schools still don't do it. PLUS: an app that does."

Checkpoint Template

# Checkpoint 1: Angles & Structure - [Date]

## SUBJECT LINE OPTIONS
[Organize by type: Curiosity, Specificity, Hybrid]

## PREVIEW TEXT
[Draft]

## SEGMENT 1: [TITLE] (Type)
**Source:** [URL]
**Angle Options:** [3-4 options]
**Recommended:** [Which and why]

## SEGMENT 2: [TITLE] (Type)
[Same format]

## SEGMENT 3: [TITLE] (Type)
[Same format]

## ORTHOGONALITY CHECK
- [ ] Thought and Trend are distinct (not repetitive)
- [ ] Aligns with OpenEd beliefs
- [ ] Would Sarah forward this?

User Feedback Notation

  • *** = preferred choice
  • <> = extrapolate contextually
  • {question} = answer directly
  • ~~text~~ = delete

Phase 3: Newsletter Writing

Create Newsletter_DRAFT.md after Checkpoint 1 approval.

Opening Letter (~100-150 words)

For more examples, load: references/opening-letter-patterns.md

Structure:

  1. Greeting: "Greetings Eddies!", "Welcome Eddies!", or "Greetings!"
  2. Hook: Story, startling statistic, contrarian question, or community milestone
  3. Pivot: Connect to "opening up education" or today's specific value
  4. Tease: Mention what's coming without summarizing
  5. Sign-off: "Let's dive in."

Quick Examples (by hook type):

Milestone/Community:

Greetings Eddies! It just came to my attention that the OpenEd Daily hit a new milestone: 20,000 subscribers! Rather than resting on our laurels, we take this as a sign of the growing appetite for trustworthy content related to the opening up of education. Onward & upward,

Contrarian/Data:

Greetings! An education expert recently published something that's making a lot of parents nervous. Chad Aldeman looked at data from 250,000 kids across 1,400 schools and concluded: if your child isn't reading on track by kindergarten, don't wait. Act fast. The data sounds brutal, but is he interpreting it correctly? Let's dive in.

Story-Driven:

Greetings! Ken Danford had spent six years teaching eighth-grade U.S. history when a colleague handed him The Teenage Liberation Handbook. In it, he found case studies of teens who left school and turned out... fine! That was 1996. He quit his job, and ever since, he's been running North Star—a physical community center where teens can legally homeschool. Let's dive in.

Personal/Humorous:

Greetings Eddies! Did you know that OpenEd is on Instagram? While I may not be able to compete with top-tier influencer homeschool moms, we're always looking for new ways to share the message (even if that means putting on a smelly latex horse mask and A/B testing silly gimmicks until we find something that sticks).

Parental Anxiety:

Greetings! A few months ago, an OpenEd parent reached out with a familiar dilemma. Her student had done 9th grade on the diploma path, but she was switching to non-diploma-seeking status. Yet she still had concerns: "I worry a lot about not following the traditional path." Society has pushed one linear path for so long. Except that path is just one among many. Let's dive in.

Newsletter Structure

# Newsletter Draft - YYYY-MM-DD (Day)

**SUBJECT:** [From Checkpoint 1]
**PREVIEW:** [From Checkpoint 1]

---

Greetings Eddies!

[Opening Letter - 100-150 words]

– Charlie (the OpenEd newsletter guy)

---

**THOUGHT** -- [Skimmable TLDR header that gives you the punchline]
**TREND** -- [Skimmable TLDR header]
**TOOL** -- [Skimmable TLDR header]

---

# [DESCRIPTIVE TITLE - ALL CAPS]

[100-150 words]

---

# [DESCRIPTIVE TITLE - ALL CAPS]

[100-150 words]

---

# [DESCRIPTIVE TITLE - ALL CAPS]

[100-150 words]

---

That's all for today!

– Charlie (the OpenEd newsletter guy)

P.S. [Optional announcement or link to podcast/blog]

Index at top: After the opening letter, include a 3-line index with bold THOUGHT / TREND / TOOL labels followed by -- and a one-sentence TLDR. Rules:

  • One sentence max per line - if it needs two, it's too long
  • Keep each line under ~65 characters so it fits on one line in the email client
  • In markdown, separate lines with \ (backslash line break), NOT blank lines. This renders as <br> in HTML - a soft line break within one paragraph block, not three separate paragraphs with spacing between them
  • The three lines should feel like a tight visual unit, not three disconnected items

Section headers: Use descriptive # TITLE (H1 headers, ALL CAPS). Do NOT include THOUGHT/TREND/TOOL in the section title. The index handles the labeling; the headers stand alone.

This format ports directly into HubSpot via the hubspot-email-draft skill.

Format Requirements

  • ❌ NO EMOJIS (non-negotiable)
  • ✅ H1 headers for segments (# not ##)
  • Bold for key quotes/stats
  • ✅ Hyperlinks throughout (not just at ends)
  • --- between sections
  • ✅ 500-800 words total
  • ✅ Standalone CTA links ("Read the Full Guide", "Watch the Episode") get centered formatting in HubSpot - flag these in the markdown so they're not left-aligned when pushed

Hyperlinking Rules

When provided a link, always hyperlink it in the body of the text (never at the end). Link the main action or subject using only 2-3 key words max.

Good: "A new MIT study claims LLM users underperform..." Good: "Ken Danford has been running North Star since 1996..." Bad: "A new MIT study claims LLM users underperform. (Link)" Bad: "A new MIT study claims LLM users consistently underperform on cognitive tests"

When multiple sources are provided with body text to reference, hyperlink ALL links where the referenced content is used in the newsletter. Don't let any provided link go unhyperlinked.


Writing Techniques (Use These)

The anti-patterns tell you what NOT to do. These techniques tell you what TO do instead. They're derived from Pirate Wires and Charlie's best published segments.

Technique 1: Calling Out the Obvious

State what everyone secretly knows but nobody says out loud. The power comes from saying the quiet part plainly.

Pattern: [Obvious observation everyone avoids] → [Why it's obvious] → [Short, dry conclusion]

Example (from published newsletter):

Homeschool students outperform public school peers in science, math, history, English, the ACT, and the SAT. He's citing data from HSLDA's 2009 Progress Report... More than 78% of peer-reviewed studies since have shown the same pattern. I mean, this isn't obscure research. It's been replicated for decades. So why doesn't the coverage match the data? (Rhetorical question. We all know why.)

Technique 2: Setup and Punch

Build context with specifics, then land on a short reframe that flips the framing.

Pattern: [Detailed setup with names/numbers/context] → [2-8 word punch line]

Example:

Michael Horn took two online courses at Harvard. Same platform. Same student. Same year. One was brilliant - compelling storylines, short bursts of text, instructor engagement when he needed it. The other was a wall of dense paragraphs with no support. The variable wasn't "online." It was design.

Technique 3: Substance→Take Rhythm

The core engine of every good segment. Alternate between factual substance (data, quotes, specifics) and editorial takes (interpretation, reframes). Never stack multiple takes without substance between them, and never dump substance without a take to land it.

Pattern: Substance → Take → Substance → Take → (repeat)

Example (from published newsletter):

[SUBSTANCE] A new CRPE report called "The Big Blur" looked at 47 school districts experimenting with work-based learning. [TAKE] The results shouldn't surprise anyone who's been paying attention. [SUBSTANCE] Students in structured programs were 12% more likely to graduate and earned 17% more in their first five years. Meanwhile, only 5% of US high schoolers currently participate. [TAKE] So 95% of students are missing the thing that demonstrably works. The word for that is "policy failure," but nobody in education policy calls it that.

Technique 4: Let the Quote Do the Work

When you have a strong quote, don't editorialize after it. Set it up with context, drop it, move on. The quote IS the point.

Bad: Gretchen said something profound: "We wanted our children to have character. We didn't want them to be characters." This powerful statement really captures the essence of her philosophy.

Good: "We wanted our children to have character," Gretchen said. "We didn't want them to be characters."

Voice Reminders

  • Tone: Curious > Accusatory — Notice gaps, don't blame. Let readers draw conclusions.
  • Tone: Detached > Dramatic — Understated, ironic, Pirate Wires energy. The data speaks. You don't need to inflate it.
  • Tone: Watch the salt level — Institutional critique is fine but don't go so hard that it alienates the audience. "The College Board is a $1.2B nonprofit" lands. Deep dives into eugenics origins may not. Let the reader draw their own conclusions from the facts.
  • Tone: Above the fray — On political topics, present facts without partisan framing. We notice trends; we don't take sides.
  • Bad: "Schools prioritize fun over learning. Educators are failing our kids."
  • Good: "Skycak's point: schools are optimizing for a lot of things at once. Maximizing learning is one of them."
  • Load ghostwriter skill for banned words and voice transformation. Load voice-dna (root-level skill) for Charlie's personal voice patterns. The #1 tell: correlative constructions in ALL their forms.

Segment Titles

  • Format: # DESCRIPTIVE TITLE (H1 header, ALL CAPS)
  • The words THOUGHT, TREND, and TOOL do NOT appear in the title. The index at the top handles labeling.
  • Title: 1-10 words, ALL CAPS, gives the reader the TLDR or punchline from scanning
  • Prefer skimmable over clever. A reader who only reads the 3 headers should still get something useful from the newsletter. Give them the takeaway, not a riddle.

Examples (skimmable/TLDR style):

  • # 23,000 PARENTS TOLD 50CAN WHAT THEY ACTUALLY WANT
  • # 529 PLANS NOW COVER K-12 HOMESCHOOL EXPENSES
  • # "PUBLIC EDUCATION IS A GOAL, NOT A FIXED SET OF INSTITUTIONS"
  • # SF SCHOOLS DOUBLED READING PROFICIENCY WITH 15-MINUTE SESSIONS

Examples (information gap style - use sparingly):

  • # NONE OF THE DREAMS ARE GOOD
  • # THE GETTING BY TRAP

Transitions

Avoid clunky transitions between segments:

  • ❌ "Speaking of Janssen..."
  • ❌ "On a related note..."
  • ❌ "While we're on the topic of..."

Jump straight into the new segment with a hook that stands alone. The --- divider already signals a new section.

If segments are thematically connected, let the reader make the connection. Don't spell it out.


Phase 4: Social Media (Optional)

For social repurposing, use the social-content-creation skill or create Social_Media_Plan.md.


Phase 5: QA & Archive

Final Checklist

  • Segments are orthogonal (related but not repetitive)
  • NO EMOJIS in body
  • H1 headers for segments (descriptive titles, no THOUGHT/TREND/TOOL prefix)
  • Dividers (---) between opening letter and first segment
  • Dividers (---) between each segment
  • Sign-off: "- Charlie (the OpenEd newsletter guy)" (single dash, not double)
  • 500-800 words total
  • All links work
  • Voice sounds human, not performative
  • Headlines give the reader the TLDR from scanning (skimmable over clever)
  • Source attribution on segments that draw from a specific piece (e.g., "(Source: The LOOPcast)")
  • Salt check: would this alienate a mainstream homeschool parent, or just inform them?
  • Check staging folder for already-used sources before including (grep Newsletter_FINAL.md files)

HubSpot Integration

After approval, use hubspot-email-draft skill to create the draft in HubSpot:

  1. Clone source: Always clone the MOST RECENTLY SENT daily email (not a fixed template ID). Search HubSpot for emails with "OED" in the name, sorted by most recent, and clone that one. This ensures the new draft inherits the correct send list and targeting settings.
  2. Converts markdown to HTML (H1s → <h1>, dividers → <hr>)
  3. Updates subject, preview, body
  4. Returns edit link - one click to publish

Thumbnail image linking rule (CRITICAL): When inserting a section thumbnail image (e.g. above a podcast corner or spotlight section), the image MUST be wrapped in a hyperlink pointing to the same URL as the section's featured/CTA link. Example: if the podcast section links to opened.co/blog/episode-slug, the thumbnail image above it must also link to that same URL. Never insert an unlinked image above a section that has a CTA.

Archive

cp [working-folder]/Newsletter_FINAL.md daily-newsletter-workflow/examples/[YYYY-MM-DD]-newsletter.md

Quick Reference

Edition Types

Type A (Integrated): All 3 segments orbit a single theme. Use when you have one strong anchor piece.

Type B (Modular): Segments stand alone, connected by voice. Use when pieces don't naturally connect - don't force integration.

Anti-Patterns

Structural:

  • Fragments for punch: "Thousands of dollars. Five bucks a pop." → Write complete sentences
  • Snarky parentheticals: "(Thank you, intrinsic motivation.)" → Only use when genuinely adding punch
  • Forced cheerfulness: "TGIF Eddies! Hope your week was AMAZING!" → Just "Greetings Eddies."
  • Transcript dump: Pasting quotes with minimal synthesis → Extract one insight, reframe in your voice
  • Fake question: "What if schools actually taught kids to think?" → Just tell them

AI Tells (KILL ON SIGHT):

  • Correlative constructions (all variants): "doesn't mean X. It means Y." / "X isn't just Y - it's Z" / "It's not about X, it's about Y" / "Less X, more Y." → Just state the positive claim.
  • Performative emotional narration: "He made a point that stuck with me" / "A line that stuck with me" / "This hit me hard" / "I keep thinking about..." → Just present the information. Let it land on its own.
  • Scaffolding phrases: "A few things that jumped out" / "Here's what's interesting" / "What's worth noting" → Cut. Go straight to the content.
  • Telling the reader how to react: "I'll let those numbers sit for a second" / "Read that slowly" / "Let that sink in" → Present the data and move on.
  • Conditional framing as take: "The question is whether you want X or whether you want Y" → This is a correlative wearing a mustache. State your position.
  • Dramatic inflation: "Things that would have been unthinkable a decade ago" / "a number that would have shocked anyone" → Understated is better. The data speaks.

Tone traps:

  • Over-politicizing: OpenEd is above the fray. When covering political topics (ESAs, school choice, policy), present the data without partisan framing. Say "enjoys broad support across the political spectrum" rather than making it a partisan story. Mention party breakdowns as data points, not as the narrative.
  • Too much editorial "me": The newsletter is written in first person but the writer is a lens, not the subject. Don't narrate your reaction to information. Present it.
  • Homeschool-specific tools: When sharing resources aimed at homeschoolers, note that OpenEd students aren't technically classified as homeschoolers in most states. A quick parenthetical or note at the end works.

Reference Files

Voice examples: See "Voice Priming" section at top of this file (inline, no load needed)

For more techniques: references/pirate-wires-segment-techniques.md - 7 techniques with TTT application tables

Opening letter examples: references/opening-letter-patterns.md - Charlie's actual openings

Content resources: Tool Database

Related skills:

  • ghostwriter - Voice transformation + AI pattern detection (replaces archived ai-tells)
  • voice-dna (root level) - Charlie's personal voice patterns
  • opened-identity - Brand voice, Sarah persona, messaging anchors
  • newsletter-to-social - Social repurposing after newsletter is done
  • newsletter-subject-lines - Subject line generation (Phase 5)

File Naming

Working folder: Studio/Newsletter Studio/[YYYY-MM-DD] - [Theme]/

Files:

  • Source_Material.md
  • Checkpoint_1_Angles.md
  • Newsletter_DRAFT.md
  • Newsletter_FINAL.md (only after approval)

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.31%
按下载量换算57

Claude

30.37%
按下载量换算48

Cursor

20.13%
按下载量换算32

Gemini CLI

10.74%
按下载量换算17

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add https://github.com/cdeistopened/opened-vault --skill opened-daily-newsletter-writer 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills