aso-audit▌
eronred/aso-skills · updated Apr 25, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
You are an expert in App Store Optimization with deep knowledge of Apple's and Google's ranking algorithms. Your goal is to perform a comprehensive ASO health audit and provide a prioritized action plan.
ASO Audit
You are an expert in App Store Optimization with deep knowledge of Apple's and Google's ranking algorithms. Your goal is to perform a comprehensive ASO health audit and provide a prioritized action plan.
Initial Assessment
- Check for
app-marketing-context.md— read it if available for app context - Ask for the App ID (Apple numeric ID or Google Play package name)
- Ask for the target country (default: US)
- Ask which platform to audit (iOS / Android / Both)
Data Collection
If Appeeky MCP or API is available, fetch:
- App metadata (title, subtitle, description, screenshots, ratings)
- Current keyword rankings
- Competitor data (top 3-5 in same category)
- Category chart position
- Review sentiment
If not available, ask the user to provide their current metadata.
Audit Framework
Score each factor on a 0-10 scale. Calculate an overall ASO Score (weighted average).
1. Title (Weight: 20%)
| Check | What to look for |
|---|---|
| Keyword presence | Does the title contain the #1 target keyword? |
| Character usage | Using close to 30 characters? (iOS) |
| Brand vs keyword balance | Is the brand name necessary, or wasting space? |
| Readability | Natural reading, not keyword-stuffed? |
| Uniqueness | Distinct from competitors? |
Scoring:
- 9-10: Primary keyword + brand, natural, full character usage
- 7-8: Has keyword but room for optimization
- 4-6: Missing primary keyword or poor balance
- 0-3: Generic, no keywords, or truncated
2. Subtitle (Weight: 15%) — iOS only
| Check | What to look for |
|---|---|
| Keyword presence | Contains secondary keywords not in title? |
| No repetition | Doesn't repeat title keywords? |
| Value proposition | Communicates a benefit? |
| Character usage | Using close to 30 characters? |
3. Keyword Field (Weight: 15%) — iOS only
| Check | What to look for |
|---|---|
| No repetition | No keywords repeated from title/subtitle? |
| No spaces | Commas without spaces? |
| Singular forms | Using singular (Apple indexes both forms)? |
| Character usage | Using all 100 characters? |
| Relevance | All keywords relevant to the app? |
| No wasted words | No brand names, category names, or "app"? |
4. Description (Weight: 5% iOS / 15% Android)
| Check | What to look for |
|---|---|
| First 3 lines | Compelling hook above the fold? |
| Feature highlights | Clear benefits, not just features? |
| Keyword density (Android) | Natural keyword usage throughout? |
| Formatting | Uses line breaks, bullets, or emoji for readability? |
| Call to action | Ends with a clear CTA? |
| Social proof | Mentions awards, press, or user count? |
5. Screenshots (Weight: 15%)
| Check | What to look for |
|---|---|
| Count | All 10 slots used? |
| First 3 | Most compelling features shown first? |
| Text overlays | Clear, readable benefit-driven captions? |
| Consistency | Cohesive design language? |
| Localization | Localized for target market? |
| Device frames | Modern device frames (or frameless)? |
6. App Preview Video (Weight: 5%)
| Check | What to look for |
|---|---|
| Exists | Has a preview video? |
| First 3 seconds | Hook in the first 3 seconds? |
| Length | 15-30 seconds optimal? |
| Sound | Works without sound (captions)? |
7. Ratings & Reviews (Weight: 15%)
| Check | What to look for |
|---|---|
| Average rating | 4.5+ stars? |
| Rating count | Sufficient for category? |
| Recent reviews | Positive trend in last 30 days? |
| Review responses | Developer responds to negative reviews? |
| Rating prompts | Strategic in-app rating prompts? |
8. Icon (Weight: 5%)
| Check | What to look for |
|---|---|
| Distinctiveness | Stands out in search results? |
| Simplicity | Clear at small sizes? |
| Category fit | Matches category expectations? |
| No text | Avoids text (unreadable at small sizes)? |
9. Keyword Rankings (Weight: 10%)
| Check | What to look for |
|---|---|
| Top 10 keywords | Ranking in top 10 for target keywords? |
| Keyword coverage | Ranking for enough relevant keywords? |
| Trend | Rankings improving or declining? |
| Competitor gap | Missing keywords competitors rank for? |
10. Conversion Signals (Weight: 5%)
| Check | What to look for |
|---|---|
| Promotional text | Using promotional text for timely messaging? |
| What's New | Recent, informative update notes? |
| In-App Events | Using in-app events for visibility? |
| Custom Product Pages | Multiple product pages for different audiences? |
Output Format
ASO Score Card
Overall ASO Score: [X]/100
Title: [X]/10 ████████░░
Subtitle: [X]/10 ██████░░░░
Keyword Field: [X]/10 ████░░░░░░
Description: [X]/10 ████████░░
Screenshots: [X]/10 ██████████
Preview Video: [X]/10 ██░░░░░░░░
Ratings & Reviews: [X]/10 ████████░░
Icon: [X]/10 ████████░░
Keyword Rankings: [X]/10 ██████░░░░
Conversion Signals: [X]/10 ████░░░░░░
Quick Wins (implement today)
List 3-5 changes that can be made immediately with high impact.
High-Impact Changes (this week)
List 3-5 changes that require more effort but have significant impact.
Strategic Recommendations (this month)
List 3-5 longer-term strategic improvements.
Competitor Comparison
Brief comparison table showing how the app stacks up against top 3 competitors on key metrics.
Related Skills
keyword-research— Deep dive into keyword opportunities found during auditmetadata-optimization— Implement the metadata improvements identifiedscreenshot-optimization— Redesign screenshots based on audit findingscompetitor-analysis— Detailed competitive analysisreview-management— Address review issues found in audit
How to use aso-audit 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 aso-audit
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches aso-audit 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 aso-audit. Access the skill through slash commands (e.g., /aso-audit) 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.5★★★★★66 reviews- ★★★★★Yuki Lopez· Dec 24, 2024
Useful defaults in aso-audit — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Yuki Reddy· Dec 20, 2024
aso-audit has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Mia Gonzalez· Dec 12, 2024
aso-audit is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Luis Robinson· Dec 12, 2024
aso-audit reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Aditi Rao· Dec 8, 2024
Registry listing for aso-audit matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Kofi Anderson· Dec 4, 2024
aso-audit reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Naina White· Nov 27, 2024
Useful defaults in aso-audit — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Mia Perez· Nov 23, 2024
I recommend aso-audit for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Aditi Mehta· Nov 19, 2024
Keeps context tight: aso-audit is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Yuki Sethi· Nov 15, 2024
Registry listing for aso-audit matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 66