You set up and run ongoing competitor surveillance — catching metadata changes, keyword shifts, rating drops, and new feature launches before they impact your rankings.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncompetitor-trackingExecute the skills CLI command in your project's root directory to begin installation:
Fetches competitor-tracking from eronred/aso-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate competitor-tracking. Access via /competitor-tracking in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
696
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
696
stars
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-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) |
app-marketing-context.mdUse Appeeky to identify competitors if unknown:
GET /v1/keywords/ranks?keyword=meditation&country=us&limit=10
GET /v1/apps/:id/intelligence # check competitors array
Check weekly using Appeeky:
GET /v1/apps/:id # title, subtitle, description
Watch for:
GET /v1/apps/:id/keywords # their ranking keywords
GET /v1/keywords/ranks?keyword=[shared keyword] # who's ranking where
Watch for:
GET /v1/apps/:id/reviews?sort=recent&limit=20
GET /v1/apps/:id # current rating
Watch for:
GET /v1/market/movers?genre=[genre_id]&country=us
GET /v1/categories/:id/top?country=us&limit=25
Watch for:
Manually check every 4–6 weeks:
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]
Run a full competitor-analysis when:
Set a calendar reminder. Run the Appeeky API calls above. Fill the template.
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.
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.
| 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 |
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 gapsMake data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
competitor-tracking has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added competitor-tracking from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
competitor-tracking reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend competitor-tracking for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: competitor-tracking is focused, and the summary matches what you get after install.
Solid pick for teams standardizing on skills: competitor-tracking is focused, and the summary matches what you get after install.
competitor-tracking has been reliable in day-to-day use. Documentation quality is above average for community skills.
competitor-tracking reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in competitor-tracking — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend competitor-tracking for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 28