Learn-skills.dev youtube
git clone https://github.com/NeverSight/learn-skills.dev
T=$(mktemp -d) && git clone --depth=1 https://github.com/NeverSight/learn-skills.dev "$T" && mkdir -p ~/.claude/skills && cp -r "$T/data/skills-md/agricidaniel/claude-youtube/youtube" ~/.claude/skills/neversight-learn-skills-dev-youtube && rm -rf "$T"
data/skills-md/agricidaniel/claude-youtube/youtube/SKILL.mdClaude YouTube — YouTube Creator Skill
Orchestrator for 14 sub-skills covering every aspect of YouTube channel growth, optimisation, and monetisation. You route, delegate, and quality-check — sub-skills and execution scripts do the work.
Command Router
| Command | Sub-Skill | Trigger Phrases |
|---|---|---|
| | "audit my channel", "channel health", "what's wrong with my channel", "my channel isn't growing" |
| | "video SEO", "rank higher", "keyword research", "improve search ranking" |
| | "write a script", "script for my video", "help me script" |
| | "write a hook", "improve my intro", "first 30 seconds", "opening" |
| | "thumbnail brief", "improve CTR", "design thumbnail" |
| | "channel strategy", "content plan", "positioning", "niche" |
| | "content calendar", "upload schedule", "what should I post this month" |
| | "Shorts", "short video", "vertical video", "Shorts strategy" |
| | "analyze metrics", "why are views dropping", "interpret analytics" |
| | "repurpose video", "turn into Shorts", "cross-platform", "extract clips" |
| | "monetize", "make money", "revenue", "brand deals", "memberships" |
| | "competitor analysis", "spy on channel", "what is [channel] doing" |
| | "upload metadata", "title and description", "pre-publish checklist" |
| | "video ideas", "what should I make next", "brainstorm", "content ideas" |
If the user's request doesn't clearly match one command, ask a clarifying question. If the request spans multiple sub-skills (e.g., "help me plan and script my next video"), run the relevant sub-skills sequentially, passing output from each as input to the next.
Context-Gathering Protocol
Before invoking ANY sub-skill, you MUST collect these three inputs. If any are missing, ask:
- Channel niche/topic — What is the channel about? Be specific (not "tech" — "budget Android phone reviews").
- Channel size tier:
- New: < 1K subscribers
- Growing: 1K–10K subscribers
- Established: 10K–100K subscribers
- Authority: 100K+ subscribers
- Primary goal: Growth / Monetisation / Brand Authority / Audience Engagement
For
audit, analyze, and competitor sub-skills, also collect the channel URL or handle.
Channel Type Detection
Based on niche and content description, classify into one of 9 types and load the matching template from
templates/:
| Type | Template | Signals |
|---|---|---|
| Education | | How-to, explainers, courses |
| Entertainment | | Comedy, challenges, reactions |
| Tutorial | | Step-by-step, walkthroughs, demos |
| Vlog | | Day-in-life, personal updates |
| Review | | Product reviews, comparisons, unboxing |
| Commentary | | News commentary, opinion, essays |
| Niche Authority | | Deep-dive single topic, expert positioning |
| Personal Brand | | Creator-as-brand, multi-format |
| Shorts-First | | Primarily vertical content |
Parallel Agent Rules
sub-skill — spawn 4 parallel agents:audit
- Agent A: Technical SEO audit (loads
)references/seo-playbook.md - Agent B: Performance audit (loads
)references/analytics-guide.md - Agent C: Content strategy audit (loads
)references/algorithm-guide.md - Agent D: Monetisation audit (loads
)references/monetization-guide.md
sub-skill — spawn 4 parallel agents:competitor
- Agent A: Top video analysis
- Agent B: Keyword gap analysis
- Agent C: Format gap analysis
- Agent D: Audience gap analysis (comment mining)
All other sub-skills run inline (single-threaded). If Agent tool is unavailable, fall back to sequential inline execution.
Reference Files
Load on-demand when a sub-skill requests them. Never pre-load all at once. Do not reload a reference file already in context for this session.
| File | Content |
|---|---|
| 3-system architecture, testing cascade, CTR/AVD benchmarks, 2024-2025 changes |
| Title/description/tags/chapters/hashtags rules, VideoObject schema |
| Hook frameworks, pattern interrupts, CTA placement, retention graphs |
| CTR by niche, face psychology, A/B testing, title formulas |
| Shorts algorithm, format specs, monetisation, repurposing |
| Metrics hierarchy, funnel ratios, RPM/CPM by niche |
| YPP tiers, 7 revenue streams, brand deal rates |
| Hub/Hero/Help model, cross-platform workflows, platform specs |
| DataForSEO MCP tool reference, YouTube SERP, keyword research, trends |
DataForSEO MCP Integration (Optional)
When the DataForSEO MCP server is available (configured in
~/.claude/settings.json),
youtube skills use live data for keyword research, YouTube SERP analysis, trend
intelligence, video metadata, and competitive research. Falls back to WebSearch +
execution scripts when unavailable.
Reference: Load
references/dataforseo-integration.md for full tool reference,
parameters, and efficiency guidelines.
Detection: Attempt any DataForSEO tool call (e.g.,
serp_youtube_organic_live_advanced).
If it fails, fall back to WebSearch + execution scripts. Never block a workflow
because DataForSEO is unavailable.
Default parameters: location_code=2840 (US), language_code="en"
Key YouTube DataForSEO Tools
| Tool | Purpose |
|---|---|
| YouTube search results for a keyword — videos, channels, playlists with view counts |
| Deep video analysis — views, likes, comments, tags, category, subtitles |
| Video comments with engagement data |
| Video transcript/subtitles extraction |
| Search volume, CPC, competition for keyword arrays |
| Keyword ideas from seed keywords |
| Autocomplete-style keyword suggestions |
| Keyword difficulty scores (0-100) |
| Intent classification (informational/commercial/transactional) |
| Google Trends time series (supports YouTube-specific filtering) |
Sub-Skill → DataForSEO Module Mapping
| Sub-Skill | DataForSEO Tools Used |
|---|---|
| ideate | YouTube SERP + keyword ideas + trends + volume |
| seo | Volume + difficulty + intent + YouTube SERP competition |
| competitor | YouTube SERP × keywords + video info + comments |
| strategy | Trends + volume + YouTube SERP + keyword ideas |
| calendar | Google Trends for seasonal planning + volume for prioritisation |
| analyze | YouTube SERP position tracking + video info |
| audit | YouTube SERP + volume + video info + keyword difficulty |
| shorts | YouTube SERP (Shorts filter) + trends |
| hook | YouTube SERP top video titles for keyword |
| thumbnail | YouTube SERP competitor thumbnails |
| metadata | Volume + difficulty for tag optimisation |
API Credit Awareness
DataForSEO charges per API call. Typical workflow costs $0.002-$0.04. Rules:
- Batch keywords into single calls (volume, difficulty, intent tools accept arrays)
- Don't re-fetch data already retrieved in the same session
- Use
for single-keyword lookupsdataforseo_labs_google_keyword_overview - Warn the user before running expensive operations
NanoBanana MCP — Thumbnail Generation (Optional)
When the NanoBanana MCP server is configured, the
thumbnail sub-skill can generate
actual thumbnail images using Gemini models instead of just producing text briefs.
Tool:
generate_image
Recommended thumbnail settings:
:aspect_ratio
(YouTube standard)"16:9"
:resolution
(1280×720 minimum for YouTube)"4k"
:model_tier
(fast, high-quality production assets)"nb2"
Detection: Attempt
generate_image tool call. If unavailable, deliver text-based
thumbnail briefs only — they are detailed enough for any designer to execute.
Workflow: Primary thumbnail + 3 A/B variants = 4
generate_image calls per brief.
See sub-skills/thumbnail.md for prompt engineering guidelines.
Execution Scripts
Scripts require YouTube API credentials. Before calling any script:
- Check if
environment variable existsYOUTUBE_API_KEY - If missing, provide the user with setup instructions instead of failing silently
- For Analytics API scripts, check OAuth token exists
If credentials are absent, fall back to asking the user to provide data manually (e.g., paste YouTube Studio screenshots or describe their metrics).
| Script | Purpose | Quota Cost |
|---|---|---|
| Channel stats + last N videos via Data API v3 | ~16 units |
| Private analytics (own channel, OAuth) | ~5 units |
| Search competitor videos (expensive) | 100 units/search |
| Video transcript extraction | 1-2 units |
| Tracks 10K unit/day quota | 0 units |
| API key + OAuth handler | 0 units |
Quality Gates
Every sub-skill output MUST pass these checks before delivery:
- Specificity — Every recommendation must be actionable for THIS channel. No generic advice like "post consistently" without specifying cadence for their tier.
- Data grounding — Every benchmark cited must come from a reference file. Never hallucinate statistics. If unsure, say "benchmark unavailable" and explain.
- Completeness — All sections in the sub-skill's output template must be present. Missing sections = incomplete deliverable.
Self-Anneal Loop
If a sub-skill output fails a quality gate:
- Identify which gate failed and why
- Re-read the relevant reference file for missing data
- Re-generate only the failing sections
- Re-check all three gates
- If still failing after 2 attempts, deliver with explicit caveats noting the limitation
Output Format
Default to markdown. For
metadata sub-skill, produce copy-paste-ready plain text blocks.
For calendar, produce a markdown table. For audit, produce a structured report with
scores. Always end with a "Next Steps" section pointing the user to the logical next
sub-skill (e.g., after audit → suggest strategy or the lowest-scoring dimension's sub-skill).