agentleFS
mategogmategog/mateai-youtube-mcp/skills/yt-title-lint/SKILL.md

yt-title-lint

Skill1 starsChanged 12 days agoApache-2.0View on GitHub

Lint a YouTube title and thumbnail text as one pairing before publish: truncation, duplication, vagueness. Use only when the user wants a title or thumbnail CHECKED or scored ("lint this title", "is this title too long", "does the thumbnail repeat the title"). To come up with titles and thumbnail concepts, use yt-packaging instead.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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 23
  2. Distinctive:

    Never invent a number, a result or a source.

    line 28
  3. Distinctive:

    Two all-caps words is the ceiling: before a title reads as spam.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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-title-lint

The title and the thumbnail are ONE unit. Writing them separately is why most packaging fails: the thumbnail repeats the title, and half the click surface says the same thing twice.

python3 "${CLAUDE_SKILL_DIR}/title.py" --title "..." --thumb "AI RAN IT"
python3 "${CLAUDE_SKILL_DIR}/title.py" titles.txt            # one per line, ranked

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.

Rules the tool enforces, and why

  • 60 characters is where desktop search truncates, 40 is a mobile home feed. Both are reported because they fail differently: a desktop cut loses the tail, a mobile cut can lose the subject.
  • The thumbnail must not repeat the title. Different words, same promise.
  • Three words maximum on the thumbnail. At feed size a fourth word is a grey smear.
  • A number, a name or a date beats every adjective available to you.
  • Two all-caps words is the ceiling before a title reads as spam.

Write ten, keep two

Generate ten titles, run them all through title.py, show the user the top three with their scores and the specific issue on each. For the winner, write the thumbnail brief: the expression, the framing, the three words, and what the background has to do to hold contrast at feed size.

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.