competitor-scan
Skill2 starsChanged 49 days agoMITView on GitHub
The weekly scan of competitor, inspiration and neighbourhood channels — what is performing right now, whether it already exists in your language, and the 3 widest gaps. Run by /radar. Triggered by "run the weekly scan", "what are my competitors doing this week", "scan my lists". In Spanish, "pasa el escaneo semanal", "qué están haciendo mis competidores esta semana", "escanea mis listas".
2 other projects use a version of this.
Adopted by
Most recently taken up by
- agentdynarq/founder-skillstheir own version, first seen Jul 15, 2026
- Mehdibargach/claude-code-pm-skillstheir own version, first seen Mar 18, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Mehdibargach/claude-code-pm-skills★ 97same name
- agentdynarq/founder-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- analyse-channel-packagingSkill
- analyse-thumbnailsSkill
- channel-analyticsSkill
- channel-identitySkill
- channel-kickoffSkill
- competitor-boardSkill
- competitor-ideationSkill
- competitor-mappingSkill
- image-generation-coreSkill
- image-refinementSkill
- keywords-seoSkill
- likeness-preservationSkill
- memory-reviewSkill
- monetisationSkill
- packagingSkill
- script-writingSkill
- thumbnail-best-practicesSkill
- thumbnail-inspirationSkill
- transparencySkill
- youtube-banner-specSkill
- youtube-profile-specSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 4 are distinctive, and 5 are 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Not the competitor board (the web page with every video of the last 6 months: that is competitor-board) and not a full ideation batch (that …
- Distinctive: line 18
Read CLAUDE.md if you have not already done so this session.
- Very specific: line 32
If fewer than 10 outliers come back, drop to --min-ratio 1.5 before concluding there is nothing.
- Distinctive: line 57
If you have a memory about how to read outliers, apply it here.
- Distinctive: line 74
Before an outlier goes into the table, check its likes per 1k views against the channel's usual.
- Very specific: line 80
Read memory/rules.md and memory/creator_profile.md.
- Distinctive: line 86
Title reminder: do not copy the original's formula.
- Very specific: line 106
If an outlier changes what was known about the niche, propose updating memory/.
- Very specific: line 108
If there is a competitor board (memory/competitor_board.md), sync it with the competitor-board skill and end with its link.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Weekly competitor scan
WHEN
The weekly review of the channel lists, usually through /radar. Always
started by the creator.
Not the competitor board (the web page with every video of the last 6 months:
that is competitor-board) and not a full ideation batch (that is
competitor-ideation). This scan finds what moved recently and where the gap
is; it ends with three proposals, not eight.
Read CLAUDE.md if you have not already done so this session.
EXECUTION ORDER
1. Scan
python3 tools/yt_outliers_channels.py --min-ratio 2.0 --sample 25 --max-days 45--max-days 45 is not optional. Without it, ranking by ratio buries what
is recent under outliers from 6-11 months ago, which are no longer
opportunities.
If fewer than 10 outliers come back, drop to --min-ratio 1.5 before
concluding there is nothing.
2. Add what was saved by hand
python3 tools/yt_outliers_playlist.py --days 143. Split by list — each one is read differently
competitors(same language, same niche): what works here is direct competition. If a competitor lands an outlier, the gap is closing.inspiration(often another language, an arbitrage source): this is usually the list that matters. For each outlier, the question is: does it already exist in your language?neighbourhood(channels YouTube associates with yours): tells you how the algorithm is classifying you.
4. Adjust for market size before quoting figures
Views in a larger-market language are not reachable as-is in a smaller one.
Measure your own factor over time and write it into memory/; until you have
one, say you are quoting the raw figure and that it overstates the expectation.
If you have a memory about how to read outliers, apply it here.
5. Check the gap in your language
For the 3-5 strongest foreign-language outliers:
python3 tools/kw_research.py --kw "topic in your language; variant"
python3 tools/yt_search.py --query "topic in your language"yt_search costs 100 quota units per query — use it only on the finalists. And
remember it does not filter by language: if the top results are in another
language, that does not prove the gap in yours is closed.
6. Leave out bought views
Before an outlier goes into the table, check its likes per 1k views against the channel's usual. Views that arrive without likes are ad reach: drop the video and say so. Affiliate links prove nothing, almost every channel carries them.
7. Filter against the channel's rules
Read memory/rules.md and memory/creator_profile.md. Discard what does not
fit and say why.
Format reminder: apply the restrictions in memory/rules.md, if there are
any. Never propose a format the channel has discarded.
Title reminder: do not copy the original's formula. Copy the TOPIC and rewrite it with the house formula, whatever your own data says that is. And a high ratio on a huge channel does not mean the same thing as on a small one.
SOURCES
- Outlier ratios, views and likes:
youtube_api(views, likes) andderived(the ratio against the channel's median). kw_research.pyscores:heuristic, a proxy — never a search volume.score_titles.pyscores:heuristic, never a CTR prediction.- The market-size factor:
configif it is inmemory/, otherwise say there is none and that the raw figure overstates the expectation.
OUTPUT
- Opportunity table: outlier, channel, ratio, views, and whether it already exists in your language.
- The 3 with the widest gap, each with a proposed title already in the
channel's formula, scored with
python3 tools/score_titles.py. - One recommendation and the reason for it.
- If an outlier changes what was known about the niche, propose updating
memory/. - If there is a competitor board (
memory/competitor_board.md), sync it with thecompetitor-boardskill and end with its link. If there is none, offer to create one in a single line.
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.

