YouTube Comment Responder

Yt comment

by Jakeschincariol · MIT license · ★ 1,136 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.

---
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,

Overview

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.

Manual install (npx, ZIP)

Claude Codenpx skills add Jakeschincariol/youtube-agent-skill --skill yt-comment -g -a claude-code

Claude Code (degit)npx degit Jakeschincariol/youtube-agent-skill/skills/yt-comment#main ~/.claude/skills/yt-comment

Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md2.3 KB

Read SKILL.md here

Jakeschincariol/main1 file shown

SKILL.md2.3 KB

Browse every file on GitHub↗

SKILL.md

Show the full text52 lines

yt-comment/SKILL.md52 lines · 2.3 KB

PreviewCode

Outline

RawView on GitHub

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

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.
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.

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?

1	---
2	name: yt-comment
3	description: >-
4	Draft replies to YouTube comments in the creator's voice, triaged by which
5	ones are worth answering. Use for "reply to my comments", "handle the
6	comment section", "someone asked X", or a pasted comment thread.
7	---
8
9	# yt-comment
10
11	The comment section is a retention surface, not a chore. Replies in the first few hours are what
12	decide whether a thread becomes a conversation other people read.
13
14	## Before you write
15
16	1. Read `~/.claude/youtube/voice.md` if it exists. That is the user's voice profile: how they talk
17	on camera, the words they never use, who they are talking to, what they will not claim. If it
18	does not exist, ask for three of their own videos, read or transcribe them, infer the voice,
19	and write the file. A script in the wrong voice is worse than no script, because they have to
20	read it out loud.
21	2. Never invent a number, a result or a source. If a figure would strengthen it and you do not have
22	one, ask for it or write the line without it.
23
24	## Triage first, always
25
26	Sort what the user pastes into four piles and say how many are in each before writing anything:
27
28	1. Questions - answer them. These are your next video's topics, so note the repeats.
29	2. Corrections - if they are right, say so plainly and thank them. Never argue a fact you
30	cannot check.
31	3. Praise - reply to a few, briefly, with something specific from their comment. A wall of
32	identical "thank you!" replies reads as automated because it is.
33	4. Bait - do not reply. Say so and move on. Never write a comeback, however deserved.
34
35	## Writing the reply
36
37	- Under 30 words. A long reply in a comment thread is a blog post nobody asked for.
38	- Answer the actual question in the first sentence.
39	- One question back, only when it is real.
40	- No emoji unless the user's own replies use them. Check their voice file.
41	- Never promise a video you have not agreed to make.
42
43	## The heart and the pin
44
45	Say which ONE comment to pin and why. Pin the question the most people also have, not the nicest
46	one. Heart generously - it costs nothing and it is visible.
47
48	## The gate
49
50	Nothing here publishes. This skill writes and you publish. Every output ends in a block the user
51	copies, and the last line of every run is the question: ship it, or change it?
52