agentleFS
utillayerutillayer/youtube-agent-skill/skills/yt-seo/SKILL.md

yt-seo

Skill10 starsChanged 29 days agoMITView on GitHub

Write a video's description, tags and search text around what a real person would type. Use for "write my description", "tags", "SEO", "help people find this video", "nobody finds this".

6 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Search matters less than packaging for most videos, and more than people expect for ones that stay useful for years.

    line 11
  2. Very specific:

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

    line 17
  3. Distinctive:

    Never make up a number, a result or a source.

    line 19
  4. Distinctive:

    Before handing over, write the three searches this video should win, and check their words appear in the title and the first two lines.

    line 44

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

Search matters less than packaging for most videos, and more than people expect for ones that stay useful for years. If a video is made for the subscriber feed, say so and put the effort into /yt-package instead.

Before you start

  1. Read ~/.claude/youtube/voice.md if it exists. If not, ask for three of the creator's videos and write it. A description is read in the creator's voice too.
  2. Never make up a number, a result or a source.

The description

  • The first two lines are the only ones most people see. They show above "...more" and become the search snippet. Say what the video gives, in the words someone would type.
  • Then the link or resource, if there is one, while it is still visible.
  • Then chapters (/yt-chapters writes them).
  • Then the long version: what it covers, who it is for, what it assumes. For a sourced video, a sources block citing exactly what it draws on.

The limit is 5,000 characters, counted in bytes by the API, so text in a non-Latin script reaches it sooner. Nothing needs to come close.

Hashtags: the first three appear above the title. Use one to three that a viewer would tap. Over 60 and YouTube ignores all of them.

Tags

YouTube's own help page says tags "play a minimal role" in discovery. Use them for spellings, product names and the abbreviations people type, and stop there. Fifteen is plenty and the field holds 500 characters. Stuffing unrelated tags breaks the terms of service.

The query test

Before handing over, write the three searches this video should win, and check their words appear in the title and the first two lines. If they do not, the title is the problem, not the description.

Before you hand it over

This skill drafts; you publish. End with the copy-ready block and one question: post it as is, or another pass?

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.