agentleFS
Sign inStart free
asospyasospy/asospy-agent-skills/skills/competitor-analysis/SKILL.md

competitor-analysis

Skill1 starsChanged 46 days agoMITView on GitHub

Compare an app with its competitors on installs, revenue estimates, ratings, chart ranks and Apple Search Ads keywords, and turn the gaps into actions. Use when the user names an app and asks how it compares, who its competitors are, or what competitors do better. Needs the ASOSpy MCP server.

66 other projects use a version of this.

Adopted by

Most recently taken up by

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

  • appeekySkill

    app-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-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
  • +1 more from appeeky

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 55 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before a positioning, pricing or ASO decision.

    line 11
  2. Very specific:

    If a name is ambiguous, the tool returns APP_NOT_FOUND with details.candidates.

    line 21
  3. Very specific:

    No competitors given: search_apps on the same store with 1–2 core words from the title or use case, the same category, sort: "installs".

    line 30
  4. Distinctive:

    If step 7 ran: the ad networks each app lists, and which ones they share.

    line 41

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

When to use

  • "Compare my app with its competitors", "who are X's competitors", "how does X stack up against Y and Z".
  • Before a positioning, pricing or ASO decision.

Inputs

InputDefaultNotes
ApprequiredASOSpy id, App Store id, package name, store URL, ASOSpy URL or name.
Competitorsfound automatically3–5 apps.
CountryusTwo letters; used for chart ranks.

If a name is ambiguous, the tool returns APP_NOT_FOUND with details.candidates. Pick the right one (ask the user if unsure) and call again with its id. A name that exists on both stores (for example "Headspace") needs store: "ios" or store: "android".

Tools

get_app_detail, search_apps, get_app_historicals, get_store_ranking_history, search_ads (mode: "app_keywords", iOS only; mode: "app_ad_networks", both stores).

Workflow

  1. get_app_detail for the app: store, category, installs, revenue, ratingScore, ratingsCount, price model.
  2. No competitors given: search_apps on the same store with 1–2 core words from the title or use case, the same category, sort: "installs". Skip the app itself and clones. Keep 3–5.
  3. get_app_detail for each competitor.
  4. get_app_historicals for every app with metrics: ["installs", "revenue", "score"] (last 90 days).
  5. get_store_ranking_history for every app with the country: best rank, current rank, stability.
  6. iOS apps: search_ads with mode: "app_keywords" and app: <id> to see which Apple Search Ads keywords they appear on.
  7. Optional, when ads monetisation matters: search_ads with mode: "app_ad_networks" and app: <id> for each app. It lists the ad networks and publisher IDs in the app's app-ads.txt, networks with DIRECT lines (the owner's own accounts) first. To see which other apps use the same account, pass a publisher ID to mode: "publisher_apps".

Output

  1. Comparison table: app, installs, daily installs, revenue (estimate), ratingScore, ratingsCount, best chart rank, 90-day installs change, last update.
  2. For each competitor: two things it does better and one weakness, each backed by a number from the table.
  3. If step 7 ran: the ad networks each app lists, and which ones they share.
  4. Five actions for the user's app, most important first.

Limitations

  • iOS installs and all revenue are estimates; compare trends more than exact values.
  • Chart ranks exist only while an app is in a chart; no rank is not the same as rank 0.
  • Apple Search Ads data is a scraped sample (iPhone, short history, beta). No row does not prove an app does not advertise. There are no spend, impressions or creatives.
  • get_app_historicals has no per-country split.
  • app-ads.txt only declares which ad networks may sell an app's ad space. It does not show which ads run or how much they earn, and a developer's apps usually share one list.

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.

Check your setup, free