yt-comment — Claude Code skill: what it does, how to install
yt-comment — a skill for Claude Code that drafts YouTube comment replies in the creator's voice. It categorizes incoming feedback and generates concise responses.
MIT 1,200 installs ★ 6,796 updated 2026-09-16
npx skills add Jakeschincariol/youtube-agent-skill --skill yt-comment -a claude-codeWhat yt-comment does
This skill streamlines comment section management by triaging user feedback into questions, corrections, praise, or bait. It drafts replies under 30 words, ensuring they match the creator's tone while avoiding automated-sounding responses. The system does not publish directly; it provides text for the user to copy and review.
For accurate results, the tool relies on a voice profile located at ~/.claude/youtube/voice.md. If this file is missing, the agent must analyze three video transcripts to learn how the creator speaks. It also identifies the most relevant comment to pin, focusing on questions that provide value to other viewers.
What it helps with
- triage YouTube comments efficiently
- draft replies in the creator's voice
- identify comments worth pinning
- filter out bait and spam
Example prompts for the agent
- Draft replies for these comments: [paste comments]
- Handle the comment section for my latest video
- Analyze these comments and suggest one to pin
How to install yt-comment
1Skills CLI (Vercel)
npx skills add Jakeschincariol/youtube-agent-skill --skill yt-comment -a claude-code2Manually: put the files in place
~/.claude/skills/yt-comment/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/yt-comment/
1Skills CLI (Vercel)
npx skills add Jakeschincariol/youtube-agent-skill --skill yt-comment -a codex2Manually: put the files in place
.agents/skills/yt-comment/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Jakeschincariol/youtube-agent-skill --skill yt-comment -a cursor2Manually: put the files in place
.cursor/skills/yt-comment/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Jakeschincariol/youtube-agent-skill skills/yt-comment2Manually: put the files in place
.github/skills/yt-comment/SKILL.md1Skills CLI (Vercel)
npx skills add Jakeschincariol/youtube-agent-skill --skill yt-comment -a gemini-cli2Platform CLI
gemini skills install https://github.com/Jakeschincariol/youtube-agent-skill --path skills/yt-commentManually: put the files in place
.devin/skills/yt-comment/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Jakeschincariol/youtube-agent-skill --skill yt-comment -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about yt-comment
How to install yt-comment in Claude Code?
Run the command npx skills add Jakeschincariol/youtube-agent-skill --skill yt-comment -a claude-code.
What does yt-comment do?
It helps manage YouTube comment sections by sorting feedback and drafting personalized replies while maintaining the creator's voice.
What is required to use yt-comment?
You need a ~/.claude/youtube/voice.md file. If it doesn't exist, provide three video transcripts so the agent can infer your voice.
Source text
SKILL.md · MIT
--- name: yt-comment description: >- 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. --- # yt-comment 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 1. Read `~/.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. 2. 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: 1. **Questions** - answer them. These are your next video's topics, so note the repeats. 2. **Corrections** - if they are right, say so plainly and thank them. Never argue a fact you cannot check. 3. **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. 4. **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. ## The gate 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?**
© Jakeschincariol · MIT · Jakeschincariol/youtube-agent-skill