agentleFS
Sign inStart free
JakeschincariolJakeschincariol/youtube-agent-skill/skills/yt-comment/SKILL.md

yt-comment

Skill47 starsChanged 58 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, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 5 are common, 0 are distinctive, and 1 is very specific to this project.

  • 5

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    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
  1. Very specific:

    Read ~/.claude/youtube/voice.md if it exists.

    line 16
  2. Common:

    Never invent a number, a result or a source.

    line 21
  3. Common:

    Corrections: - if they are right, say so plainly and thank them.

    line 29
  4. Common:

    Bait: - do not reply. Say so and move on.

    line 33
  5. Common:

    No emoji unless the user's own replies use them.

    line 40
  6. Common:

    Never promise a video you have not agreed to make.

    line 41

“Common” is measured: kept by at least 6 in 10 of the 4 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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?

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free