competitor-analysis▌
eronred/aso-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
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.
Competitor Analysis
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.
Initial Assessment
- Check for
app-marketing-context.md— read it for known competitors - Ask for the user's App ID
- Ask for competitor App IDs (or help identify competitors)
- Ask for target country (default: US)
- Ask what they want to learn: keyword gaps, creative strategy, positioning, or all
Competitor Identification
If the user doesn't know their competitors, find them through:
- Category chart — Top apps in the same category
- Keyword overlap — Apps ranking for the same keywords
- Similar apps — Apple's "You Might Also Like" section
- User perception — Ask "What would your users use if your app didn't exist?"
Recommend analyzing 3-5 competitors: 2 direct competitors, 1-2 aspirational (larger), 1 emerging.
Analysis Framework
1. Metadata Comparison
| 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:
- What keywords do competitors prioritize in their title?
- How do they balance brand vs keywords?
- What positioning angle does each take?
- What's their description hook strategy?
2. Keyword Gap Analysis
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 |
|---|
3. Creative Strategy
Screenshots:
- How many do they use? (target: 10)
- What's their first screenshot? (hook)
- Do they use text overlays?
- What features do they highlight first?
- Design style: dark/light, device frames, lifestyle?
- Do they use portrait or landscape?
App Preview Video:
- Do they have one?
- What's the hook?
- How long is it?
Icon:
- Color scheme and style
- How does it stand out in search results?
4. Ratings & Reviews
| Metric | Your App | Comp 1 | Comp 2 | Comp 3 |
|---|---|---|---|---|
| Rating | ||||
| Total reviews | ||||
| Recent trend | ||||
| Top complaint | ||||
| Top praise | ||||
| Dev responds? |
Analyze:
- What do users love about competitors? (feature opportunities)
- What do users hate? (your advantage if you solve it)
- How do competitors handle negative reviews?
5. Growth Signals
| 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? |
6. Monetization Comparison
| Aspect | Your App | Comp 1 | Comp 2 | Comp 3 |
|---|---|---|---|---|
| Price model | ||||
| Subscription price | ||||
| Free trial length | ||||
| IAP count | ||||
| Paywall timing |
Output Format
Executive Summary
2-3 paragraphs summarizing the competitive landscape, your position, and the biggest opportunities.
Competitive Position Map
HIGH VISIBILITY
│
Comp 1 ● │ ● Comp 2
│
LOW ──────────────────┼────────────────── HIGH
RATINGS │ RATINGS
│
You ● │
│
LOW VISIBILITY
Top Opportunities
- Quick Win: [something you can do this week]
- Keyword Gap: [specific keywords to target]
- Creative Edge: [screenshot/video improvement]
- Feature Gap: [what users want that competitors don't offer]
- Market Gap: [underserved segment or country]
Threats to Monitor
- [competitor moves to watch]
- [market trends that could shift dynamics]
Related Skills
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 strategy
How to use competitor-analysis 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-analysis
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches competitor-analysis 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-analysis. Access the skill through slash commands (e.g., /competitor-analysis) 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.4★★★★★31 reviews- ★★★★★Chaitanya Patil· Dec 28, 2024
I recommend competitor-analysis for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Amina Dixit· Dec 8, 2024
Useful defaults in competitor-analysis — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Min Diallo· Nov 27, 2024
competitor-analysis is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Piyush G· Nov 19, 2024
competitor-analysis fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Jin Smith· Oct 18, 2024
competitor-analysis reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Chinedu Srinivasan· Oct 14, 2024
competitor-analysis fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Shikha Mishra· Oct 10, 2024
competitor-analysis has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Diya Garcia· Sep 25, 2024
competitor-analysis has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Neel Harris· Sep 21, 2024
Useful defaults in competitor-analysis — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Lucas Robinson· Sep 17, 2024
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