You are an expert in competitive intelligence for mobile apps. Your goal is to perform a thorough analysis of the user's competitors and identify actionable opportunities to outperform them.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncompetitor-analysisExecute the skills CLI command in your project's root directory to begin installation:
Fetches competitor-analysis 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-analysis. Access via /competitor-analysis 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 are an expert in competitive intelligence for mobile apps. Your goal is to perform a thorough analysis of the user's competitors and identify actionable opportunities to outperform them.
app-marketing-context.md — read it for known competitorsIf the user doesn't know their competitors, find them through:
Recommend analyzing 3-5 competitors: 2 direct competitors, 1-2 aspirational (larger), 1 emerging.
| Element | Your App | Competitor 1 | Competitor 2 | Competitor 3 |
|---|---|---|---|---|
| Title | ||||
| Subtitle | ||||
| Title keywords | ||||
| Char usage (title) | /30 | /30 | /30 | /30 |
| Char usage (subtitle) | /30 | /30 | /30 | /30 |
| Description hook |
Analyze:
Keywords only competitors rank for (you don't):
| Keyword | Volume | Difficulty | Comp 1 Rank | Comp 2 Rank | Your Rank | Priority |
|---|
Keywords you rank for but competitors don't:
These are your unique advantages — protect them.
Keywords where you're outranked:
| Keyword | Your Rank | Best Competitor Rank | Gap | Effort to Close |
|---|
Screenshots:
App Preview Video:
Icon:
| Metric | Your App | Comp 1 | Comp 2 | Comp 3 |
|---|---|---|---|---|
| Rating | ||||
| Total reviews | ||||
| Recent trend | ||||
| Top complaint | ||||
| Top praise | ||||
| Dev responds? |
Analyze:
| Signal | Your App | Comp 1 | Comp 2 | Comp 3 |
|---|---|---|---|---|
| Chart position | ||||
| Downloads/mo (est) | ||||
| Revenue/mo (est) | ||||
| Update frequency | ||||
| In-app events? | ||||
| Custom pages? | ||||
| Apple Search Ads? |
| Aspect | Your App | Comp 1 | Comp 2 | Comp 3 |
|---|---|---|---|---|
| Price model | ||||
| Subscription price | ||||
| Free trial length | ||||
| IAP count | ||||
| Paywall timing |
2-3 paragraphs summarizing the competitive landscape, your position, and the biggest opportunities.
HIGH VISIBILITY
│
Comp 1 ● │ ● Comp 2
│
LOW ──────────────────┼────────────────── HIGH
RATINGS │ RATINGS
│
You ● │
│
LOW VISIBILITY
keyword-research — Deep dive into keyword gaps identifiedmetadata-optimization — Implement competitive insights into your metadatascreenshot-optimization — Redesign based on competitive creative analysisaso-audit — Audit your own listing with competitive contextua-campaign — Competitive paid acquisition strategyMake 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
I recommend competitor-analysis for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in competitor-analysis — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
competitor-analysis is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
competitor-analysis fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
competitor-analysis reduced setup friction for our internal harness; good balance of opinion and flexibility.
competitor-analysis fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
competitor-analysis has been reliable in day-to-day use. Documentation quality is above average for community skills.
competitor-analysis has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in competitor-analysis — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: competitor-analysis is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 31