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
Most recently taken up by
- khadinakbarlabs/competition-analyzer-trackertheir own version, first seen Oct 25, 2026
- appeeky/aso-skillsword for word, first seen Feb 27, 2026
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.
Other versions2 projects use a version of this.
Word for word · 1
- appeeky/aso-skills★ 2.2k100% same
Edited · 0
None found.
Wrote their own version · 1
- khadinakbarlabs/competition-analyzer-tracker★ 0same name
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 repository41 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- ab-test-store-listingSkill
- android-asoSkill
- app-analyticsSkill
- app-clipsSkill
- app-icon-optimizationSkill
- app-launchSkill
- apple-search-adsSkill
- app-marketing-contextSkill
- app-preview-videoSkill
- app-rejection-recoverySkill
- app-store-featuredSkill
- asc-metricsSkill
- aso-auditSkill
- aso-routerSkill
- attribution-setupSkill
- category-positioningSkill
- competitor-analysisSkill
- crash-analyticsSkill
- creator-ugc-marketingSkill
- custom-product-pagesSkill
- in-app-eventsSkill
- keyword-researchSkill
- localizationSkill
- market-moversSkill
- market-pulseSkill
- metadata-optimizationSkill
- monetization-strategySkill
- onboarding-optimizationSkill
- paywall-optimizationSkill
- press-and-prSkill
- rating-prompt-strategySkill
- referral-programSkill
- retention-optimizationSkill
- review-managementSkill
- screenshot-optimizationSkill
- seasonal-asoSkill
- subscription-lifecycleSkill
- ua-campaignSkill
- web-to-app-funnelSkill
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
- Distinctive: line 24
Ask: Who are your top 3–5 competitors?
- Distinctive: line 25
Ask: How often do you want to review?
- Distinctive: line 26
Ask: What are you most concerned about?
- Distinctive: line 28
Use Appeeky to identify competitors if unknown:
- Distinctive: line 38
Check weekly using Appeeky:
- Distinctive: line 93
Run this analysis every Monday:
- Very specific: line 128
Run a full competitor-analysis when:
- Distinctive: line 160
Ask your agent each Monday:
≈ “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.
Files
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 skill | This skill (competitor-tracking) | |
| Frequency | One-time deep dive | Weekly/monthly recurring |
| Output | Strategy document | Change log + alerts |
| Focus | Gap analysis, positioning | What changed and why it matters |
| Data | Snapshot | Delta (before vs after) |
Setup: Define Your Watchlist
- Check for
app-marketing-context.md - Ask: Who are your top 3–5 competitors? (get App IDs if possible)
- Ask: How often do you want to review? (weekly recommended)
- 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 arrayWhat to Track
Metadata Changes
Check weekly using Appeeky:
GET /v1/apps/:id # title, subtitle, descriptionWatch 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 whereWatch 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 ratingWatch 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=25Watch 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}'
doneStore 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 changed | Response |
| Competitor targets your #1 keyword in title | Defend: check your metadata is fully optimized; consider increasing ASA bids |
| Competitor drops a keyword you share | Opportunity: double down, increase bid in ASA |
| Competitor upgrades screenshots | Audit yours — are they still best in category? |
| Competitor rating drops below 4.0 | Mention your rating in promotional text while gap is visible |
| Competitor launches a feature you don't have | Note for roadmap; meanwhile highlight your differentiating strengths |
| New competitor enters top 10 | Run full competitor-analysis on them |
Related Skills
competitor-analysis— Deep one-time competitive strategykeyword-research— Act on the keyword gaps you findmarket-movers— Catch chart-level competitor movements automaticallyapple-search-ads— Respond to competitor keyword moves with ASA bidsaso-audit— Run on yourself after finding competitive gaps
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.

