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

competitor-tracking

Skill2.2k starsChanged 9 months agoMITView on GitHub

When the user wants to monitor competitor apps on an ongoing basis — tracking metadata changes, keyword shifts, screenshot updates, rating trends, or new features. Use when the user mentions "competitor monitoring", "track competitors", "competitor alert", "competitor changed their title", "watch a competitor app", "competitor weekly report", "competitive intelligence", or "what changed in competitor's listing". For a one-time deep competitive analysis, see competitor-analysis. For market-wide chart movements, see market-movers.

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

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    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. Distinctive:

    Ask: Who are your top 3–5 competitors?

    line 24
  2. Distinctive:

    Ask: How often do you want to review?

    line 25
  3. Distinctive:

    Ask: What are you most concerned about?

    line 26
  4. Distinctive:

    Use Appeeky to identify competitors if unknown:

    line 28
  5. Distinctive:

    Check weekly using Appeeky:

    line 38
  6. Distinctive:

    Run this analysis every Monday:

    line 93
  7. Very specific:

    Run a full competitor-analysis when:

    line 128
  8. Distinctive:

    Ask your agent each Monday:

    line 160

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Competitor Tracking

You set up and run ongoing competitor surveillance — catching metadata changes, keyword shifts, rating drops, and new feature launches before they impact your rankings.

One-Time Analysis vs Ongoing Tracking

competitor-analysis skillThis skill (competitor-tracking)
FrequencyOne-time deep diveWeekly/monthly recurring
OutputStrategy documentChange log + alerts
FocusGap analysis, positioningWhat changed and why it matters
DataSnapshotDelta (before vs after)

Setup: Define Your Watchlist

  1. Check for app-marketing-context.md
  2. Ask: Who are your top 3–5 competitors? (get App IDs if possible)
  3. Ask: How often do you want to review? (weekly recommended)
  4. Ask: What are you most concerned about? (keywords, ratings, creative, pricing)

Use Appeeky to identify competitors if unknown:

GET /v1/keywords/ranks?keyword=meditation&country=us&limit=10
GET /v1/apps/:id/intelligence  # check competitors array

What to Track

Metadata Changes

Check weekly using Appeeky:

GET /v1/apps/:id  # title, subtitle, description

Watch for:

  • Title changes — new keyword being targeted, repositioning
  • Subtitle changes — testing new hooks or keywords
  • Description changes — messaging strategy shift (Google Play especially)
  • Screenshot updates — new creative direction or A/B test winner shipped

Keyword Ranking Changes

GET /v1/apps/:id/keywords  # their ranking keywords
GET /v1/keywords/ranks?keyword=[shared keyword]  # who's ranking where

Watch for:

  • Keywords they're newly ranking for (they optimized for this — should you?)
  • Keywords they dropped (opportunity to capture)
  • A competitor jumping above you for a shared keyword

Ratings and Reviews

GET /v1/apps/:id/reviews?sort=recent&limit=20
GET /v1/apps/:id  # current rating

Watch for:

  • Rating drop (they shipped a bad update — opportunity to highlight your stability)
  • Surge of 1-stars around a specific complaint (user pain point you could solve)
  • New positive reviews praising a feature you don't have

Chart Positions

GET /v1/market/movers?genre=[genre_id]&country=us
GET /v1/categories/:id/top?country=us&limit=25

Watch for:

  • A competitor entering or exiting top 10 in your category
  • New competitor entering your space from a chart rise

Pricing and Paywall

Manually check every 4–6 weeks:

  • Trial length changes
  • Price changes (lower = aggressive growth; higher = LTV optimization)
  • New paywall format or plans

Weekly Competitive Report Template

Run this analysis every Monday:

Competitive Update — Week of [Date]

Apps tracked: [list names]

CHANGES DETECTED:
━━━━━━━━━━━━━━━━━
[Competitor Name]
  Metadata: [changed / no change]
    → [specific change if any]
  Top keywords: [gained X / lost Y / stable]
  Rating: [X.X → X.X] ([+/-N] ratings this week)
  Chart position: [#N → #N in category]
  New reviews theme: [if notable]

[Repeat per competitor]

OPPORTUNITIES IDENTIFIED:
1. [Competitor X dropped keyword Y — consider targeting it]
2. [Competitor X has surge of complaints about Z — your strength]
3. [Competitor X raised price — positioning opportunity]

THREATS:
1. [Competitor X now ranks #3 for [keyword] — we're at #8]
2. [New entrant spotted: [name] — check their metadata]

ACTION ITEMS:
1. [Specific response to a change]
2. [Keyword to target based on competitor gap]

Monthly Deep-Dive Triggers

Run a full competitor-analysis when:

  • A competitor jumps 10+ positions in the category chart
  • A competitor changes their title (signals major repositioning)
  • A new competitor enters the top 10 in your category
  • Your ranking drops on a keyword a competitor recently targeted

Automation Options

Manual (recommended for small teams)

Set a calendar reminder. Run the Appeeky API calls above. Fill the template.

Semi-automated

Build a script that calls Appeeky weekly and diffs results:

#!/bin/bash
APPS=("6759740679" "987654321" "111222333")
KEY="apk_your_key"

for APP_ID in "${APPS[@]}"; do
  echo "=== $APP_ID ==="
  curl -s "https://api.appeeky.com/v1/apps/$APP_ID" \
    -H "X-API-Key: $KEY" | jq '.data | {title, subtitle, rating, reviewCount}'
done

Store results weekly and diff with the previous week's output.

Appeeky MCP (in Claude/Cursor)

Ask your agent each Monday:

"Run a competitor check on apps [ID1], [ID2], [ID3] and 
compare their metadata and top keywords to last week."

The agent will use get_app, get_app_keywords, get_app_reviews to produce the report.

Competitive Response Playbook

What changedResponse
Competitor targets your #1 keyword in titleDefend: check your metadata is fully optimized; consider increasing ASA bids
Competitor drops a keyword you shareOpportunity: double down, increase bid in ASA
Competitor upgrades screenshotsAudit yours — are they still best in category?
Competitor rating drops below 4.0Mention your rating in promotional text while gap is visible
Competitor launches a feature you don't haveNote for roadmap; meanwhile highlight your differentiating strengths
New competitor enters top 10Run full competitor-analysis on them

Related Skills

  • competitor-analysis — Deep one-time competitive strategy
  • keyword-research — Act on the keyword gaps you find
  • market-movers — Catch chart-level competitor movements automatically
  • apple-search-ads — Respond to competitor keyword moves with ASA bids
  • aso-audit — Run on yourself after finding competitive gaps

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.