analyze-team-session
Use when reviewing an agent team session export for quality, when asked to "analyze this team session", "review my agent team…
Repurpose a newsletter issue into a high-level YouTube video outline. Use when asked to "create a YouTube outline from this newsletter", "turn this newsletter into a video", "repurpose for YouTube", "video outline from newsletter", or when converting any newsletter issue into
$ npx -y skills add kenneth-liao/ai-launchpad-marketplace --skill newsletter-to-video --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/newsletter-to-videoContext preview
The summary Claude sees to decide when to auto-load this skill.
Repurpose a newsletter issue into a high-level YouTube video outline. Use when asked to "create a YouTube outline from this newsletter", "turn this newsletter into a video", "repurpose for YouTube", "video outline from newsletter", or when converting any newsletter issue into
name: newsletter-to-video description: Repurpose a newsletter issue into a high-level YouTube video outline. Use when asked to "create a YouTube outline from this newsletter", "turn this newsletter into a video", "repurpose for YouTube", "video outline from newsletter", or when converting any newsletter issue into video format.
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.
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.
Use this skill when:
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";
}Read the full newsletter issue. Identify:
**Drop these** — they don't translate to video:
**Promote these** — they work better on video than in text:
**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.
**Invoke `creator-stack:hook`** to craft the video's opening hook.
Feed the skill this context from Steps 1–2:
The skill will produce a hook that:
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.
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.
## Hook (0:00–0:15) [Generated by creator-stack:hook skill — 2-3 sentences describing the opening: what the viewer sees/hears, the hook pattern used, and the curiosity it creates] ## Setup [What context the viewer needs to understand the rest — 1 sentence] ## 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.] ## 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.
Present
A curated collection of Claude Code plugins to unlock your personal workflows.
Use when reviewing an agent team session export for quality, when asked to "analyze this team session", "review my agent team…
Generate a self-contained HTML viewer for any Claude Code session, including agent team sessions with full inter-agent DM…
Define, codify, or update brand identity and connect it to design systems. Use when the user wants to create brand guidelines,…
Create YouTube community posts that drive views and audience engagement. Use when asked to create a community post, promote a…
Create, update, or refresh a visual design system or art style guide. Use when the user wants to define a visual style, create a…
Extract structured content ideas from published material. Use when you have source material (transcripts, newsletters, notes, web…