AGENT SKILLBY ERONRED
Competitor tracking
AT A GLANCE
Competitor tracking is an analytics agent skill from eronred. When the user wants to monitor competitor apps on an ongoing basis — tracking metadata changes, keyword shifts, screenshot updates, rating trends, or new features. It is published in the eronred/aso-skills GitHub repository (1.8K stars) under the MIT license. Install it with: npx skills add eronred/aso-skills --skill competitor-tracking
- SOURCE REPOSITORY
- eronred/aso-skills (opens GitHub in a new tab)
- REPO STARS
- SOURCE REPOSITORY
- LICENSE
- MIT
- SKILL.MD SIZE
- 5.6 KB179 LINES
QUICK ANSWER
- WHAT IT IS01
- When the user wants to monitor competitor apps on an ongoing basis, tracking metadata changes, keyword shifts, screenshot updates, rating trends, or new features. What sets it apart is how it narrows competitive research into one specific workflow rather than a broad, generic prompt.
- INPUTS02
- Context for competitive research: your goals, audience, constraints, and any source material the skill asks for.
- OUTPUT03
- A ready-to-use result for competitive research: the analysis, copy, or recommendations the agent produces.
INSTALL
One command adds this skill from its source repository.
npx skills add eronred/aso-skills --skill competitor-trackingREAD THE SKILL.MD BELOW BEFORE YOU RUN IT. SKILLS INSTRUCT YOUR AGENT.
SKILL.MD
The full file, as published in the source repository. Copy it, download it or open it on GitHub.
ON THIS PAGE · 16
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
FAQ
07 QUESTIONS
01What is the Competitor tracking agent skill?
When the user wants to monitor competitor apps on an ongoing basis, tracking metadata changes, keyword shifts, screenshot updates, rating trends, or new features. It is listed under analytics and go-to-market in the 100xLab agent skills directory.
02How do I install Competitor tracking in Cursor, Claude Code, or Codex?
Run npx skills add eronred/aso-skills --skill competitor-tracking in the project where you want it, then ask your agent for the skill by name. The --skill flag installs only Competitor tracking, not every skill in the repository.
03What does the Competitor tracking SKILL.md cover?
The SKILL.md includes sections on One-Time Analysis vs Ongoing Tracking, Setup: Define Your Watchlist, What to Track, Metadata Changes, Keyword Ranking Changes and Ratings and Reviews. Read the full text on this page or in plain markdown at /resources/agent-skills/eronred-aso-skills--competitor-tracking--15irpmh/raw.
04Which agents can use Competitor tracking?
Competitor tracking installs with the cross-agent skills installer (npx skills add), which sets it up for agents such as Claude Code, Cursor and Codex. Each agent loads the SKILL.md when you ask for the skill by name.
05What license is Competitor tracking under?
The eronred/aso-skills repository declares the MIT license. Read the license file in the repository before you copy or redistribute the skill.
06Is Competitor tracking free to use?
Reading, copying and installing Competitor tracking costs nothing: it is published in a public GitHub repository under the MIT license. Reuse and redistribution follow that license.
07Where is the source of Competitor tracking?
Competitor tracking comes from https://github.com/eronred/aso-skills, which has 1.8K GitHub stars. The SKILL.md is at https://github.com/eronred/aso-skills/blob/HEAD/skills/competitor-tracking/SKILL.md. The author is eronred.
Need an agent workflow built around your stack?
Tell us the workflow you want automated. We reply within 4 working hours (IST).
ATTRIBUTION
Competitor tracking was written by its original authors and is published in eronred/aso-skills (opens GitHub in a new tab) under the MIT license. All rights stay with the original authors.
100xLab did not write, maintain or endorse this skill. This page lists it for discovery. Repo stars belong to the source repository, not to the skill. Review any skill before you install it.