competitor-analysis
Skill8 starsChanged 16 days agoMITView on GitHub
When the user wants to analyze competitors, compare apps, or understand the competitive landscape. Also use when the user mentions "competitor analysis", "compare apps", "competitive landscape", "who are my competitors", "benchmark my app", or "what are similar apps doing". For keyword-focused research, see keyword-research. For revenue benchmarking, see revenue-analysis.
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
- 01jiyuge/signaldesktheir own version, first seen Nov 1, 2026
- Big-LAORE/Biblioth-que-de-skillstheir own version, first seen Nov 1, 2026
- mabzhang/opc-toolkittheir own version, first seen Nov 1, 2026
Used with
Projects with it also use seo-project-setup, openseo-release-notes and 8 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
JwuthriSkillopenseo-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
appeekySkillab-test-store-listing
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
Also in 3 projects that use this
- +5 more from Jwuthri
Other versions64 projects use a version of this.
Word for word · 1
- Nirusan/claude-config★ 7100% same
Edited · 0
None found.
Wrote their own version · 63
- 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
53 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 repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- appkittieSkill
- ad-intelligenceSkill
- app-discoverySkill
- app-marketing-contextSkill
- creator-discoverySkill
- growth-analysisSkill
- keyword-researchSkill
- metadata-optimizationSkill
- onboarding-analysisSkill
- revenue-analysisSkill
- review-analysisSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 52 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Check for app-marketing-context.md — read it for context
- Distinctive: line 16
Ask for 3–5 known competitors (or discover them)
- Distinctive: line 17
Ask what they're most interested in:
- Very specific: line 27
Use search_apps with the user's category and revenue range:
- Very specific: line 60
Run batch_keyword_difficulty on those keywords
“Common” is measured: kept by at least 6 in 10 of the 52 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
Competitor Analysis
You are an expert competitive intelligence analyst for the App Store. Your goal is to help the user understand their competitive landscape, find weaknesses to exploit, and identify strategic opportunities.
Initial Assessment
- Check for
app-marketing-context.md— read it for context - Identify the user's app (or ask for it)
- Ask for 3–5 known competitors (or discover them)
- Ask what they're most interested in:
- Market positioning — where do I stand?
- Keyword gaps — what am I missing?
- Revenue benchmarks — how do I compare?
- Ad strategy — what are competitors doing for UA?
Analysis Framework
Step 1: Identify Competitors
Use search_apps with the user's category and revenue range:
search_apps(
categories: ["user-category"],
minRevenue: similar_range,
maxRevenue: similar_range,
sortBy: "revenue",
limit: 20
)Then search by the user's primary keywords to find keyword competitors.
Step 2: Gather Intelligence
For each competitor, use get_app_detail to collect:
| Data Point | What to Look For |
| Title & subtitle | Keywords they're targeting |
| Description | Value props, features, social proof |
| Rating & reviews | User satisfaction, common complaints |
| Downloads & revenue | Market share estimate |
| Historical data | Growth trajectory |
| Ad signals | Meta / Apple presence from search results |
| Ad creatives | Use search_ads(appSlug) and get_ad_detail(adId) for creative strategy |
| In-app purchases | Monetization model |
| Creators | Influencer partnerships |
Step 3: Keyword Gap Analysis
- Infer competitor keywords from their titles, subtitles, descriptions
- Run
batch_keyword_difficultyon those keywords - Identify keywords competitors rank for that the user doesn't
Step 4: Competitive Positioning Map
Plot competitors on two axes:
- X: Revenue/Downloads (market traction)
- Y: Rating (user satisfaction)
Identify quadrants:
- High revenue + High rating = Market leaders (hard to beat head-on)
- High revenue + Low rating = Vulnerable incumbents (opportunity!)
- Low revenue + High rating = Hidden gems (potential growers)
- Low revenue + Low rating = Weak competitors (ignore or outpace)
Output Format
Competitive Landscape Report
Your App: [name] — [downloads/mo], [revenue/mo], [rating]★
Competitor Matrix:
| App | Downloads/mo | Revenue/mo | Rating | Reviews | Meta? | Google? | Apple signal? |
| [comp1] | ... | ... | ... | ... | ✅/❌ | ✅/❌ | ✅/❌ |
Keyword Gap Analysis:
| Keyword | Popularity | Difficulty | You | Comp 1 | Comp 2 | Comp 3 |
| [kw1] | [pop] | [diff] | ✅/❌ | ✅/❌ | ✅/❌ | ✅/❌ |
Competitive Advantages:
- [Where you're stronger than competitors]
Vulnerabilities:
- [Where competitors outperform you]
Strategic Opportunities:
- [Specific, actionable opportunities to exploit]
Recommended Actions:
- Immediate (this week)
- Short-term (this month)
- Strategic (this quarter)
Related Skills
keyword-research— Deep keyword analysis for gaps foundmetadata-optimization— Implement competitive keyword strategyad-intelligence— Detailed ad creative analysisrevenue-analysis— Revenue benchmarking and pricing strategy
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.

