executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
yt-seoWrite the description, tags and search-facing text for a YouTube video, aimed at the query a real person types. Use for "write my description", "tags", "SEO", "help this video get found", "nobody is finding this".
Independent GitHub snapshot · Automated classification · Original documentation governs
Search is a smaller lever than packaging and a bigger one than people think for evergreen videos.
For a video aimed at the subscriber feed, say so and spend the effort on /yt-package instead.
~/.claude/youtube/voice.md if it exists. That is the user's voice profile: how they talk
on camera, the words they never use, who they are talking to, what they will not claim. If it
does not exist, ask for three of their own videos, read or transcribe them, infer the voice,
and write the file. A script in the wrong voice is worse than no script, because they have to
read it out loud./yt-chapters writes them).Tags are a weak signal and YouTube has said so. Use them for disambiguation - spellings, the tool names, the abbreviations people actually type - and stop. Fifteen is plenty. A wall of tags is not a strategy and stuffing unrelated ones is against the terms.
Before handing anything over, write the three search queries this video should win, and check the title and first two description lines contain the words in those queries. If they do not, the problem is the title, not the description.
Nothing here publishes. This skill writes and you publish. Every output ends in a block the user copies, and the last line of every run is the question: ship it, or change it?