mcpField
Y
youtube-pipeline

youtube-pipeline

github.com/j-star-films-studiosCreative & media26101 installsUpdated 2w ago
Repository

About youtube-pipeline

youtube-pipeline is a self-contained skill for planning, producing, and distributing YouTube videos. Creators can run the full workflow or start at a single phase, with bundled research workflows, prompts, and scripts.

Key features

  1. 01Six-phase video production workflow
  2. 02Three-source topic validation
  3. 03Title and thumbnail planning
  4. 04Long-form scripts and Shorts
  5. 05Cross-platform content repurposing
  6. 06Bundled research scripts

Use cases

  1. 01Validate a video topic before production
  2. 02Plan titles, thumbnails, and scripts
  3. 03Create Shorts from a main video
  4. 04Adapt content for multiple platforms

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/j-star-films-studios/vibecode-protocol-suite --skill youtube-pipeline

After installing, type/youtube-pipelinein Claude Code to confirm it loaded.

Details

From the project README

YouTube Pipeline Skill

This skill provides access to a complete YouTube video production pipeline. It is self-contained: when activated, resolve the folder containing this SKILL.md as <skill-root> and read the bundled workflow, knowledge, prompt, and script files from there.

Quick Reference

PhaseWorkflowPurpose
1/youtube-phase1-strategyFind proven topic via 3-source validation (YT Studio + VidIQ + Google Trends)
2/youtube-phase2-packagingEngineer title & thumbnail
3/youtube-phase3-scriptingWrite retention-optimized script
3.5/youtube-phase3.5-shortsCreate 6 Shorts (3 Topic + 3 Extract)
4/youtube-phase4-productionFilm, edit, polish
5/youtube-phase5-repurposingDistribute to all platforms (YT, TikTok, IG, LinkedIn)
Master/youtube-pipelineOrchestrate all 6 phases

Bundled Files (Always Read These First)

All runtime instructions are bundled in this skill. Do not require the user's vault, a global config folder, or a specific agent harness for normal use.

Workflow Files:

<skill-root>/resources/youtube-pipeline.md
<skill-root>/resources/youtube-phase1-strategy.md
<skill-root>/resources/youtube-phase2-packaging.md
<skill-root>/resources/youtube-phase3-scripting.md
<skill-root>/resources/youtube-phase3.5-shorts.md
<skill-root>/resources/youtube-phase4-production.md
<skill-root>/resources/youtube-phase5-repurposing.md

Knowledge And Prompts:

<skill-root>/resources/knowledge/
<skill-root>/resources/prompts/

Automation Scripts (Phase 1):

<skill-root>/scripts/parse_yt_studio.ps1
<skill-root>/scripts/google-trends/search.js

Phase 1 Automation Tools

YouTube Studio HTML Parser

Extracts topics and volume indicators from YouTube Studio's Inspiration tab.

User Workflow:

  1. Go to YouTube Studio → Inspiration → Search topic
  2. Right-click results → Inspect → Find <yta-section id="top-section">
  3. Right-click → Copy → Copy outerHTML
  4. Paste into .html file

Agent Command:

$SkillRoot = "<path-to-installed-youtube-pipeline-skill>"
powershell -ExecutionPolicy Bypass -File (Join-Path $SkillRoot "scripts/parse_yt_studio.ps1") -InputFile "topic.html" -OutputFile "parsed.md"
Google Trends Research

Google Trends validation is required. This skill bundles the local google-trends Node CLI so agents can run trends checks without relying on a separate global skill install.

First-Time Setup:

$SkillRoot = "<path-to-installed-youtube-pipeline-skill>"
$TrendRoot = Join-Path $SkillRoot "scripts/google-trends"
Push-Location $TrendRoot
pnpm install
Pop-Location

Agent Command:

$SkillRoot = "<path-to-installed-youtube-pipeline-skill>"
node (Join-Path $SkillRoot "scripts/google-trends/search.js") -k "Claude Cowork" -p youtube -t "now 7-d"

If Node dependencies are unavailable, use the manual Google Trends workflow in resources/youtube-phase1-strategy.md. Do not assume a Gemini, Codex, Pi, or other harness-specific path.

How to Use This Skill

Option 1: Full Pipeline

Invoke /youtube-pipeline and follow the prompts. The orchestrator will:

  1. Ask where you're starting
  2. Chain through all 6 phases
  3. Track state across phases
Option 2: Single Phase

