newsletter-to-video
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseNewsletter to YouTube Video Outline
通讯转YouTube视频大纲
Repurpose a newsletter issue into a high-level YouTube video outline. The output is topic-level only — no scripts, no talking points, no actual content. Just the topics you'll cover, structured for video.
将一期通讯改造为高层面的YouTube视频大纲。输出仅为主题层级内容——不包含脚本、话术要点、实际正文内容,仅列出你将要覆盖的主题,按视频适配的结构组织。
Why This Exists
设计初衷
Newsletter and YouTube are different mediums. Newsletters reward scanners — readers jump to what interests them. YouTube rewards retention — viewers watch linearly, and every moment competes with the back button. A straight 1:1 port of newsletter structure usually makes for a boring video. This skill restructures the content to match how people actually watch.
通讯和YouTube是不同的内容媒介。通讯适合快速浏览的读者——读者可以直接跳转到自己感兴趣的内容。YouTube则看重留存率——观众是线性观看的,每一秒都在和返回按钮竞争。直接1:1照搬通讯的结构通常会做出很无聊的视频。本技能会重构内容结构,适配用户实际的观看习惯。
When to Use
适用场景
Use this skill when:
- Converting a newsletter issue into a YouTube video plan
- The user asks to repurpose newsletter content for YouTube
- Planning a video based on an existing newsletter issue
- The user mentions "video outline from newsletter" or similar
当出现以下情况时使用本技能:
- 将一期通讯转换为YouTube视频策划
- 用户要求将通讯内容二次创作适配YouTube
- 基于已有的通讯内容策划视频
- 用户提到「从通讯生成视频大纲」或类似表述
Process
流程
dot
digraph newsletter_to_youtube {
"Read newsletter issue" [shape=doublecircle];
"Extract core topics" [shape=box];
"Identify the tension" [shape=box];
"Drop non-video sections" [shape=box];
"Reorder for retention" [shape=box];
"Generate hook via skill" [shape=box, style=bold];
"Structure the outline" [shape=box];
"Present to user" [shape=doublecircle];
"Read newsletter issue" -> "Extract core topics";
"Extract core topics" -> "Identify the tension";
"Identify the tension" -> "Drop non-video sections";
"Drop non-video sections" -> "Reorder for retention";
"Reorder for retention" -> "Generate hook via skill";
"Generate hook via skill" -> "Structure the outline";
"Structure the outline" -> "Present to user";
}dot
digraph newsletter_to_youtube {
"Read newsletter issue" [shape=doublecircle];
"Extract core topics" [shape=box];
"Identify the tension" [shape=box];
"Drop non-video sections" [shape=box];
"Reorder for retention" [shape=box];
"Generate hook via skill" [shape=box, style=bold];
"Structure the outline" [shape=box];
"Present to user" [shape=doublecircle];
"Read newsletter issue" -> "Extract core topics";
"Extract core topics" -> "Identify the tension";
"Identify the tension" -> "Drop non-video sections";
"Drop non-video sections" -> "Reorder for retention";
"Reorder for retention" -> "Generate hook via skill";
"Generate hook via skill" -> "Structure the outline";
"Structure the outline" -> "Present to user";
}Step 1: Read the Newsletter Issue
步骤1:阅读通讯内容
Read the full newsletter issue. Identify:
- The core thesis (what's the one main idea?)
- All distinct topics/subtopics covered
- The most surprising or counterintuitive finding
- Any limitations, trade-offs, or honest takes (these create tension)
- Personal experience and real results (these build credibility on camera)
通读完整的通讯内容,识别以下信息:
- 核心论点(核心主旨是什么?)
- 所有覆盖的独立主题/子主题
- 最让人意外或反常识的发现
- 任何局限性、权衡取舍或真实评价(这些内容可以制造冲突感)
- 个人经验和实际成果(这些内容可以在镜头前建立可信度)
Step 2: Adapt for Video
步骤2:适配视频形式
Drop these — they don't translate to video:
- P.S. lines and email-specific CTAs (forward, reply)
- Preview text / subtitle
- Subject line options
- "Getting started" setup sections (install steps, config JSON) — unless the video is a tutorial
- Sections that only work as scannable text (comparison tables can become talking points, but raw tables don't work on screen)
Promote these — they work better on video than in text:
- Personal stories and anecdotes (these are gold on camera)
- Surprising findings or limitations (great for hooks and retention)
- Before/after comparisons (visual, easy to demonstrate)
- Live demos or walkthroughs (newsletter screenshots become video demos)
Reorder for retention:
YouTube viewers decide to stay or leave in the first 30 seconds. The newsletter hook might work as-is, but often the most interesting finding is buried in the middle or end of the newsletter. Pull it forward.
| Newsletter pattern | Video adaptation |
|---|---|
| Hook → Context → Content → Limitation → Close | Hook with the limitation → Why it matters → How it works → Limitation deep-dive → What's next |
| Hook → Problem → Solution → How-to → Close | Hook with the result → The problem → The solution → Quick demo → What's next |
| Hook → Feature overview → Cost → Limitations → Close | Hook with the tension (cost/limitation) → What it does → How it actually works → The honest trade-offs → Verdict |
The general principle: lead with tension or surprise, deliver value in the middle, end forward-looking. Tension is what keeps viewers watching. The newsletter can afford a slow build because readers scan ahead. Video can't.
删掉以下内容——它们不适合视频呈现:
- 附言(P.S.)和邮件专属CTA(转发、回复)
- 预览文本/副标题
- 主题线备选项
- 「入门」相关的设置环节(安装步骤、配置JSON)——除非视频本身是教程
- 仅适合快速浏览的文本类内容(对比表可以改成话术要点,但原始表格不适合出现在视频画面中)
突出以下内容——它们在视频中的呈现效果比文本更好:
- 个人故事和轶事(是镜头前的优质素材)
- 意外发现或局限性(非常适合做钩子和提升留存)
- 前后对比(可视化强,容易展示)
- 实时演示或操作引导(通讯里的截图可以改成视频演示)
为提升留存调整顺序:
YouTube观众会在开头30秒内决定要不要继续看。通讯的钩子可能可以直接用,但通常最有趣的内容会藏在通讯的中间或者末尾,要把它提前。
| 通讯结构 | 视频适配结构 |
|---|---|
| 钩子→背景→内容→局限性→结尾 | 用局限性做钩子→重要性说明→运作原理→局限性深挖→后续展望 |
| 钩子→问题→解决方案→操作指南→结尾 | 用成果做钩子→问题说明→解决方案→快速演示→后续展望 |
| 钩子→功能概览→成本→局限性→结尾 | 用冲突点(成本/局限性)做钩子→功能说明→实际运作原理→真实取舍分析→最终结论 |
通用原则:以冲突点或意外内容开篇,中间传递价值,结尾面向未来。 冲突感是让观众持续观看的核心。通讯可以接受慢热铺垫,因为读者会快速扫读后面的内容,但视频不行。
Step 3: Generate the Hook
步骤3:生成钩子
Invoke to craft the video's opening hook.
content-strategy:hookFeed the skill this context from Steps 1–2:
- The working title (or a placeholder title describing the video topic)
- The most surprising or counterintuitive finding from the newsletter — this is almost always the best hook material
- The core tension (limitation, trade-off, honest take) identified in Step 1
- The content type (YouTube video) so the skill loads
references/youtube-hooks.md
The skill will produce a hook that:
- Extends curiosity beyond the title (doesn't just repeat it)
- Lands within 5–15 seconds
- Avoids forbidden patterns (title repetition, welcome-first, unrelated tangent)
- Passes its own 7-point verification checklist
Include the skill's hook output in the outline's Hook section. The hook should be 2–3 sentences: what the viewer sees/hears and why it creates urgency to keep watching.
调用来制作视频的开篇钩子。
content-strategy:hook把步骤1-2得到的以下信息输入给该技能:
- 暂定标题(或描述视频主题的占位标题)
- 通讯里最让人意外或反常识的发现——这几乎都是最好的钩子素材
- 步骤1里识别出的核心冲突点(局限性、权衡取舍、真实评价)
- 内容类型(YouTube视频),这样技能会加载
references/youtube-hooks.md
该技能会生成符合以下要求的钩子:
- 激发超出标题的好奇心(不会单纯重复标题)
- 时长控制在5-15秒内
- 规避禁用模式(重复标题、开篇先问候、无关跑题)
- 通过自身的7项验证 checklist
把技能生成的钩子放到大纲的「钩子」部分。钩子需要2-3句话:说明观众看到/听到的内容,以及它激发观众继续观看的紧迫感的原因。
Step 4: Build the Outline
步骤4:搭建大纲
Structure every outline with these sections. The Hook section comes from Step 3. The rest is topic-level only — 1-2 lines per section, not actual content.
undefined所有大纲都按以下板块组织。钩子部分来自步骤3,其余部分仅为主题层级——每个板块1-2行描述,不要写实际内容。
undefinedHook (0:00–0:15)
钩子 (0:00–0:15)
[Generated by content-strategy:hook skill — 2-3 sentences
describing the opening: what the viewer sees/hears, the hook pattern used,
and the curiosity it creates]
[由content-strategy:hook技能生成——2-3句话描述开篇内容:
观众看到/听到的内容、使用的钩子模式、激发的好奇心点]
Setup
背景铺垫
[What context the viewer needs to understand the rest — 1 sentence]
[观众理解后续内容需要的背景信息——1句话]
Main Topics
核心主题
[Each topic as a bullet — just the topic name and what aspect of it you'll cover]
- Topic 1: ...
- Topic 2: ...
- Topic 3: ... [Usually 3-5 topics. More than 5 means the video is trying to cover too much.]
[每个主题用 bullet 列出——仅写主题名称和你会覆盖的角度]
- 主题1:...
- 主题2:...
- 主题3:... [通常为3-5个主题,超过5个说明视频覆盖的内容太多了]
Close
结尾
[How the video wraps — what the viewer should take away or do next]
Keep it tight. The outline for a 10-minute video should fit in under 15 lines (excluding the hook). If you're writing more than that, you're going past topic-level into content territory.[视频的收尾方式:观众应该带走的收获或下一步行动]
保持内容精简。10分钟视频的大纲(不含钩子)应该控制在15行以内。如果写得更多,说明你已经超出主题层级,进入内容细节了。Output Format
输出格式
Present the outline as a single markdown block. Use the template structure above. No commentary outside the outline unless the user asks for it.
If a newsletter issue covers too many topics for one video, say so and suggest splitting into 2 videos with a recommended split point — but still produce the outline for the primary video.
把大纲放在单个Markdown块中,使用上面的模板结构。除非用户要求,否则不要在大纲外添加任何评论。
如果一期通讯覆盖的主题太多,单条视频放不下,要说明情况并建议拆分为2条视频,给出推荐的拆分点——但仍然要输出主视频的大纲。
Brand Compliance
品牌合规
When creating video outlines for The AI Launchpad, invoke to verify the hook and outline align with brand standards.
branding-kit:brand-guidelines为The AI Launchpad制作视频大纲时,调用验证钩子和大纲符合品牌标准。
branding-kit:brand-guidelinesQuality Checklist
质量检查清单
Verify completion before finalizing:
- Newsletter issue fully read and core thesis identified
- Non-video sections dropped (P.S., subject lines, setup steps)
- Video-friendly elements promoted (stories, demos, surprises)
- Content reordered for retention (tension/surprise leads)
- invoked for hook generation
content-strategy:hook - Hook passes the skill's 7-point verification checklist
- Outline uses the template structure (Hook → Setup → Main Topics → Close)
- 3-5 main topics (not more)
- Each topic is a label + angle, not talking points
- Outline fits under 15 lines (excluding hook)
最终输出前确认完成以下事项:
- 已通读完整通讯,识别出核心论点
- 已删掉不适合视频的板块(附言、主题线、设置步骤)
- 已突出适合视频的元素(故事、演示、意外内容)
- 已为提升留存调整内容顺序(冲突点/意外内容放在开头)
- 已调用生成钩子
content-strategy:hook - 钩子已通过技能的7项验证checklist
- 大纲使用模板结构(钩子→背景铺垫→核心主题→结尾)
- 核心主题为3-5个(不会更多)
- 每个主题都是「标签+角度」的形式,不是话术要点
- 大纲(不含钩子)控制在15行以内
Common Mistakes
常见错误
| Mistake | Fix |
|---|---|
| Writing talking points instead of topics | Each bullet should be a topic label + angle, not what you'd say about it |
| Mirroring the newsletter order exactly | Reorder — lead with whatever creates the most tension or curiosity |
| Including 7+ main topics | Pick 3-5. A focused video outperforms a comprehensive one. |
| Keeping email-specific sections | Drop P.S., subject lines, reply CTAs — they don't exist in video |
| Writing the hook inline instead of using the skill | Invoke |
| Generic hook ("Today we're going to talk about...") | The hook skill will prevent this — feed it the tension/surprise and let it pick the right pattern |
| Forgetting the close | Every video needs a clear ending — verdict, next steps, or a forward look |
| 错误 | 修复方案 |
|---|---|
| 写话术要点而不是主题 | 每个bullet应该是主题标签+角度,而不是你要说的具体内容 |
| 完全照搬通讯的内容顺序 | 重新排序——把最能制造冲突感或好奇心的内容放在开头 |
| 包含7个以上的核心主题 | 选3-5个即可,聚焦的视频表现比大而全的视频更好 |
| 保留邮件专属板块 | 删掉附言、主题线、回复CTA——它们在视频里没有意义 |
| 手动写钩子而不使用技能 | 调用 |
| 钩子太泛(比如「今天我们要聊一下...」) | 钩子技能会避免这个问题——输入冲突点/意外内容,让它选择合适的模式 |
| 忘记写结尾 | 每条视频都需要清晰的收尾——结论、下一步行动或者未来展望 |