opened-weekly-newsletter-writer
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseOpenEd Weekly Newsletter Writer
OpenEd每周通讯撰写技能
Creates Friday digest newsletters synthesizing the week's content into six distinct newsletter sections, plus a bonus Phase 4 for creating Ed's Roundup Twitter thread strategy.
用于创建周五摘要通讯,将一周内容整合为六个不同的通讯板块,外加一个额外的第四阶段,用于制定Ed's Roundup Twitter线程策略。
Content Engine Philosophy
内容引擎理念
This skill is part of a living system. Every time we run this workflow, we should be:
-
Tightening - Finding friction points and removing them. If something takes too long or requires too many steps, note it for skill improvement.
-
Connecting - Looking for ways to involve other skills without adding friction:
- After drafting → for social spokes
newsletter-to-social - After identifying quotes → check for tagging
nearbound - After completion → for featured creators
outreach-email-draft - Quality concerns → for review
quality-loop
- After drafting →
-
Evolving - When we discover better patterns mid-workflow, ask permission to update this skill in real-time. The skill should encode what we learn.
-
Proactive - After completing the newsletter, automatically offer:
- Social post generation (6-9 posts)
- Ed's Roundup Twitter thread
- Outreach emails to featured creators
- HubSpot draft export
The goal: Each run makes the next run better. Skills are energetic pathways - the more we use them, the sharper they get.
Not for: Monday-Thursday daily newsletters (use ).
opened-daily-newsletter-writerRequirements: Flexible length (typically 1,500-2,500 words) • NO EMOJIS in body • Pirate Wires-influenced voice • All external links include source attribution in parentheses
此技能属于一个动态系统。 每次运行此工作流时,我们应做到:
-
精简 - 找出流程中的摩擦点并消除。如果某件事耗时过长或步骤过多,记录下来以便优化技能。
-
关联 - 寻找无需增加摩擦即可联动其他技能的方式:
- 草稿完成后 → 使用生成社交内容
newsletter-to-social - 识别引用内容后 → 使用检查标签
nearbound - 完成通讯后 → 使用撰写给特色创作者的推广邮件
outreach-email-draft - 质量问题 → 使用进行审核
quality-loop
- 草稿完成后 → 使用
-
演进 - 如果在工作流执行过程中发现更优模式,请求实时更新此技能。技能应融入我们学到的经验。
-
主动 - 完成通讯后,自动提供以下服务:
- 社交帖子生成(6-9篇)
- Ed's Roundup Twitter线程
- 给特色创作者的推广邮件
- HubSpot草稿导出
目标: 每次运行都让下一次更高效。技能是充满活力的路径——使用得越多,就越精准。
不适用于: 周一至周四的每日通讯(请使用)。
opened-daily-newsletter-writer要求: 长度灵活(通常1500-2500字)• 正文禁止使用表情符号 • 采用Pirate Wires风格的语气 • 所有外部链接需在括号中注明来源
Formatting Rules (Critical)
格式规则(至关重要)
Images Above Titles
图片置于标题上方
Thumbnail/header images ALWAYS go ABOVE the H1 section title, not below it:
缩略图/页眉图片必须放在H1章节标题上方,而非下方:
Section Title Here
Section Title Here
undefinedundefinedH1 for All Sections
所有章节使用H1
Section titles use (H1), not (H2). This applies to: Featured Podcast, Deep Dive, Trends, Tools, From the Community, Ed's Stable.
###章节标题使用(H1),而非(H2)。适用于:Featured Podcast、Deep Dive、Trends、Tools、From the Community、Ed's Stable。
###Opening Letter Has No Header
开篇无标题
The opening letter starts immediately after the frontmatter - no header, no dividing line before it. Just launch into the content.
## OPENING LETTER开篇信件直接在前置内容后开始——无需标题,也无需前置分隔线,直接进入内容。
## OPENING LETTERInclude Links Early in Opening Letter
开篇信件尽早加入链接
Include links to the podcast episode and deep dive article inline in the opening letter. Many readers won't scroll past the opening - give them the links up front.
在开篇信件中尽早加入播客和深度文章的内嵌链接(许多读者不会往下滚动)。
Source Attribution Format
来源归因格式
Put the source in italics right after the link, before the description:
[**Compelling Headline**](url) *(Source Name)* - Short teasing description.NOT at the end of the paragraph:
...description. (Source Name)在链接后立即用斜体注明来源,而非段落末尾:
[**引人注目的标题**](url) *(Source Name)* - 简短的吸引性描述。不要放在段落末尾:
...description. (Source Name)Link Text = Compelling Headlines
链接文本=引人注目的标题
Never just copy the article's actual title for link text. Write a compelling, curiosity-driven headline. Think: what would make someone stop scrolling? MFM energy - tease the value, open a loop.
Good:
Bad:
[**Why your kid struggles with algebra (it started in 3rd grade)**](url)[**Test Results Reveal a Deeper Issue in Math**](url)Good:
Bad:
[**This school finishes all academics by 10am**](url)[**Alpha School Students Finish Academics in 2 Hours**](url)切勿直接复制文章的实际标题作为链接文本。撰写引人好奇、激发兴趣的标题。思考:什么能让读者停下滚动的手指?要有MFM风格——突出价值,留下悬念。
示例:
好:
差:
[**为什么你的孩子学不好代数?根源在三年级**](url)[**测试结果揭示数学学习的深层问题**](url)好:
差:
[**这所学校上午10点前就完成所有学业**](url)[**Alpha学校学生2小时完成学业**](url)Best Links Format (McGarry Style)
最佳链接格式(McGarry风格)
The links section uses a single H1 () with H3 subheaders (, ). One uniform format for all items:
# Best Links### Trends### ToolsCuriosity-provoking sentence that earns the click. (Source Name)Where Source Name is the only hyperlink. The description text is plain - no bold, no italics. The source name is hyperlinked in parentheses at the end.
In markdown:
The richest school in DC just told 8th graders: no more novels. ([Education Next](url))
Your kid knows the material. Here's why they freeze on tests. ([Raising Lifelong Learners](url))Key principles (from Matt McGarry):
- The sentence should provoke curiosity, not summarize the article. Leave something out. Tease the value.
- Don't give away the plot - earn the click.
- One sentence is ideal. Two max if the second adds essential context.
- Source name is always the hyperlink, never the description text.
- No bold, no italics, no formatting on the description. Clean and scannable.
McGarry reference examples (for flavor - our headers/content differ, but the link format is the model):
BEST LINKS
My favorite finds
📈 Growth
Simple AI prompt to turn your newsletter into viral LinkedIn posts (LinkedIn)
Colin and Samir: How TBPN built the luxury brand of the creator economy (podcast and article)
💰 Revenue
How Caleb Hammer makes $780k per month (Substack)
How to best utilize beehiiv's new dynamic content feature (YouTube)
How to go from getting paid as an affiliate to a flat fee sponsorship model (YouTube)
👀 ICYMI
The fastest way to make an extra $10k+ from your email list this week (GrowLetter)
🗞️ Industry News
Google says it's fixed Gmail issues with spam and misclassification (TechCrunch)Note the pattern: every item is a single curiosity-driven sentence, and the source name in parens is the only link. No bold. No italics. No description paragraphs. Just the sentence and the source. Our version uses the same format but with and as H3 subheaders (no emojis).
### Trends### ToolsCommunity subsection is optional - include only when there are standout community voices worth featuring. Use the same format.
链接部分使用一个H1()和H3子标题(、)。所有条目采用统一格式:
# Best Links### Trends### Tools激发好奇心的句子,吸引读者点击。(Source Name)其中Source Name是唯一的超链接。描述文本为纯文本——无需加粗、斜体。来源名称在括号中并添加超链接。
Markdown格式示例:
华盛顿最富有的学校刚刚告知八年级学生:不再教授小说。([Education Next](url))
你的孩子掌握了知识,但考试时却大脑空白。原因在这里。([Raising Lifelong Learners](url))核心原则(来自Matt McGarry):
- 句子应激发好奇心,而非总结文章。留下悬念,突出价值。
- 不要剧透——让读者主动点击。
- 理想长度为一句话。若能补充关键背景,最多两句话。
- 来源名称始终是超链接,而非描述文本。
- 描述文本无需加粗、斜体或任何格式,保持简洁易读。
McGarry参考示例(仅作风格参考——我们的标题/内容不同,但链接格式一致):
BEST LINKS
My favorite finds
📈 Growth
Simple AI prompt to turn your newsletter into viral LinkedIn posts (LinkedIn)
Colin and Samir: How TBPN built the luxury brand of the creator economy (podcast and article)
💰 Revenue
How Caleb Hammer makes $780k per month (Substack)
How to best utilize beehiiv's new dynamic content feature (YouTube)
How to go from getting paid as an affiliate to a flat fee sponsorship model (YouTube)
👀 ICYMI
The fastest way to make an extra $10k+ from your email list this week (GrowLetter)
🗞️ Industry News
Google says it's fixed Gmail issues with spam and misclassification (TechCrunch)注意模式:每个条目都是一句激发好奇心的句子,括号中的来源名称是唯一链接。无加粗、斜体,无描述段落。仅包含句子和来源。我们的版本采用相同格式,但使用和作为H3子标题(无表情符号)。
### Trends### Tools社区子板块为可选内容——仅当有值得推荐的杰出社区声音时才添加。使用相同格式。
Workflow
工作流
Phase 1: Gather & Organize Source Material
阶段1:收集与整理素材
IMPORTANT EFFICIENCY NOTE: When the user provides source material directly (copy-pasted content, transcripts, links), DO NOT regenerate it token-by-token. Instead:
- Ask the user to create the file themselves by copy-paste
Source_Material.md - OR use Read tool if they've already created it
- OR acknowledge what they've provided and move directly to Phase 2
Only create/write source material files when:
- User asks you to organize scattered notes
- User needs help structuring raw data
- Content requires significant reorganization
Collect from the week:
- Opening letter context (timely announcements, promotions, deadlines)
- Deep Dive article with full text and author info
- Deep Dive Podcast episode transcript or description
- Additional curated links, tools, and other resources
If creating , include:
Source_Material.md- All URLs, descriptions, and key quotes
- Author names and titles
- Statistics and data points
- Engagement context (why this content matters)
- Names and Twitter handles of people/organizations mentioned (for Phase 4 Twitter thread)
重要效率提示: 当用户直接提供素材(复制粘贴的内容、文字稿、链接)时,请勿逐词重新生成。而是:
- 请用户自行通过复制粘贴创建文件
Source_Material.md - 或如果用户已创建该文件,使用Read工具读取
- 或确认用户提供的内容,直接进入阶段2
仅在以下情况创建/编写素材文件:
- 用户要求整理零散笔记
- 用户需要帮助结构化原始数据
- 内容需要大幅重组
收集一周内的以下内容:
- 开篇信件背景(及时公告、推广、截止日期)
- 带有完整文本和作者信息的深度文章
- 深度播客的文字稿或描述
- 其他精选链接、工具和资源
如果创建,请包含:
Source_Material.md- 所有URL、描述和关键引用
- 作者姓名和头衔
- 统计数据和数据点
- 参与背景(此内容为何重要)
- 提及的个人/组织的姓名和Twitter账号(用于阶段4的Twitter线程)
Phase 2: Draft Opening Letter
阶段2:撰写开篇信件
No header. The opening letter starts right after frontmatter - no , no divider.
## OPENING LETTERCreate opening section that:
- Opens with greeting ("Happy Friday!" or similar)
- Names the 1-2 conversations/stories that define this week
- Includes inline links to the podcast and deep dive early (many readers won't scroll)
- Connects the week's content with a through-line (what ties it all together?)
- Keeps it conversational and specific - name people, reference moments
- Signs off: "- Charlie (the OpenEd newsletter guy)"
Opening Letter Example Structure:
- Greeting
- Name the week's lead story with link (podcast, deep dive, or both)
- Name the second story with link
- One sentence connecting them (the through-line)
- "That's the thread this week."
- Charlie signature
无标题。 开篇信件直接在前置内容后开始——无需,也无需分隔线。
## OPENING LETTER创建开篇部分,需:
- 以问候语开头(如“周五快乐!”)
- 点明定义本周的1-2个对话/故事
- 尽早加入播客和深度文章的内嵌链接(许多读者不会往下滚动)
- 将一周内容串联成一条主线(所有内容的关联点是什么?)
- 保持口语化和具体性——提及人名,引用具体时刻
- 落款:“- Charlie(OpenEd通讯负责人)”
开篇信件示例结构:
- 问候语
- 点明本周核心故事并附带链接(播客、深度文章或两者皆有)
- 点明第二个故事并附带链接
- 一句话串联两者(主线)
- “这就是本周的核心脉络。”
- Charlie落款
Phase 3: Draft All Remaining Newsletter Sections
阶段3:撰写所有剩余通讯章节
Create with six sections:
Weekly_Newsletter_Draft.mdFeatured Podcast (image above title)
创建,包含六个章节:
Weekly_Newsletter_Draft.mdFeatured Podcast(图片置于标题上方)
Compelling Title for the Episode
引人注目的播客标题
- *By [Author Name]* byline below title
- Brief setup, then the story
- One compelling moment or key insight
- 2-3 direct quotes from transcript
- Honest criticisms or nuance (shows we're not cheerleading)
- Link to listen + link to read: `[Listen](URL) | [Read the write-up](URL)`
**Deep Dive** (image above title)- 标题下方标注 *By [Author Name]*
- 简短介绍,然后讲述故事
- 一个引人入胜的时刻或关键见解
- 2-3条来自文字稿的直接引用
- 诚实的批评或不同观点(表明我们并非一味吹捧)
- 收听链接+阅读链接:`[Listen](URL) | [Read the write-up](URL)`
**Deep Dive**(图片置于标题上方)Compelling Title for the Article
引人注目的文章标题
- 3-4 paragraphs, narrative style
- Hook with compelling angle
- Include key data point(s) or memorable quote
- End with link: `[Read the full deep dive](URL)`
**Best Links** (consolidated section with H3 subheaders, McGarry format)- 3-4段叙事风格的内容
- 以引人入胜的角度开篇
- 包含关键数据点或难忘引用
- 结尾添加链接:`[Read the full deep dive](URL)`
**Best Links**(整合章节,使用H3子标题,McGarry格式)Best Links
Best Links
Our favorite finds from this week.
本周我们最喜欢的精选内容。
Trends
Trends
The richest school in DC just told 8th graders: no more novels. (Education Next)
This school finishes all academics by 10am. (Michael B. Horn)
华盛顿最富有的学校刚刚告知八年级学生:不再教授小说。(Education Next)
这所学校上午10点前就完成所有学业。(Michael B. Horn)
Tools
Tools
Your kid knows the material. Here's why they freeze on tests. (Raising Lifelong Learners)
A homeschool mom just did a frog dissection with her 6th grader in rural Hawaii. The comments are full of curriculum tips. (r/homeschool)
- `### Trends`: 4-6 items. Curiosity-provoking sentence + hyperlinked source in parens.
- `### Tools`: 6-10 items. Same format. Sentence + source. One extra sentence OK if it adds real context.
- `### Community` (optional): Only include if there are standout community voices. Same format.
**Ed's Stable**
- Closing synthesis that ties the week's through-line together
- Can reference social media posts, carousels, or Facebook content from the week
- Close with the question or idea that connects everything
- Include links to blog + podcast at the bottom
**Closing:**That's all for this week!
– Charlie (the OpenEd newsletter guy)
undefined你的孩子掌握了知识,但考试时却大脑空白。原因在这里。(Raising Lifelong Learners)
一位 homeschool妈妈在夏威夷农村和六年级孩子一起完成了青蛙解剖。评论区满是课程建议。(r/homeschool)
- `### Trends`:4-6个条目。激发好奇心的句子+括号中的超链接来源。
- `### Tools`:6-10个条目。相同格式。句子+来源。若能补充关键背景,最多可添加一句。
- `### Community`(可选):仅当有值得推荐的杰出社区声音时才添加。使用相同格式。
**Ed's Stable**
- 收尾总结,串联本周主线
- 可提及本周的社交媒体帖子、轮播图或Facebook内容
- 以一个能关联所有内容的问题或想法结尾
- 底部添加博客+播客链接
**结尾:**本周内容就到这里!
– Charlie(OpenEd通讯负责人)
P.S. 管理邮件偏好链接
undefinedPhase 4: Create Ed's Roundup Twitter Thread Strategy
阶段4:制定Ed's Roundup Twitter线程策略
NEW PHASE: Create (or if iterating)
Twitter_Thread_Roundup.mdTwitter_Thread_Roundup_V2.mdThis phase creates a multi-tweet thread that recaps the week's key stories and creators featured in the newsletter.
Step 1: Identify All Twitter Handles
- Create a comprehensive list of every person/organization mentioned in the newsletter
- Search Twitter/X for each to find active accounts and verify handles
- Prioritize people who are:
- Featured guests (podcasters, experts)
- Content creators referenced (Austin Scholar, Adam Savage, Henrik Wes, etc.)
- Organizations mentioned (LearningRx, Simply Charlotte Mason, etc.)
- Format as:
@handle (Name/Organization) - [brief context]
Step 2: Research Active Accounts
- For each identified person/org, verify:
- Do they have a Twitter account?
- Is it active (posted in last 30 days)?
- Should they be tagged in the thread?
- Document in the Twitter thread file which handles are taggable
Step 3: Draft Twitter Thread
Opening Tweet (Hook):
- Opens with brand identity: "Ed's Roundup: The most clicked education links from this week"
- Or: "Here's what 10K+ readers of OpenEd Weekly are paying attention to"
- States number of creators: "13 creators. 1 thread."
- Includes emoji (horse/roundup theme): 🪶 or 🐴
- Clear call to action: "(thread)"
Creator Tweets (One per major theme/person):
- Feature person's name: @handle
- Their contribution/insight (1 sentence max)
- Direct quote if available
- Link to their content or OpenEd's content about them
- Use proven tweet structures: Direct Quote, Problem Recognition, Data Point, Contrarian Take, Observation Post
Closing Tweets:
- Wrap-up tweet with CTA to OpenEd Daily/Weekly
- Engagement tweet asking readers to reply with their favorite creators
Format Examples:
Tweet with direct quote:
"When we teach science as memorization, we're missing the point."
— @AdamSavage (MythBusters)
That quote started a conversation about why wonder matters more than worksheets.
Full deep dive: https://opened.co/blog/best-homeschool-science-curriculumTweet with problem/insight:
The reason your kid won't listen when you yell?
It's not defiance. It's neurology.
Dr. Amy Moore explains auditory exclusion: https://opened.co/blog/why-your-adhd-kid-wont-listen-its-not-what-you-thinkTweet with data:
1.5M students are now in microschools.
That's the same as Catholic schools.
Same enrollment. Different satisfaction rates.
@rebeleducator mapped it: [URL]Reference Guide: See for complete real-world example from Nov 14, 2025 newsletter
references/eds-roundup-example.md新阶段: 创建(如果迭代则为)
Twitter_Thread_Roundup.mdTwitter_Thread_Roundup_V2.md此阶段创建多条推文组成的线程,总结通讯中重点介绍的本周关键故事和创作者。
步骤1:识别所有Twitter账号
- 创建通讯中提及的所有个人/组织的完整列表
- 在Twitter/X上搜索每个账号,确认活跃状态并验证账号
- 优先考虑以下对象:
- 特邀嘉宾(播客嘉宾、专家)
- 引用的内容创作者(Austin Scholar、Adam Savage、Henrik Wes等)
- 提及的组织(LearningRx、Simply Charlotte Mason等)
- 格式:
@handle (Name/Organization) - [简要背景]
步骤2:研究活跃账号
- 对每个识别出的个人/组织,验证:
- 是否有Twitter账号?
- 是否活跃(过去30天内发布过内容)?
- 是否应在线程中@他们?
- 在Twitter线程文件中记录可@的账号
步骤3:撰写Twitter线程
开篇推文(钩子):
- 以品牌身份开头:“Ed's Roundup:本周最受关注的教育链接”
- 或:“1万+ OpenEd每周通讯读者正在关注这些内容”
- 提及创作者数量:“13位创作者,一条线程”
- 添加表情符号(马/围捕主题):🪶或🐴
- 明确行动号召:“(thread)”
创作者推文(每个主题/人物一条):
- 提及人物姓名:@handle
- 他们的贡献/见解(最多一句话)
- 如有可用的直接引用
- 链接到他们的内容或OpenEd关于他们的内容
- 使用经过验证的推文结构:直接引用、问题识别、数据点、反向观点、观察帖
收尾推文:
- 总结推文,号召关注OpenEd每日/每周通讯
- 互动推文,邀请读者回复分享他们最喜欢的创作者
格式示例:
带直接引用的推文:
“当我们把科学教成死记硬背,就偏离了初衷。”
— @AdamSavage (MythBusters)
这句话引发了关于为何好奇心比练习题更重要的讨论。
完整深度文章:https://opened.co/blog/best-homeschool-science-curriculum带问题/见解的推文:
为什么你大喊时孩子不听?
不是叛逆,是神经学原因。
Dr. Amy Moore解释听觉排斥:https://opened.co/blog/why-your-adhd-kid-wont-listen-its-not-what-you-think带数据的推文:
150万学生现在就读于微型学校。
这和天主教学校的招生人数相同。
招生人数相同,但满意度不同。
@rebeleducator进行了分析:[URL]参考指南: 请参阅,获取2025年11月14日通讯中的完整真实示例
references/eds-roundup-example.mdPhase 5: Integrate Source Attributions
阶段5:整合来源归因
As sections are drafted, embed source attributions directly in the newsletter text. No separate file needed.
URL_Mappings.mdAttribution Style:
Mention the source by name EARLY in the blurb with a hyperlink woven naturally into the text. Avoid parenthetical citations at the end.
- Good: "A Reddit mom of five shares her hard-won advice..."
- Good: "New EdChoice polling found overwhelming support..."
- Good: "A Penn Foster survey reported by USA Today found..."
- Avoid: "...bouncing around opens you to gaps. (Reddit)"
- Avoid: "...found overwhelming support for teaching debate. (EdChoice)"
The goal is conversational flow, not academic citation style.
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: "Ken Danford has been running North Star since 1996..."
Bad: "Ken Danford has been running North Star, a physical community center where teens can legally homeschool"
When multiple sources are provided with body text to reference, hyperlink ALL links where the referenced content is used. Don't let any provided link go unhyperlinked.
在撰写章节时,将来源归因直接嵌入通讯文本中。无需单独的文件。
URL_Mappings.md归因风格:
尽早在内容中提及来源名称,并自然融入超链接。避免在段落末尾使用括号引用。
- 好: “一位Reddit上的五孩妈妈分享了她来之不易的建议……”
- 好: “EdChoice的最新民意调查发现……”
- 好: “《今日美国》报道的Penn Foster调查显示……”
- 避免: “……频繁切换会导致知识漏洞。(Reddit)”
- 避免: “……发现对教授辩论的支持率很高。(EdChoice)”
目标是保持对话流畅,而非学术引用风格。
超链接规则:
当提供链接时,始终在文本正文中添加超链接(切勿放在末尾)。仅用2-3个关键词链接主要动作或主题。
好: “Ken Danford从1996年起就运营North Star……”
差: “Ken Danford运营North Star,这是一个青少年可以合法进行homeschool的实体社区中心”
当提供多个链接并附带参考文本时,所有参考内容对应的链接都要添加超链接。不要遗漏任何提供的链接。
Phase 6: QA & Finalization
阶段6:质量检查与最终定稿
Quality Checklist:
- NO EMOJIS in newsletter body text (OK in Twitter thread)
- All external links include source attribution
- Deep Dive article is compelling (not just a summary)
- Podcast highlight is one moment, not overview
- Trends section is data-driven with sources
- Tools section leads with benefit, not features
- Ed's Stable reflects actual brand moments
- All links are verified and working
- No duplicate content between sections
- Pirate Wires tone consistent throughout
- Opening letter includes all key announcements
- Twitter thread handles are verified and active
Archive:
bash
cp [working-folder]/Weekly_Newsletter_DRAFT.md [archive-folder]/[YYYY-MM-DD]-newsletter-final.md
cp [working-folder]/Social_Media.md [archive-folder]/[YYYY-MM-DD]-social-media.md
cp [working-folder]/X_Article_Format.md [archive-folder]/[YYYY-MM-DD]-x-article.md质量检查清单:
- 通讯正文禁止使用表情符号(Twitter线程中可使用)
- 所有外部链接都包含来源归因
- 深度文章引人入胜(而非简单摘要)
- 播客亮点聚焦一个时刻,而非概述
- Trends部分基于数据并带有来源
- Tools部分以价值为导向,而非功能
- Ed's Stable反映真实品牌时刻
- 所有链接已验证且可用
- 章节间无重复内容
- 全程保持Pirate Wires风格
- 开篇信件包含所有关键公告
- Twitter线程中的账号已验证且活跃
存档:
bash
cp [working-folder]/Weekly_Newsletter_DRAFT.md [archive-folder]/[YYYY-MM-DD]-newsletter-final.md
cp [working-folder]/Social_Media.md [archive-folder]/[YYYY-MM-DD]-social-media.md
cp [working-folder]/X_Article_Format.md [archive-folder]/[YYYY-MM-DD]-x-article.mdReference Files
参考文件
Each section of the newsletter has an example reference file with the actual format, real examples from a published newsletter, and specific instructions for writing that section:
- Opening Letter Example - How to write warm, inclusive openings with clear CTAs
- Deep Dive Example - Third-person teaser format that makes readers curious
- Podcast Highlight Example - One compelling moment with quotes
- Trends We're Following Example - Data-driven stories with source attribution
- Tools We're Bookmarking Example - Benefit-first descriptions with sequential ordering
- Ed's Stable Example - Social media highlights and brand moments
- Ed's Roundup Twitter Thread Example - Complete Twitter thread with all creators tagged
通讯的每个章节都有示例参考文件,包含实际格式、已发布通讯的真实示例以及撰写该章节的具体说明:
- 开篇信件示例 - 如何撰写温暖、包容且行动号召明确的开篇
- 深度文章示例 - 第三人称 teaser格式,激发读者好奇心
- 播客亮点示例 - 聚焦一个引人入胜的时刻并附带引用
- Trends示例 - 基于数据的故事,带有来源归因
- Tools示例 - 以价值为导向的描述,按顺序排列
- Ed's Stable示例 - 社交媒体亮点和品牌时刻
- Ed's Roundup Twitter线程示例 - 完整的Twitter线程,包含所有@的创作者
Key Distinctions
关键区别
Weekly vs Daily:
- Daily: 500-800 words, 1 each Trend/Tool, shorter sections
- Weekly: 1,500-2,500 words, 4-6 Trends, 10-15 Tools, deeper analysis
Newsletter Structure:
- Opening Letter
- Deep Dive Article (Wed article)
- Podcast Highlight (Thu episode - one moment) — OPTIONAL: skip if no episode that week
- Trends We're Following (data-driven stories, 4-5 items)
- Tools We're Bookmarking (resources, curricula, 6-10 items, max 1 Reddit)
- Ed's Stable (brand moments, social highlights, engagement ask)
Social Media Outputs (Phase 4):
- Social_Media.md (handles table, X thread, single posts)
- X_Article_Format.md (long-form article for X)
What's Removed:
- "Listen for the Listeners" (too redundant with Trends)
- "Reddit Corner" (content integrated into other sections as relevant)
- "Parting Thought" (function now served by Ed's Stable closing)
每周vs每日:
- 每日:500-800字,每个Trend/Tool各1个,章节较短
- 每周:1500-2500字,4-6个Trends,10-15个Tools,分析更深入
通讯结构:
- 开篇信件
- 深度文章(周三发布的文章)
- 播客亮点(周四发布的节目——聚焦一个时刻)——可选:若无本周节目则跳过
- Trends We're Following(基于数据的故事,4-5个条目)
- Tools We're Bookmarking(资源、课程,6-10个条目,最多1个Reddit内容)
- Ed's Stable(品牌时刻、社交媒体亮点、互动请求)
社交媒体输出(阶段4):
- Social_Media.md(账号表、X线程、单条帖子)
- X_Article_Format.md(用于X的长文格式)
已移除内容:
- "Listen for the Listeners"(与Trends过于重复)
- "Reddit Corner"(内容整合到其他相关章节)
- "Parting Thought"(功能由Ed's Stable结尾替代)
Critical Reminders
重要提醒
❌ NO EMOJIS in newsletter body
❌ Don't skip Phase 1 (source material gathering)
❌ Deep Dive = Wed article ONLY (not podcast)
❌ Trends must have data
❌ No duplicate content between sections
❌ Twitter handles must be verified before tagging (never guess)
❌ No parenthetical attributions — weave source names early with hyperlinks
❌ Max ONE Reddit post in Tools section
✅ 1,500-2,500 words for newsletter
✅ Humanize stats with context
✅ Benefit-first approach for tools
✅ Create Social_Media.md with handles table, thread, single posts
✅ Create X_Article_Format.md for long-form posting
✅ Archive newsletter, social media, AND X article files
❌ 通讯正文禁止使用表情符号
❌ 请勿跳过阶段1(素材收集)
❌ 深度文章仅限周三发布的文章(非播客)
❌ Trends必须基于数据
❌ 章节间无重复内容
❌ 必须验证Twitter账号后再@(切勿猜测)
❌ 避免使用括号归因——尽早提及来源名称并融入超链接
❌ Tools部分最多包含1个Reddit内容
✅ 通讯长度1500-2500字
✅ 用背景信息让数据更人性化
✅ Tools部分以价值为导向
✅ 创建包含账号表、线程、单条帖子的Social_Media.md
✅ 创建用于X长文的X_Article_Format.md
✅ 存档通讯、社交媒体和X长文文件
Phase 4: Social Media Protocol (UPDATED)
阶段4:社交媒体协议(更新)
Create with the following sections:
Social_Media.md创建,包含以下章节:
Social_Media.md4.1 Verified Handles Table
4.1 已验证账号表
Search and verify X/Twitter handles for all people and organizations mentioned in the newsletter. Document in a table:
| Person/Org | Handle | Context | Tag in thread? |
|---|---|---|---|
| [Name] | @handle | [Role/quote] | ✅ or ❌ |
Note which are Instagram-only or Substack-only (no Twitter).
搜索并验证通讯中提及的所有个人/组织的X/Twitter账号。整理为表格:
| 个人/组织 | 账号 | 背景 | 是否在线程中@ |
|---|---|---|---|
| [姓名] | @handle | [角色/引用] | ✅ 或 ❌ |
注明仅在Instagram或Substack活跃的账号(无Twitter)。
4.2 X Thread (8-12 tweets)
4.2 X线程(8-12条推文)
Structure:
- Hook tweet — List the main topics, end with "Thread 👇"
- Feature tweets — One per key person/insight, tag them directly
- CTA tweet — Links to newsletter, deep dive, subscribe
Tweet formats that work:
- Direct quote + attribution + link
- Contrarian observation + source
- Data point + implication
- "Meanwhile, @handle shared this..."
结构:
- 钩子推文 — 列出主要主题,结尾加“Thread 👇”
- 特色推文 — 每个关键人物/见解一条,直接@他们
- 行动号召推文 — 链接到通讯、深度文章,邀请订阅
有效推文格式:
- 直接引用+归因+链接
- 反向观察+来源
- 数据点+影响
- “与此同时,@handle分享了这个……”
4.3 Single-Post Options (2-3 standalone posts)
4.3 单条帖子选项(2-3条独立帖子)
Create 2-3 self-contained posts that can go out independently:
- Best for viral potential (contrarian takes, surprising data)
- Don't require the full thread context
- Can be scheduled throughout the weekend
创建2-3条可独立发布的帖子:
- 适合传播(反向观点、惊人数据)
- 无需依赖完整线程背景
- 可安排在周末发布
4.4 X Article Format
4.4 X长文格式
Create — the full newsletter reformatted for X's long-form Articles feature:
X_Article_Format.md- Remove markdown formatting that doesn't render
- Add @ mentions inline where people are quoted
- Keep section headers
- Ensure all links are full URLs
创建——将完整通讯重新格式化为X的长文文章格式:
X_Article_Format.md- 移除无法渲染的Markdown格式
- 在引用人物的地方内嵌@提及
- 保留章节标题
- 确保所有链接为完整URL
Expected Output Files:
预期输出文件:
[working-folder]/
├── Weekly_Newsletter_DRAFT.md
├── Social_Media.md # Handles + thread + single posts
└── X_Article_Format.md # Long-form X Article version[working-folder]/
├── Weekly_Newsletter_DRAFT.md
├── Social_Media.md # 账号表+线程+单条帖子
└── X_Article_Format.md # X长文版本Success Metrics:
成功指标:
- All mentioned creators identified with verified handles
- Thread tags real, active accounts (not guessed)
- Single posts have standalone viral potential
- X Article is copy-paste ready
- 所有提及的创作者都已识别并验证账号
- 线程中@的是真实活跃账号(非猜测)
- 单条帖子具备独立传播潜力
- X长文可直接复制粘贴发布
Related Skills
相关技能
- - For generating newsletter subject lines
hook-and-headline-writing - - For repurposing newsletter sections into individual posts
social-content-creation - - For creating captions for clips featured in newsletter
video-caption-creation
- - 用于生成通讯主题
hook-and-headline-writing - - 用于将通讯章节改编为独立帖子
social-content-creation - - 用于为通讯中特色视频创建字幕
video-caption-creation
Version History
版本历史
-
v2.1 (2026-01-09): Social & Attribution Update
- Attribution style changed: Source name early with hyperlink woven into text (not parenthetical at end)
- Phase 4 expanded: Now includes X Article format, single-post options, handles verification table
- Output files: Now creates Social_Media.md AND X_Article_Format.md
- Tools section: Max ONE Reddit post per newsletter; 6-10 tools (down from 10-15)
- Podcast section: Now optional (skip if no episode that week)
-
v2.0 (2025-11-14): MAJOR UPDATE
- Simplified from 8 sections to 6 newsletter sections
- Headers updated: "Trends We're Following" (not "What's Moving")
- Headers updated: "Ed's Stable" (not "Parting Thought")
- Removed: "Listen for the Listeners" and "Reddit Corner" (redundant)
- ADDED: Phase 4 Twitter Thread Strategy ("Ed's Roundup")
- Added comprehensive Twitter handle verification process
- Added tweet structure examples and reference guide
-
v1.0 (Previous): Original 8-section structure with separate Podcast Corner and Reddit Corner
For detailed examples of the current structure, see the reference files folder and the Nov 14, 2025 newsletter implementation.
-
v2.1 (2026-01-09): 社交与归因更新
- 归因风格变更:尽早提及来源名称并自然融入超链接(而非末尾括号引用)
- 阶段4扩展:现在包含X长文格式、单条帖子选项、账号验证表
- 输出文件:现在创建Social_Media.md和X_Article_Format.md
- Tools部分:每期通讯最多包含1个Reddit内容;6-10个工具(从10-15个减少)
- 播客部分:现在为可选(若无本周节目则跳过)
-
v2.0 (2025-11-14): 重大更新
- 从8个章节简化为6个通讯章节
- 标题更新:“Trends We're Following”(替代“What's Moving”)
- 标题更新:“Ed's Stable”(替代“Parting Thought”)
- 移除:“Listen for the Listeners”和“Reddit Corner”(冗余)
- 新增:阶段4 Twitter线程策略(“Ed's Roundup”)
- 新增全面的Twitter账号验证流程
- 新增推文结构示例和参考指南
-
v1.0 (之前): 原始8章节结构,包含独立的Podcast Corner和Reddit Corner
有关当前结构的详细示例,请参阅参考文件文件夹和2025年11月14日的通讯实现。