Agent skill
youtube-companion
Write Substack newsletters that accompany YouTube videos. Use when user has a YouTube video (transcript, outline, or link) and needs the companion newsletter with video embed, summary sections, and resources. Different from standalone newsletters - these drive to and summarize video content.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/youtube-companion
SKILL.md
Load Context First
Before executing this skill, read the following files from the project folder if they exist:
- USER.md — who the user is, how they think, how they work, what they care about
- BUSINESS.md — their business, products, positioning, brand voice, content strategy, social links, sign-off
- ICP.md — their ideal customer, their language, their fears, what makes them buy
- Voice or brand voice skill — look for any installed skill related to voice, tone, or brand voice and apply it automatically
- Any additional context provided by the user in this session
Use all of this context silently to inform everything you produce. Do not reference or summarize the files unless asked.
YouTube Companion Newsletter
Write a concise Substack newsletter that accompanies a YouTube video. The newsletter hooks readers, tells them what they'll learn, links to paid resources, and gets out of the way. It drives to the video — it does NOT replace it.
Voice
Apply any voice or brand voice skill if installed. Otherwise pull tone direction from BUSINESS.md. If neither is available: direct, confident, no fluff. Write like the smart friend who figured this out, not a guru or a marketer.
Input
Accepts a transcript, outline, or notes from a YouTube video. Extract:
- Video topic — what's being shown
- Key outcomes — what viewers will learn/be able to do (5-6 max)
- Resources — any downloads, plugins, starter kits mentioned
- One-liner hook — why this matters right now
Output Structure
The newsletter has exactly these sections in this order:
# [Video Title]
### 💎 RESOURCE: [Short resource name]
_**Paid members:** All assets from my videos and guides—starter kits, prompts, skills, agents—are available for paid members._
---
---
[2-3 sentence setup. What shipped/changed, what you cover in the video, why it matters. Get to the point fast.]
[Optional: "In this video, I walk through everything — [thing], [thing], and [thing]."]
By the end, you'll have:
- **[Outcome 1]** — brief clarification
- **[Outcome 2]** — brief clarification
- **[Outcome 3]** — brief clarification
- **[Outcome 4]** — brief clarification
- **[Outcome 5]** — brief clarification
[One-liner kicker. Something like "If you've been using X, pay attention. This might change your setup."]
---
### **💎 GRAB YOUR RESOURCE: [Resource name]**
[1-2 sentences describing the resource.]
[CLICK HERE FOR THE RESOURCE](link placeholder)
What's inside:
- **[Item 1]** — what it does
- **[Item 2]** — what it does
- **[Item 3]** — what it does
- **[Item 4]** — what it does
[1 sentence on how to use it.]
---
[2-3 sentence closer. Acknowledge it's early/new if relevant. Reinforce the direction. Tell them to start now.]
_—[Name from BUSINESS.md or USER.md]_
**Stay connected**
[Social links from BUSINESS.md]
Rules
- Total length: 400-600 words. This is not a long-form piece. It's a companion.
- No "Why [topic]?" section. The setup paragraph handles this in 2-3 sentences.
- No "What's in the video" table. The bullet list of outcomes covers it.
- No "Key concepts" section. That's what the video is for.
- No "Start here" steps. The resource section IS the action.
- No subject line options block. Just write the title.
- Resource callout appears twice — once at the very top (teaser) and once in the middle (full breakdown with link).
- Double horizontal rules (
---\n\n---) after the paid member callout. - Outcomes list uses bold + dash clarification. Keep clarifications to one line.
- Closer is 2-3 sentences max. Sign off with the user's name from their context files.
- Tone is direct and practical. No hype, no "game-changer," no "unlock the power of."
What NOT to Do
- Don't write a full tutorial — the video does that
- Don't add sections that aren't in the template above
- Don't pad with "why this matters" paragraphs — the setup covers it
- Don't use tables — use bullet lists
- Don't write more than 600 words
- Don't add meta-commentary like word counts or stats at the end
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?