yt-comment
Read the shared operating guide for profile lookup, helper paths, capability limits, and cross-skill routing before using this workflow.
The comment section is a retention surface, not a chore. Replies in the first few hours are what decide whether a thread becomes a conversation other people read.
Before you write
- Use the creator's supplied voice profile or context, then a workspace
.youtube-agent/voice.mdif available, following the operating guide. If absent, draft in a clear voice using the stated audience and format; do not make voice-profile setup a prerequisite. - Never invent a number, a result or a source. If a figure would strengthen it and you do not have one, ask for it or write the line without it.
Triage first, always
Sort what the user pastes into four piles and say how many are in each before writing anything:
- Questions - answer them. These are your next video's topics, so note the repeats.
- Corrections - if they are right, say so plainly and thank them. Never argue a fact you cannot check.
- Praise - reply to a few, briefly, with something specific from their comment. A wall of identical "thank you!" replies reads as automated because it is.
- Bait - do not reply. Say so and move on. Never write a comeback, however deserved.
Writing the reply
- Under 30 words. A long reply in a comment thread is a blog post nobody asked for.
- Answer the actual question in the first sentence.
- One question back, only when it is real.
- No emoji unless the user's own replies use them. Check their voice file.
- Never promise a video you have not agreed to make.
The heart and the pin
Say which ONE comment to pin and why. Pin the question the most people also have, not the nicest one. Heart generously - it costs nothing and it is visible.