competitor-analysis
Skill0 starsChanged 5 months agoMITView on GitHub
Maps the competitive landscape, finds positioning gaps, and builds a differentiation table plus a sharp "why we win" angle. Trigger on "who are my competitors", "competitive analysis", "how do I differentiate", "positioning gap", "build a battle card", or "why would anyone switch to us".
64 other projects use a version of this.
Adopted by
Most recently taken up by
- oivanfelipe/claude-skillstheir own version, first seen Nov 8, 2026
- alunadev/ald-skillstheir own version, first seen Nov 8, 2026
- foverse/seoversetheir own version, first seen Nov 8, 2026
- AppKittie/aso-mcp-skillstheir own version, first seen Nov 8, 2026
- 01jiyuge/signaldesktheir own version, first seen Nov 1, 2026
- Big-LAORE/Biblioth-que-de-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use seo-project-setup, app-marketing-context and 10 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.
JwuthriSkillseo-project-setup
Set up a durable local SEO workspace with project context, notes, goals, positioning, preferences, MCP checks, and Search Console data intake.
Also in 11 projects that use this
appeekySkillapp-marketing-context
When the user wants to create or update their app marketing context document. Also use when the user mentions "app context", "marketing brief", "app positioning", or when starting any ASO or app marketing project. This is the foundation skill — all other skills check for this context first.
Also in 6 projects that use this
- appeekySkill
metadata-optimization
When the user wants to optimize App Store metadata — title, subtitle, keyword field, or description. Also use when the user mentions "optimize my title", "ASO metadata", "keyword field", "character limits", "app description", or "write my subtitle". For keyword discovery, see keyword-research. For full ASO audits, see aso-audit.
Also in 6 projects that use this
- JwuthriSkill
openseo-release-notes
Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR. Use when the user asks to prepare a release, bump the version, or write release notes.
Also in 6 projects that use this
akii-technologies-ltdSkillkeyword-clustering
Cluster and organize keywords into topical groups for SEO. Use when the user asks to "cluster keywords", "group keywords", "organize keywords", "keyword mapping", "topic clusters", "keyword grouping", "build a content plan", "pillar pages", "topical authority", "semantic clustering", or pastes a list of keywords.
Also in 11 projects that use this
MicrosoftSkillcompetitive-landscape
Use when a branch manager asks something like \"Who are we up against in each metro\"
Also in 11 projects that use this
- +5 more from Jwuthri
- +1 more from appeeky
Other versions64 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 64
- langchain-ai/deepagents★ 31ksame name
- every-app/open-seo★ 27ksame name
- browserbase/agent-browse★ 3.7ksame name
- appeeky/aso-skills★ 2.2ksame name
- Eronred/aso-skills★ 2.2ksame name
- Jwuthri/Tracely-ai★ 1.3ksame name
- VladSez/easy-invoice-pdf★ 1.1ksame name
- jwuthri-cloud/Tracely-ai★ 979same name
- indranilbanerjee/digital-marketing-pro★ 934same name
- OpenClaudia/openclaudia-skills★ 731same name
54 more not listed
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 repository9 other files it gives its agents.
- cold-outreachSkill
- fundraising-narrativeSkill
- growth-experimentsSkill
- landing-page-copySkill
- market-researchSkill
- mvp-specSkill
- pricing-experimentsSkill
- pricing-strategySkill
- tam-sam-somSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 53 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
When a founder needs to understand who else solves this pain, where the white space is, and how to position so the product looks obviously …
- Distinctive: line 40
Treat thin GPT/Claude wrappers as fragile rivals: their moat is zero, attack it.
- Distinctive: line 41
Avoid: ignoring the status-quo competitor.
“Common” is measured: kept by at least 6 in 10 of the 53 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.
Files
When to use
When a founder needs to understand who else solves this pain, where the white space is, and how to position so the product looks obviously different (not just better).
Inputs to gather
- Product description and target ICP.
- Any competitors already known (direct, indirect, and "the status quo").
- The 1-2 dimensions customers actually care about most.
Process
- List 5-8 competitors across 3 buckets: direct (same job, same buyer), indirect (different shape, same job), and the real default (spreadsheet, agency, doing nothing). The default is usually the toughest competitor.
- Profile each on: who they serve, pricing model, core promise, visible weakness, and their moat (data, integrations, brand, network effects).
- Plot a 2x2 on the two axes the ICP cares about most; find the empty quadrant.
- Build the differentiation table: rows = features/outcomes that matter, columns = you vs. top 3 rivals. Be honest where they win.
- Write the "why we win" angle — one sentence of earned, defensible difference, not a feature list. Run the moat test: "if OpenAI shipped this, what's left?"
Output
- Landscape map: the 2x2 with every competitor placed and the open quadrant marked.
- Differentiation table (markdown) with an honest ✓ / ✗ / ~ grid.
- "Why we win": one positioning sentence + 3 proof points.
- Battle card: for the top rival — their pitch, their weakness, your counter.
Quality bar & pitfalls
- Good = the differentiation is structural (data, vertical depth, workflow lock-in), not "cleaner UI" or "cheaper" — those get copied in a sprint.
- Treat thin GPT/Claude wrappers as fragile rivals: their moat is zero, attack it.
- Avoid: ignoring the status-quo competitor; a feature table where you win every row (nobody believes it); positioning that any rival could claim word-for-word.
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.