title-research
Skill5 starsChanged 44 days agoMITView on GitHub
Research real top-performing YouTube titles for a topic with Firecrawl, extract the winning patterns, generate candidates that apply those patterns to the user's video, then rank them with the title-score skill. Use when the user wants YouTube title ideas, clickbait titles, title inspiration from what's already working, or asks to "research titles". Produces evidence-backed titles (each traced to a real high-view video) instead of guessing.
In this repository21 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- delegateSkill
- finish-featureSkill
- new-projectSkill
- prune-context-fileSkill
- questionsSkill
- reddit-firecrawl-supportSkill
- reference-led-websitesSkill
- say-as-meSkill
- short-edit-beaconSkill
- short-editSkill
- shortSkill
- shorts-writerSkill
- site-designSkill
- sync-docsSkill
- title-scoreSkill
- tweetSkill
- verifySkill
- video-scriptSkill
- wdytSkill
- website-reference-curatorSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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
- Very specific: line 26
If $SCORE does not exist, title-score is not installed: say so and stop before Step 4 rather than reporting unscored titles as ranked.
- Distinctive: line 40
Run 2-3 query variants for broader coverage (e.g.
- Distinctive: line 61
Keep each title truthful to the actual video content.
- Distinctive: line 86
Never present invented titles as "real videos".
- Distinctive: line 88
If view counts are unavailable (search fallback), say so.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
title-research
Generate YouTube titles by mining what actually performs, not by guessing.
Pipeline: research → extract patterns → generate → score → report.
Depends on:
firecrawlCLI (authenticated)- the
title-scoreskill, installed as a sibling directory of this one
Paths below are relative to this skill's base directory, not the user's project. Resolve them from the SKILL.md you are reading, e.g.:
SKILL_DIR=<absolute path of the directory containing this SKILL.md>
SCORE="$SKILL_DIR/../title-score/scripts/score.py"If $SCORE does not exist, title-score is not installed: say so and stop
before Step 4 rather than reporting unscored titles as ranked.
Step 1 — Research top titles
python3 "$SKILL_DIR/scripts/research.py" "web scraping AI" --sort viewsThe script scrapes YouTube search results sorted by view count, uses
firecrawl interact to extract title | channel | views, and falls back to
firecrawl search site:youtube.com ... when interact fails (common: YouTube
scrape jobs die with "Job not found" or 401 consent pages).
Run 2-3 query variants for broader coverage (e.g. "web scraping AI", "AI agent web search", "scrape anything"). If both strategies fail, tell the user instead of inventing data.
Step 2 — Extract winning patterns
From the highest-view titles, note concrete formulas, e.g.:
- "Use AI To Scrape ANYTHING" → [VERB] + [TECH] + To + [VERB] + ANYTHING
- "This AI Agent Can Scrape ANYTHING (100% Automatic)" → This X Can Y (promise)
- "AI Web Scraping Is Insanely Good" → X Is Insanely Good
- "How To Scrape Any Website With X" → How To + task + With + tech
- "in 10 Minutes" / "in 100 Lines" → concrete effort qualifier
- CAPS emphasis words: ANY, ANYTHING, FREE, BLIND, INFINITE
Step 3 — Generate candidates
Apply the patterns to the user's video. Rules:
- Honor hard constraints (e.g. "must include Convex", no clickbait lies).
- Generate 10-15 candidates across at least 4 distinct patterns.
- Keep each title truthful to the actual video content.
- Reuse exact power words (ANYTHING, Insanely, FREE) and number qualifiers (minutes, lines, pages) from the real winners.
Step 4 — Score and rank
printf '%s\n' "Title 1" "Title 2" ... | python3 "$SCORE" -Iterate once: tweak the weakest sub-scores of the top half (add a digit, a colon/question mark, a power word) and re-score. Keep the best 10.
Step 5 — Report
Table ranked by score:
| # | Score | Title | Inspired by (real video + views) |
Note which sub-scores help/hurt each title, flag that the score is a heuristic approximation (see title-score skill), and recommend the top 1-2 with a one-line rationale tying title to actual video content.
Honesty
- Never present invented titles as "real videos". Every inspiration must come from Step 1 output.
- If view counts are unavailable (search fallback), say so.
- The final score is the title-score approximation, not vidIQ.
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
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.

