
Competitor Tracking
- 1.6k installs
- 1.7k repo stars
- Updated July 27, 2026
- eronred/aso-skills
competitor-tracking is an agent skill that 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
About
competitor-tracking is an agent skill from eronred/aso-skills that 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 "competit. # 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 dee Developers invoke competitor-tracking during ship/testing work for testing & qa tasks. The skill documents triggers, prerequisites, and step-by-step workflows grounded in SKILL.md. Compatible with Claude Code, Cursor, and Codex agent runtimes that load marketplace skills. Review the Security Audits panel on this listing before installing in production environments.
- 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 |
Competitor Tracking by the numbers
- 1,615 all-time installs (skills.sh)
- +63 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #463 of 2,153 Testing & QA skills by installs in the Skillselion catalog
- Security screen: HIGH risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
competitor-tracking capabilities & compatibility
- Capabilities
- one time analysis vs ongoing tracking · | | `competitor analysis` skill | this skill (`c · | **frequency** | one time deep dive | weekly/mo · | **output** | strategy document | change log + · | **focus** | gap analysis, positioning | what c
- Use cases
- orchestration
What competitor-tracking says it does
You set up and run ongoing competitor surveillance — catching metadata changes, keyword shifts, rating drops, and new feature launches before they impact your rankings.
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)
npx skills add https://github.com/eronred/aso-skills --skill competitor-trackingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.6k |
|---|---|
| repo stars | ★ 1.7k |
| Security audit | 2 / 3 scanners passed |
| Last updated | July 27, 2026 |
| Repository | eronred/aso-skills ↗ |
What it does
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 "competit
Who is it for?
Developers working on testing & qa during ship tasks.
Skip if: Tasks outside Testing & QA scope described in SKILL.md.
When should I use this 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. Use when the user mentions "competit
What you get
Completed testing & qa workflow aligned with SKILL.md steps.
- Competitor watchlists
- Change alerts
- Weekly competitive reports
By the numbers
- Skill metadata version is 1.0.0
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
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 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
Related skills
How it compares
Pick competitor-tracking for continuous listing change alerts; pick competitor-analysis for a single deep competitive review.
FAQ
What does competitor-tracking do?
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 "competit
When should I use competitor-tracking?
During ship testing work for testing & qa.
Is competitor-tracking safe to install?
Review the Security Audits panel on this listing before production use.