agentleFS
TubeLabHQTubeLabHQ/youtube-research-skills/AGENTS.md

youtube-research-skills

AGENTS.md91 starsChanged 11 days agoMITView on GitHub

This repository is a set of Agent Skills for YouTube research on top of the TubeLab MCP. Skills live in skills/<name>/SKILL.md. Read the one that matches the ask, then follow it. skills/tubelab-mcp is the data layer every workflow skill names; load it when a tool call fails, returns nothing, or you are unsure which filter to use. Ordered chains for common jobs live in playbooks/ (run the whole agency, launch a faceless channel, monthly client report). The plugin ships six…

The file

We split this AGENTS.md 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
  1. Very specific:

    Always set publishedAtFrom (tokens: month, trimester, semester, year).

    line 44
  2. Distinctive:

    Every finding carries its proof from a tool response: channel (handle) · video title verbatim · views · ratio · date.

    line 47
  3. Distinctive:

    Look at the thumbnail of every video you analyze.

    line 49
  4. Distinctive:

    Write reports in plain language.

    line 52
  5. Distinctive:

    No MCP: the REST reference at https://tubelab.net/docs/skill.md.

    line 62

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
AGENTS.md

Agent routing guide

This repository is a set of Agent Skills for YouTube research on top of the TubeLab MCP. Skills live in skills/<name>/SKILL.md. Read the one that matches the ask, then follow it. skills/tubelab-mcp is the data layer every workflow skill names; load it when a tool call fails, returns nothing, or you are unsure which filter to use.

Which skill for which ask

The user asksLoad
Find a niche, unsaturated niches, faceless ideas, niches that earn beyond AdSense, twist or combine nichesniche-finder
Bend this channel's format into another market, niche bending, which proven formats can I bring to my marketniche-bending
What is working in X, why did this video blow up, trend report, weekly digest, hooks and formats to stealtrend-report
Video ideas for my channel, what should I make nextvideo-ideation
Analyze or roast my channel, why did views drop, what to change firstchannel-analysis
Will my channel get demonetized or terminated, is my channel at risk, audit my channels for monetization riskaudit-channel-risk
Reverse engineer a channel, what works for it, its title, thumbnail and hook formulas, how it grew and earns, what can I copy from itreverse-engineer-channel
Thumbnail for this video or title or script, thumbnail concepts, generate thumbnails, which thumbnails work in a nichethumbnail-concepts
Is X worth entering, is this niche saturated, go or no-go, score this niche, compare a shortlist of nichesniche-validator
Titles for my video, title formulas, trending title templates, rewrite a title, a title and a thumbnail together (titles first)title-formulas
Who are my competitors, how do I compare, competitive landscape, who is growing in my spacecompetitor-research
What do viewers ask or complain about, voice of audience, commentscomment-mining
Script structure, beat sheet, hook of this video, script skeleton, how the top videos of a niche or channel are builtscript-breakdown
Monetization gaps for my channel, what to sell, how channels like mine make money, raise RPM, who could sponsor my channel (the creator's side)monetization-research
Which channels should we sponsor, creator prospect list for a product, match creators to a buyer (the brand's side)sponsorship-prospecting
Watch a niche, which channels broke out since last run, scheduled digestniche-watchlist
How do TubeLab tools work, which filter, credits, RESTtubelab-mcp

Ordered chains for common jobs live in playbooks/ (run the whole agency, launch a faceless channel, monthly client report).

Roles (Claude Code agents)

The plugin ships six agents in agents/, one per role. Each loads the skills below and returns the skill's report. On other clients, load the skills directly.

AgentSkills
🔭 niche-scoutniche-finder; niche-bending to bend one channel's format, or a proven one, into new markets; niche-watchlist to watch a niche over time
⚖️ validatorniche-validator
📈 trend-analysttrend-report
🎬 script-analystscript-breakdown
🎨 packaging-teamtitle-formulas, then thumbnail-concepts for the chosen title
💰 monetization-teammonetization-research; sponsorship-prospecting when the user is a brand choosing channels to sponsor

Rules every skill follows

  1. Always set publishedAtFrom (tokens: month, trimester, semester, year). Widen one step at a time and say so.
  2. Content Authenticity is never off: classificationQuality at "neutral" or above for niches, outliers, ideation and titles; "positive" for anything thumbnail-related. Never drop it to widen a thin result. niche-watchlist and audit-channel-risk are the exceptions: the watchlist's saved search and the audit's similar channel searches leave the filter out.
  3. Rank by averageViewsRatio, not raw views. Show both.
  4. Every finding carries its proof from a tool response: channel (handle) · video title verbatim · views · ratio · date. Invent nothing.
  5. Link everything you cite: videos, channels, moments, brands and products. Use a URL from tool data, never a guessed one. A sponsor that was only heard links to the video moment where it was said.
  6. Look at the thumbnail of every video you analyze. Fetch the image from its link and open it.
  7. Revenue, RPM and audience are estimates. Present as bands, labelled.
  8. Searches cost credits. Channel, video, transcript and comment reads are free. Search to find candidates, and read to understand them. Most skills use two to six searches, and do not page through a paid search. One skill goes deeper, because the sample is the product: niche-finder pages its two channel searches 3 to 4 pages deep.
  9. Write reports in plain language. Use short, full sentences, not dense or telegraphic notes, and no jargon. A reader who is not a YouTube strategist should understand every line on first read.
  10. End with the artifact laid out in the skill's "Output Format" section.

Connecting the MCP

Repo conventions for contributors

See CONTRIBUTING.md. Each workflow skill is one self-contained SKILL.md with the sections Overview · Workflow · Output Format · Common Pitfalls. No skill has a references/ folder; the full API reference lives at https://tubelab.net/docs/skill.md. Keep it simple, do not over-engineer, Conventional Commits (type(scope): subject). Run node scripts/validate-skills.mjs before opening a PR.

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.