メニュー
Complete YouTube video production pipeline from ideation to distribution. Covers Strategy (Phase 1), Packaging (Phase 2), Scripting (Phase 3), Shorts (Phase 3.5), Production (Phase 4), and Repurposing (Phase 5).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Reuse one Resend account and one verified sender domain across multiple branded products, especially for solo developers and free-tier portfolios. Use when adding transactional email to another app without creating a separate Resend account or verified domain, while preserving per-product identity, recipients, Reply-To routing, templates, security boundaries, delivery reliability, and awareness of a shared sending quota.
Add captions to a talking-head video. ONE catalog (CATALOG.md) of 32 visual identities behind two engines: column-flow (captions composited INTO the scene — matte occlusion + mix-blend; cream/ink/editorial/keynote/documentary/loud/neon/glitch/chrome/velocity) and themed constitutions (anchor/ordnance/terminal/neonsign/stardust/stomp/scoreboard/transit/vhs/arcade/dossier/laser/thunder/hologram/biolume/aurora/spectrum/papercut/popup/chalkboard/graffiti/brush/inkwater/ransom/lastpage/nightcity — e.g. a glyph-decode climax, a neon sign WRITTEN stroke by stroke, or the quiet `anchor` rail default). Route by identity, never by mode. Trigger on "captions/subtitles", "embed/cinematic captions", "VFX captions", "炸/特效/酷炫字幕", a named identity, or top-tier motion-graphics asks. Embedding every word is wrong for most talking-head content — `anchor` is the verbatim default. Pipeline: transcription → hyperframes remove-background matting → HTML render → ffmpeg overlay. Requires hyperframes and a single-subject clip.
turn arbitrary text — an article, notes, a topic, a brief — into a faceless explainer video, up to ~3 min (sweet spot 30-90s), where every visual is invented (typography, abstract graphics, diagrams, data-viz) rather than captured. There is no URL, no website capture, and no real assets. Use this skill for topic explainers, concept breakdowns, how-tos, listicles, and narrative explainers. Do not use it for a product launch/promo (use /product-launch-video), a tour of a real website (use /website-to-video), a GitHub PR (use /pr-to-video), captions on existing footage (use /embedded-captions), or a short unnarrated motion graphic (use /motion-graphics). If the intent is unclear, route through /hyperframes first. This is the shot-sequence architecture: every frame is authored as a time-coded shot sequence picked from a menu of golden blueprints, so frames develop over their full duration instead of freezing after entrance.
Import Figma content into a HyperFrames composition — rendered assets, brand tokens, components, storyboard sections → animatics (REST/CLI), and Figma Motion animations + shaders (MCP). Use when the user pastes a figma.com link or asks to bring a Figma design, frame, logo, brand, or animation into a video/composition.
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). HyperFrames-native: single paused timeline, seek-safe, deterministic.
HyperFrames CLI dev loop. Use when running npx hyperframes init, add, catalog, capture, lint, validate, inspect, layout, snapshot, preview, play, render, publish, lambda, doctor, browser, info, upgrade, skills, compositions, docs, benchmark, telemetry, transcribe, tts, or remove-background, or when troubleshooting the HyperFrames build/render environment. Entry point for AWS Lambda cloud rendering (`hyperframes lambda deploy / render / progress / destroy / policies`).
SOC 職業分類に基づく
| name | youtube-pipeline |
| description | Complete YouTube video production pipeline from ideation to distribution. Covers Strategy (Phase 1), Packaging (Phase 2), Scripting (Phase 3), Shorts (Phase 3.5), Production (Phase 4), and Repurposing (Phase 5). |
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.
| Phase | Workflow | Purpose |
|---|---|---|
| 1 | /youtube-phase1-strategy | Find proven topic via 3-source validation (YT Studio + VidIQ + Google Trends) |
| 2 | /youtube-phase2-packaging | Engineer title & thumbnail |
| 3 | /youtube-phase3-scripting | Write retention-optimized script |
| 3.5 | /youtube-phase3.5-shorts | Create 6 Shorts (3 Topic + 3 Extract) |
| 4 | /youtube-phase4-production | Film, edit, polish |
| 5 | /youtube-phase5-repurposing | Distribute to all platforms (YT, TikTok, IG, LinkedIn) |
| Master | /youtube-pipeline | Orchestrate all 6 phases |
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
Extracts topics and volume indicators from YouTube Studio's Inspiration tab.
User Workflow:
<yta-section id="top-section">.html fileAgent 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 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.
Invoke /youtube-pipeline and follow the prompts. The orchestrator will:
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 platformsWhen running this pipeline, the AI operates as:
Find proven topics using three data sources:
| Source | What to Check | Signal |
|---|---|---|
| YouTube Studio Trends | Inspiration tab → "What people are looking for" | High/Medium volume |
| Competitor VidIQ | Videos 4+ weeks old still getting views/hr | Evergreen topic |
| Google Trends | Explore → YouTube Search → Rising queries | Breakout (5000%+) |
Perfect Storm: When all 3 sources point to the same topic = proven opportunity.
⚠️ Retention Protection: Extract shorts hurt main video retention (viewers skip sections they've seen). Post extract shorts LAST.
| Category | Count | What It Is | When to Post |
|---|---|---|---|
| Topic Shorts | 3 | NEW recordings on the topic | Week 1: Mon/Wed/Fri |
| Extract Shorts | 3 | Sandwich Method clips from main | Week 2: Mon/Wed/Fri |
Topic Short Types:
Sandwich Method (Extract Shorts):
| Layer | Time | What It Is |
|---|---|---|
| Top Bun | 0:00-0:05 | Fresh hook (user records new VO) |
| Meat | 0:05-0:50 | Clip from main video |
| Bottom Bun | 0:50-1:00 | Fresh CTA (user records new VO) |
| Platform | Content | Extra Work |
|---|---|---|
| YouTube | Main + 6 Shorts | None |
| TikTok | Same 6 Shorts | None (repost) |
| Same 6 Shorts (Reels) | None (repost) | |
| 6 Shorts + 3 Text Posts + Stories | Text posts need drafting |
Result: 1 filming session = 7 pieces of content = 2 weeks of distribution across all platforms.
These are embedded in the Phase 3 workflow but summarized here for reference:
| Framework | What 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 Layering | Hit all personality types: D=Results, I=Story, S=Steps, C=Data |
| 30-Second Snap | Reset attention every 30 seconds with visual/energy change |
| Loop Architecture | Open Loop → Content → Payoff → Bridge to next loop |
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:
resources/, add supporting knowledge/prompts if needed, and update this SKILL.md quick reference.scripts/google-trends/search.js, package.json, and pnpm-lock.yaml together.