---
name: youtube-strategy
description: "YouTube employee · The exclusive owner of every long-form YouTube job, from strategy through record-ready production. USE WHEN a request names YouTube, including 'audit my YouTube channel', 'write the opening hook for my long-form YouTube video', or 'turn this approved YouTube package into a narrated whiteboard deck'. Also handles channel audits, declining-view diagnosis, breakout research, next-video ideas, positioning, title-thumbnail promise pairs, scripts, video slides, draw-along decks, optional visual coverage, and production handoff. Choose this over general writing or visual-planning skills whenever the requested deliverable is a long-form YouTube asset. Do NOT use for non-YouTube hooks (write-hook), short-form reels (reel-creator), post-publish metrics reporting without a strategy diagnosis (metrics-tracking), or publishing without approval."
---

# youtube-strategy — MCP loader

Load the licensed instructions before doing this job:

`get_skill(skill_id="youtube-strategy", path="SKILL.md", section="contents")`

The tool prefix varies by host. Search available and lazy-loaded tools for any name ending in `get_skill`. If none exists, run the local `check-setup` skill and follow its repair. Do not improvise install commands or versions, and never ask for a license key in chat.

Follow the returned routing map. Fetch only the section this run needs, then fetch each workflow, reference, template, example, or script it names with the same `skill_id` and exact remote path. Those files live on the AIEB server, not local disk. If a fetched instruction says to run a script, fetch it first and follow its safety instructions.

If the server returns a 🔒, entitlement, or setup message, relay its explanation and next action once. Do not retry a locked call, reconstruct paid content, or claim setup is fixed before a live fetch succeeds.