agentleFS
duncan-buildroomduncan-buildroom/profit-room-skills/skills/yt-titles/SKILL.md

yt-titles

Skill18 starsChanged 4 months agoMITView on GitHub

Generate high-performing YouTube title ideas from your video content, cross-referenced with your own channel's recent top-performing videos and competitor titles. Use this skill whenever the user wants YouTube title suggestions, asks "what should I title this video", "give me title ideas", "title options for my video about...", "help me name this video", brainstorming video titles, or any request involving YouTube title generation or optimization.

  • Installs packages

3 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 1 is common, 11 are distinctive, and 1 is very specific to this project.

  • 1

    Common

    Most of the 3 edited versions we read keep these.

  • 11

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

    If it doesn't exist, run the personalize skill first (or just tell me your name, niche, offer, and audience — I'll create it).

    line 12
  2. Distinctive:

    If a field this skill needs is blank, I'll ask one or two quick questions and save the answers back to the profile so you only answer once.

    line 13
  3. Distinctive:

    Never invent facts or results about the user — use only what's in the profile, or ask.

    line 14
  4. Very specific:

    Use the channel handle from your brand profile (or set the CHANNEL env var once so you can drop the flag).

    line 29
  5. Distinctive:

    If you have no channel yet, skip this step and lean on competitor analysis (Step 3) plus the title principles below.

    line 31
  6. Distinctive:

    Avoid duplicating existing titles, find angles competitors missed, identify high-performing framings.

    line 52
  7. Distinctive:

    Follow proven patterns. Safe bets.

    line 59
  8. Distinctive:

    No generic filler: "Ultimate Guide", "Everything You Need to Know"

    line 80
  9. Distinctive:

    Don't start with the channel name

    line 81
  10. Distinctive:

    No brackets like [FULL GUIDE] or [2026] — they waste character space

    line 83
  11. Distinctive:

    The test: if the thumbnail text could be a subtitle of the title, it's wrong.

    line 88
  12. Distinctive:

    ALL CAPS reads better on thumbnails at small sizes

    line 90
  13. Common:

    After presenting, ask if the user wants to refine any direction or generate variations on a specific title.

    line 121

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

YouTube Title Generator

Generate YouTube title options by analyzing what's already working on your channel and applying those patterns to new content.

Personalization

This skill works in your brand voice. Before running, load the brand profile at ~/.claude/brand-profile.md.

  • If it doesn't exist, run the personalize skill first (or just tell me your name, niche, offer, and audience — I'll create it).
  • If a field this skill needs is blank, I'll ask one or two quick questions and save the answers back to the profile so you only answer once.
  • Never invent facts or results about the user — use only what's in the profile, or ask.

This skill needs your YouTube channel (a @handle or channel URL). If it's not in your brand profile's social handles, ask once and save it back.

Requirements

  • yt-dlp on PATH (pip install yt-dlp) for pulling channel + competitor data. If it's missing, I'll tell you the one command to add it.

Workflow

Step 1: Pull your channel performance data

python3 ~/.claude/skills/yt-titles/scripts/channel_performance.py --channel @yourhandle --months 3 --count 30

Use the channel handle from your brand profile (or set the CHANNEL env var once so you can drop the flag). Returns recent videos sorted by views with views/day, engagement ratio, and like ratio.

If you have no channel yet, skip this step and lean on competitor analysis (Step 3) plus the title principles below.


Step 2: Analyze title patterns

From the top 10 performers, identify:

  • Hooks: Opening words that pull people in ("I built...", "Stop...", "How I...")
  • Structure: Format patterns ("Hook + specific outcome", "Number + result")
  • Length: What character count range works
  • Specificity signals: Tools by name, time frames, dollar amounts, results
  • Emotional triggers: Curiosity gaps, contrarian takes, urgency

Also note bottom performers — what to avoid.

Step 3: Scout competition

python3 ~/.claude/skills/yt-search/scripts/search.py <topic keywords> --count 10 --months 3

Avoid duplicating existing titles, find angles competitors missed, identify high-performing framings.

Step 4: Generate titles

10-15 options in three tiers:

Tier 1 — High Confidence (3-5) Follow proven patterns. Safe bets.

Tier 2 — Calculated Risks (3-5) Remix successful patterns with competitor angles. Higher ceiling.

Tier 3 — Swing for the Fences (3-5) Contrarian angles, pattern breaks, untested formats. Testing these is how channels grow.

Each title gets a one-line note: what pattern it's based on and why it works for this content.

Title principles

  • Front-load the hook — first 3-5 words determine if someone reads the rest
  • Specific > vague — "I Automated My Entire Business in 4 Hours" beats "How to Use AI for Business"
  • Keep it under 60 characters — longer titles truncate on mobile
  • Avoid clickbait that can't deliver — respect the audience's intelligence
  • Match search intent when relevant — but don't force SEO at the expense of CTR
  • Title Case reads better in YouTube's UI
  • Honor your brand-profile words-to-avoid — never use phrasing the user has asked you to avoid

What NOT to do

  • No generic filler: "Ultimate Guide", "Everything You Need to Know"
  • Don't start with the channel name
  • One emoji maximum (if any)
  • No brackets like [FULL GUIDE] or [2026] — they waste character space

Thumbnail text principles

2-5 words max. Creates a curiosity gap WITH the title — never restates it.

  • The test: if the thumbnail text could be a subtitle of the title, it's wrong. It should add new information the title withholds.
  • Thumbnail text answers a question the title raises — or reveals the how/what the title teases
  • ALL CAPS reads better on thumbnails at small sizes
  • Emotion/reaction words work: "WAIT WHAT", "GAME OVER", "IT'S FREE"
  • Concrete numbers: "$0/month", "10 MINUTES", "7 SKILLS"

Output format

## Your Top Performers (last 3 months)
[Brief summary — top 5 with views and what title patterns stand out]

## Competitor Landscape
[What's already out there, what angles are open]

## Title Options

### Tier 1 — High Confidence
1. **Title Here**
   Based on: [pattern] — [why it works]

### Tier 2 — Calculated Risks
...

### Tier 3 — Swing for the Fences
...

## Thumbnail Text Options

### For: "[Title 1]"
1. **[2-3 WORDS]** — [why this works with the title]

After presenting, ask if the user wants to refine any direction or generate variations on a specific title.

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.