agentleFS
TubeLabHQTubeLabHQ/youtube-research-skills/skills/competitor-research/SKILL.md

competitor-research

Skill91 starsChanged 11 days agoMITView on GitHub

Use when the user wants to find a YouTube channel's real competitors, see how it compares, and find the gaps to win. Requires the TubeLab MCP.

29 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use icp-research, level and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • growthack88Skill

    icp-research

    Scrapes case studies, testimonials, and solutions pages from a target website to build structured ICP documentation. Produces TAM analysis, firmographic segments, champion and economic buyer personas, use case mapping, customer proof points, and voice-of-customer synthesis with normalized attributes. Requires website URL as primary input. Upstream: recommended company-context. Downstream: feeds positioning, product-messaging, landing-page-copy, content-strategy, and outreach-emails.

    Also in 5 projects that use this

  • dachi-jp3Skill

    level

    表示レベル(auto / low / medium / high)を切り替える。

    Also in 3 projects that use this

  • VercelSkill

    messaging

    Use when turning settled positioning into the lines other people will reuse: the message hierarchy, value propositions per audience, objection handling, and the proof behind each claim.

    Also in 4 projects that use this

  • ai-agents-for-agencies-coachesSkill

    brand-kit

    Establish and enforce per-client brand fidelity using the DESIGN.md standard (google-labs-code/design.md). Use whenever starting work for a client, creating any ad/landing-page/creative, or when brand colors/fonts/spacing are needed. Auto-extracts a client's visual identity into a validated DESIGN.md, keeps a central registry, and feeds the tokens into image-studio (statics), fb-ad-video-studio (video), and landing pages. Triggers: "set up brand for <client>", "make a DESIGN.md", "match the client's brand", "what are their brand colors", "new client onboarding", any creative work that must be on-brand.

    Also in 4 projects that use this

  • nocodeworkSkill

    company-context

    Interview the user to build or update a reusable company context file for AI tools — what the company does, its offer, clients, personas, positioning, voice, and the questions clients ask most. Use when the user says "build our company context", "create company context", "set up business context for AI", "update our company context", or wants AI to answer clients and write content in the company's voice without re-explaining the business each time. Produces company-context.md.

    Also in 3 projects that use this

  • VercelSkill

    positioning

    Use when working out what a product is, who it's for, and what it competes with: the market alternatives, the ideal customer, the differentiators worth claiming, and the positioning statement that follows.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 7

    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:

    Use searches to go further.

    line 21
  2. Distinctive:

    Verify every channel with a free read, one at a time: topic, audience, language and size.

    line 22
  3. Distinctive:

    If it runs long, cut whole items.

    line 56
  4. Very specific:

    Do not search without publishedAtFrom and classificationQuality at "neutral" or above, or the results fill with low-effort videos.

    line 62
  5. Distinctive:

    Do not keep a channel because a search returned it.

    line 63
  6. Distinctive:

    Do not compare raw medians across channel sizes.

    line 64
  7. Distinctive:

    Do not mix in Shorts.

    line 65
  8. Distinctive:

    Do not build a gap on one lucky video.

    line 66

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

Competitor Research

Overview

Find the channels competing for the same viewers. A similar channel is not always a competitor. A competitor serves the same audience with an overlapping promise. The value is the gap: what competitors win with that this channel does not cover. Not for how they earn (monetization-research).

Workflow

  1. Clarify scope only if needed.
  2. Build a set of 12 to 15 channels: direct competitors of similar size, a few larger leaders, and a few smaller channels growing fast. Start with the ones the user names and the ones you know.
  3. Use searches to go further. Channels behind recent outliers in the niche are good, cheap candidates. For a large channel, skip the similar-channels search; outliers in the niche are the source.
  4. Verify every channel with a free read, one at a time: topic, audience, language and size. Use medians over the last 90 days.
  5. Fetch and view the thumbnail of each gap video. If one fails to load, say so.

Output Format

# ⚔️ Competitor Research: [{channel}]({url})

- **Biggest gap:** {one sentence, with numbers}

Medians cover the last 90 days. This channel's row is in bold.

| Channel (link) | Subs | Median views | Median per sub | Uploads, 90 days | Topics |
|---|---:|---:|---:|---:|---|

## 🎯 Gaps to Win

### 1. {Gap}

[![]({thumbnail})]({video url})

- [{channel}]({url}) · [{title}]({video url}) · {views, ratio, date}
- [{channel}]({url}) · [{title}]({video url}) · {views, ratio, date} (a second win, if found)
- **Why it fits:** {one sentence}

## 🧭 Moves
- **Copy:** {one sentence}
- **Avoid:** {one sentence}
- **Positioning:** {one sentence}
  • Length: about 800 words. Every verified channel in the table, sorted by median per subscriber, with this channel's row in bold. About five gaps, each with up to two proofs.
  • Language: plain words and short, complete sentences. Nothing compressed.
  • Bullets: one fact each, under 25 words, except quotes and verbatim titles. No extra sections or bullets.
  • If it runs long, cut whole items. Never cut proof, and never squeeze sentences.
  • Links: link every video, channel, moment, brand and offer you cite, built from IDs, handles and links in the data. Never guess one.
  • Thumbnails: use the 320px mqdefault.jpg image, on its own line under the heading, linked to the video.

Common Pitfalls

  • Do not search without publishedAtFrom and classificationQuality at "neutral" or above, or the results fill with low-effort videos.
  • Do not keep a channel because a search returned it. Lookalikes are often tiny or off-topic, especially for large channels.
  • Do not compare raw medians across channel sizes. Median per subscriber is fairer.
  • Do not mix in Shorts.
  • Do not build a gap on one lucky video. It should win more than once.

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.