yt-comment
Skill1 starsChanged 36 days agoMITView on GitHub
Draft replies to YouTube comments in the creator's voice, triaged by which ones are worth answering. Use for "reply to my comments", "handle the comment section", "someone asked X", or a pasted comment thread.
5 other projects use a version of this, 5 of them edited.
Adopted by
Most recently taken up by
- utillayer/youtube-agent-skilledited, first seen Nov 8, 2026
- uplika/uplika-pluginedited, first seen Oct 25, 2026
- swayamdhawan/youtube-agentedited, first seen Oct 15, 2026
- nessalazne/youtube-agent-skilledited, first seen Sep 23, 2026
- Jakeschincariol/youtube-agent-skilledited, first seen Sep 16, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 5
- Jakeschincariol/youtube-agent-skill★ 4770% same
- utillayer/youtube-agent-skill★ 1019% same
- nessalazne/youtube-agent-skill★ 566% same
- uplika/uplika-plugin★ 328% same
- swayamdhawan/youtube-agent★ 070% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- openai/AGENTS.mdAGENTS.md
- llms.txtllms.txt
- yt-analyticsSkill
- yt-auditSkill
- yt-briefSkill
- yt-chaptersSkill
- yt-collabSkill
- yt-editSkill
- yt-endscreenSkill
- yt-funnelSkill
- yt-ideaSkill
- yt-packageSkill
- yt-planSkill
- yt-repurposeSkill
- yt-retentionSkill
- yt-scriptSkill
- yt-seoSkill
- yt-seriesSkill
- yt-shortsSkill
- ytSkill
- yt-sponsorSkill
- yt-thumbnailSkill
- yt-trendSkill
- yt-viralSkill
- yt-voiceSkill
The file
We split this skill into the rules it gives an agent
7 rules. 5 are common, 1 is distinctive, and 1 is very specific to this project.
5
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Read the shared operating guide for profile lookup, helper paths, capability limits, and cross-skill routing before using this workflow.
- Very specific: line 19
Use the creator's supplied voice profile or context, then a local ~/.claude/youtube/voice.md if available, following the operating guide.
- Common: line 22
Never invent a number, a result or a source.
- Common: line 30
Corrections: - if they are right, say so plainly and thank them.
- Common: line 34
Bait: - do not reply. Say so and move on.
- Common: line 41
No emoji unless the user's own replies use them.
- Common: line 42
Never promise a video you have not agreed to make.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 local
~/.claude/youtube/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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.