youtube-strategy
YouTube Strategy Skill
This skill helps with YouTube video creation from ideation through publishing. It covers the full workflow: validating ideas, crafting packaging (title + thumbnail + hook as a unified unit), and creating post-production elements like descriptions and pinned comments.
How to Use This Skill
1. Identify the User's Stage
Before pulling in resources, determine where the user is in their process:
| Stage | User Signals | Primary Resources |
|---|---|---|
| Ideation | "I have an idea", "thinking about making a video", "should I make this?" | ideation.md |
| Packaging | "help with title", "thumbnail ideas", "working on my hook" | titles.md, thumbnail.md, hook.md (use together) |
| Scripting | "help with script", "structure the video", "how to keep viewers engaged" | scripting.md, hook.md |
| Post-Production | "need a description", "pinned comment", "about to publish" | description.md, pinned-comment.md |
If unclear, ask: "Are you still exploring the idea, or do you have a video ready to package?"
2. The Packaging Contract (Critical)
Title, thumbnail, and hook are ONE unit. They form a contract with the viewer:
- Title + Thumbnail make a promise that creates curiosity
- Hook (first 20 seconds) must deliver on that promise immediately
When helping with ANY packaging element, consider all three:
- If working on a title, ask about the thumbnail concept and hook
- If the hook doesn't pay off the title/thumbnail promise, flag it
- Never finalize one without considering how it connects to the others
3. The Differentiation Filter
Before committing to packaging, apply this test from ideation.md:
"Would you spend $1,000 making this video? If not, find a more differentiated angle."
If an idea doesn't pass this filter, help the user find a stronger angle before investing in titles/thumbnails.
4. Audience Consistency
All videos should target the same precise audience avatar. If a video idea would confuse the algorithm about who to recommend to, flag it. Reference ideation.md for audience avatar guidance.
Resources by Topic
Ideation & Validation resources/ideation.md
- Audience avatar definition
- The differentiation test
- Idea validation before production
Titles resources/titles.md
- Title formulas and patterns
- Checklist before publishing
Thumbnail resources/thumbnail.md
- Visual design principles
- Technical content templates
- The 3-element rule
The Hook resources/hook.md
- The 20-second formula (0-5s, 5-12s, 12-20s)
- Click confirmation principle
- Hook templates by type
Scripting resources/scripting.md
- Anticipation-validation loops (the "seesaw" pattern)
- Head fakes and misdirection techniques
- Script structures for technical content
- Pacing and retention strategies
Description resources/description.md
- SEO structure
- Template for technical content
Pinned Comment resources/pinned-comment.md
- Five comment types
- When to use each
Viral Checklist resources/viral-checklist.md
- Pre-publish gut check
Workflow Summary
IDEATION
↓
Is the idea differentiated? (Would you spend $1,000?)
Does it serve your audience avatar?
↓
PACKAGING (as one unit)
↓
Title + Thumbnail + Hook must form a coherent contract
The promise made must be delivered in first 20 seconds
↓
SCRIPTING
↓
Structure using anticipation-validation loops
Use head fakes to maintain engagement
Every ~3 min should have tension or release
↓
POST-PRODUCTION
↓
Description, Pinned Comment, Final Checks
When in doubt, start earlier in the workflow. A weak idea with great packaging still underperforms.
More from dgalarza/claude-code-workflows
tdd-workflow
Use this skill whenever you are implementing a feature using TDD.
38process-meeting-transcript
Process raw meeting transcripts from Granola or other sources into structured notes with frontmatter, action items, summary, and formatted transcript. Use this skill when the user asks to process a meeting transcript or provides a raw transcript that needs formatting.
38conventional-commits
This skill should be used when creating Git commits to ensure they follow the Conventional Commits specification. It provides guidance on commit message structure, types, scopes, and best practices for writing clear, consistent, and automated-friendly commit messages. Use when committing code changes or reviewing commit history.
31linear-implement
This skill should be used when implementing features from Linear issues with full TDD workflow, automated planning, parallel code reviews (security and Rails best practices), systematic feedback implementation, and automated PR creation with Linear integration. Use when the user provides a Linear issue ID (e.g., "TRA-9", "DEV-123") and wants a complete implementation workflow from issue to PR.
29rspec-testing
This skill should be used when writing, reviewing, or improving RSpec tests for Ruby on Rails applications. Use this skill for all testing tasks including model specs, controller specs, system specs, component specs, service specs, and integration tests. The skill provides comprehensive RSpec best practices from Better Specs and thoughtbot guides.
19parallel-code-review
This skill should be used when performing comprehensive code reviews using multiple specialized review agents in parallel. It provides patterns for concurrent execution, decision tracking to prevent redundancy, and consolidated reporting. Use when needing thorough review coverage from multiple perspectives (security, architecture, performance) or when reviewing large changesets.
19