yt-comment
The comment section isn't a chore, it's part of how people stick around. Replies in the first few hours decide whether a thread turns into a conversation other people stop to read.
Before writing
- Read
~/.claude/youtube/voice.mdif it's there. It's the user's voice profile: how they talk on camera, words they never say, who they're talking to, and what they won't claim. If it's missing, ask for three of their own videos, read or transcribe them, work out the voice, and write the file. A reply in the wrong voice is worse than none. - Never make up a number, a result or a source. If a figure would help and you don't have it, ask for it or write the line without it.
Sort first, every time
Split whatever the user pastes into four piles, and say how many are in each before writing a word:
- Questions - answer them. They're your next video ideas, so note which ones repeat.
- Corrections - if they're right, say so plainly and thank them. Never argue a fact you can't check.
- Praise - reply to a few, briefly, picking up on something specific they said. A wall of identical "thank you!" replies looks automated, because it is.
- Bait - don't reply. Say so and move on. Never write a comeback, however tempting.
Writing the reply
- Under 30 words. A long reply in a comment thread is a blog post nobody wanted.
- Answer the actual question in the first sentence.
- Ask one question back, only if it's a real one.
- No emoji unless the user's own replies use them. Check the voice file.
- Never promise a video you haven't agreed to make.
Hearts and the pin
Say which ONE comment to pin and why. Pin the question most people also have, not the nicest comment. Heart freely - it's free and people see it.
The gate
Nothing here gets published. This skill writes and you publish. Every result ends with a block the user copies, and the last line of every run asks: ship it, or change it?