competitor-tracking▌
eronred/aso-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
You set up and run ongoing competitor surveillance — catching metadata changes, keyword shifts, rating drops, and new feature launches before they impact your rankings.
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 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 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
How to use competitor-tracking on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add competitor-tracking
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches competitor-tracking from GitHub repository eronred/aso-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate competitor-tracking. Access the skill through slash commands (e.g., /competitor-tracking) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★28 reviews- ★★★★★Nikhil Gill· Dec 16, 2024
competitor-tracking has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Camila Farah· Nov 11, 2024
We added competitor-tracking from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Naina Choi· Nov 7, 2024
competitor-tracking reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Neel Kapoor· Oct 26, 2024
I recommend competitor-tracking for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Luis Verma· Oct 2, 2024
Solid pick for teams standardizing on skills: competitor-tracking is focused, and the summary matches what you get after install.
- ★★★★★Oshnikdeep· Sep 25, 2024
Solid pick for teams standardizing on skills: competitor-tracking is focused, and the summary matches what you get after install.
- ★★★★★Luis Martin· Sep 5, 2024
competitor-tracking has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Piyush G· Sep 1, 2024
competitor-tracking reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Luis Yang· Aug 24, 2024
Useful defaults in competitor-tracking — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Shikha Mishra· Aug 20, 2024
I recommend competitor-tracking for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 28