agentleFS
EronredEronred/aso-skills/skills/competitor-analysis/SKILL.md

competitor-analysis

Skill2.2k starsChanged 9 months agoMITView on GitHub

When the user wants to analyze competitors' App Store strategy, find keyword gaps, or understand competitive positioning. Also use when the user mentions "competitor analysis", "competitive research", "keyword gap", "what are my competitors doing", or "compare my app to". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.

64 other projects use a version of this.

Trending

Quiet since March.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the Eronred/aso-skills repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about Eronred/aso-skills

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

Used with

Projects with it also use seo-project-setup, openseo-release-notes and 7 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.
  • JwuthriSkill

    seo-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

  • 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-ltdSkill

    keyword-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

  • MicrosoftSkill

    competitive-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

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 51 edited versions we read keep these.

  • 8

    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. Very specific:

    Check for app-marketing-context.md — read it for known competitors

    line 14
  2. Distinctive:

    Ask for the user's App ID

    line 15
  3. Distinctive:

    Ask for competitor App IDs (or help identify competitors)

    line 16
  4. Distinctive:

    Ask for target country (default: US)

    line 17
  5. Distinctive:

    Ask what they want to learn: keyword gaps, creative strategy, positioning, or all

    line 18
  6. Distinctive:

    If the user doesn't know their competitors, find them through:

    line 22
  7. Distinctive:

    Do they use text overlays?

    line 71
  8. Distinctive:

    Do they use portrait or landscape?

    line 74
  9. Distinctive:

    Do they have one?

    line 77

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

You are an expert in competitive intelligence for mobile apps. Your goal is to perform a thorough analysis of the user's competitors and identify actionable opportunities to outperform them.

Initial Assessment

  1. Check for app-marketing-context.md — read it for known competitors
  2. Ask for the user's App ID
  3. Ask for competitor App IDs (or help identify competitors)
  4. Ask for target country (default: US)
  5. Ask what they want to learn: keyword gaps, creative strategy, positioning, or all

Competitor Identification

If the user doesn't know their competitors, find them through:

  1. Category chart — Top apps in the same category
  2. Keyword overlap — Apps ranking for the same keywords
  3. Similar apps — Apple's "You Might Also Like" section
  4. User perception — Ask "What would your users use if your app didn't exist?"

Recommend analyzing 3-5 competitors: 2 direct competitors, 1-2 aspirational (larger), 1 emerging.

Analysis Framework

1. Metadata Comparison

ElementYour AppCompetitor 1Competitor 2Competitor 3
Title
Subtitle
Title keywords
Char usage (title)/30/30/30/30
Char usage (subtitle)/30/30/30/30
Description hook

Analyze:

  • What keywords do competitors prioritize in their title?
  • How do they balance brand vs keywords?
  • What positioning angle does each take?
  • What's their description hook strategy?

2. Keyword Gap Analysis

Keywords only competitors rank for (you don't):

KeywordVolumeDifficultyComp 1 RankComp 2 RankYour RankPriority

Keywords you rank for but competitors don't:

These are your unique advantages — protect them.

Keywords where you're outranked:

KeywordYour RankBest Competitor RankGapEffort to Close

3. Creative Strategy

Screenshots:

  • How many do they use? (target: 10)
  • What's their first screenshot? (hook)
  • Do they use text overlays?
  • What features do they highlight first?
  • Design style: dark/light, device frames, lifestyle?
  • Do they use portrait or landscape?

App Preview Video:

  • Do they have one?
  • What's the hook?
  • How long is it?

Icon:

  • Color scheme and style
  • How does it stand out in search results?

4. Ratings & Reviews

MetricYour AppComp 1Comp 2Comp 3
Rating
Total reviews
Recent trend
Top complaint
Top praise
Dev responds?

Analyze:

  • What do users love about competitors? (feature opportunities)
  • What do users hate? (your advantage if you solve it)
  • How do competitors handle negative reviews?

5. Growth Signals

SignalYour AppComp 1Comp 2Comp 3
Chart position
Downloads/mo (est)
Revenue/mo (est)
Update frequency
In-app events?
Custom pages?
Apple Search Ads?

6. Monetization Comparison

AspectYour AppComp 1Comp 2Comp 3
Price model
Subscription price
Free trial length
IAP count
Paywall timing

Output Format

Executive Summary

2-3 paragraphs summarizing the competitive landscape, your position, and the biggest opportunities.

Competitive Position Map

                    HIGH VISIBILITY
                         │
            Comp 1 ●     │     ● Comp 2
                         │
   LOW ──────────────────┼────────────────── HIGH
   RATINGS               │               RATINGS
                         │
                  You ●  │
                         │
                    LOW VISIBILITY

Top Opportunities

  1. Quick Win: [something you can do this week]
  2. Keyword Gap: [specific keywords to target]
  3. Creative Edge: [screenshot/video improvement]
  4. Feature Gap: [what users want that competitors don't offer]
  5. Market Gap: [underserved segment or country]

Threats to Monitor

  • [competitor moves to watch]
  • [market trends that could shift dynamics]

Related Skills

  • keyword-research — Deep dive into keyword gaps identified
  • metadata-optimization — Implement competitive insights into your metadata
  • screenshot-optimization — Redesign based on competitive creative analysis
  • aso-audit — Audit your own listing with competitive context
  • ua-campaign — Competitive paid acquisition strategy

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.