competitor-tracking
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.
npx skills add Eronred/aso-skills --skill competitor-tracking --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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: ```bash 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: ```bash GET /v1/apps/:id # title, subtitle, description ``` Watch for: - **Title changes** — n
- One-Time Analysis vs Ongoing Tracking
- Setup: Define Your Watchlist
- What to Track
- Metadata Changes
- Keyword Ranking Changes
- Ratings and Reviews
- Chart Positions
- Pricing and Paywall
- Weekly Competitive Report Template
- Monthly Deep-Dive Triggers
- Automation Options
- Manual (recommended for small teams)
- Semi-automated
- Appeeky MCP (in Claude/Cursor)
GET /v1/keywords/ranks?keyword=meditation&country=us&limit=10
GET /v1/apps/:id/intelligence # check competitors array
GET /v1/apps/:id # title, subtitle, description
GET /v1/apps/:id/keywords # their ranking keywords
GET /v1/keywords/ranks?keyword=[shared keyword] # who's ranking where
GET /v1/apps/:id/reviews?sort=recent&limit=20
GET /v1/apps/:id # current rating
GET /v1/market/movers?genre=[genre_id]&country=us
GET /v1/categories/:id/top?country=us&limit=25
for APP_ID in "${APPS[@]}"; doWhat does the competitor-tracking skill 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 "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.
How do I install it?
Run `npx skills add Eronred/aso-skills --skill competitor-tracking --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Eronred/aso-skills, a repository with 1,708 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.