Jump directly to any phase:

  • /youtube-phase1-strategy — Just need a topic (uses 3-source validation)
  • /youtube-phase2-packaging — Just need title/thumbnail
  • /youtube-phase3-scripting — Just need a script
  • /youtube-phase3.5-shorts — Create 6 Shorts from a video
  • /youtube-phase4-production — Just need production guidance
  • /youtube-phase5-repurposing — Distribute to all platforms

AI Persona: The Brutal Expert

When running this pipeline, the AI operates as:

  • Never yes-mans. Weak ideas get called out.
  • Demands proof. "This video is viral" → "Show me the view:sub ratio."
  • Generates outputs. AI generates titles, hooks, thumbnail concepts for user to pick from.
  • Teaches the why. Every step includes the reasoning behind it.
  • Challenges weak work. "That hook is mid. Try this instead..."

Phase 1: 3-Source Research Validation

Find proven topics using three data sources:

SourceWhat to CheckSignal
YouTube Studio TrendsInspiration tab → "What people are looking for"High/Medium volume
Competitor VidIQVideos 4+ weeks old still getting views/hrEvergreen topic
Google TrendsExplore → YouTube Search → Rising queriesBreakout (5000%+)

Perfect Storm: When all 3 sources point to the same topic = proven opportunity.


Phase 3.5: 6 Shorts System (Topic + Extract)

⚠️ Retention Protection: Extract shorts hurt main video retention (viewers skip sections they've seen). Post extract shorts LAST.

CategoryCountWhat It IsWhen to Post
Topic Shorts3NEW recordings on the topicWeek 1: Mon/Wed/Fri
Extract Shorts3Sandwich Method clips from mainWeek 2: Mon/Wed/Fri

Topic Short Types:

  1. Hot Take — Spicy opinion on the topic
  2. Quick Win — One actionable tip
  3. Story Hook — Personal story as teaser

Sandwich Method (Extract Shorts):

LayerTimeWhat It Is
Top Bun0:00-0:05Fresh hook (user records new VO)
Meat0:05-0:50Clip from main video
Bottom Bun0:50-1:00Fresh CTA (user records new VO)

Phase 5: Repurposing & Distribution

PlatformContentExtra Work
YouTubeMain + 6 ShortsNone
TikTokSame 6 ShortsNone (repost)
InstagramSame 6 Shorts (Reels)None (repost)
LinkedIn6 Shorts + 3 Text Posts + StoriesText posts need drafting

Result: 1 filming session = 7 pieces of content = 2 weeks of distribution across all platforms.


Key Frameworks (Phase 3 Scripting)

These are embedded in the Phase 3 workflow but summarized here for reference:

FrameworkWhat It Does
Ego Trap Hook"You think [X] is helping you, but it's actually why you're failing"
Cost of Inaction"If you ignore this, you'll keep [Pain] while others [Gain]"
DISC LayeringHit all personality types: D=Results, I=Story, S=Steps, C=Data
30-Second SnapReset attention every 30 seconds with visual/energy change
Loop ArchitectureOpen Loop → Content → Payoff → Bridge to next loop

Updating This Skill

The files in resources/ are the packaged source used at runtime. If you refresh them from another workspace, copy into this skill folder and keep all references relative to <skill-root>.

To Sync (PowerShell):

$SkillRoot = "<path-to-installed-youtube-pipeline-skill>"
$ExternalWorkflowDir = "<path-to-external-workflow-source>"
$ExternalKnowledgeDir = "<path-to-external-knowledge-source>"
$ExternalPromptDir = "<path-to-external-prompt-source>"

Copy-Item -Path (Join-Path $ExternalWorkflowDir "youtube-*.md") -Destination (Join-Path $SkillRoot "resources") -Force
Copy-Item -Path (Join-Path $ExternalKnowledgeDir "*.md") -Destination (Join-Path $SkillRoot "resources/knowledge") -Force
Copy-Item -Path (Join-Path $ExternalPromptDir "*.md") -Destination (Join-Path $SkillRoot "resources/prompts") -Force

When to Sync:

  • After updating any external workflow, processed note, or prompt source.
  • To add new phases, add the workflow to resources/, add supporting knowledge/prompts if needed, and update this SKILL.md quick reference.
  • If the Google Trends CLI changes, refresh scripts/google-trends/search.js, package.json, and pnpm-lock.yaml together.
  • After syncing, run a reference check for absolute local paths and harness-specific install paths.

Comments

Markdown supported