SKILLS/aso-audit/SKILL.md
When the user wants a full ASO health audit, review their App Store listing quality, or diagnose why their app isn't ranking. Also use when the user mentions "ASO audit", "ASO score", "why am I not ranking", "listing review", or "optimize my app store page". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
npx skillsauth add pinkpixel-dev/skills-collection-1 aso-auditInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
app-marketing-context.md — read it if available for app contextIf Appeeky MCP or API is available, fetch:
If not available, ask the user to provide their current metadata.
Score each factor on a 0-10 scale. Calculate an overall ASO Score (weighted average).
| 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:
| 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? |
| 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"? |
| 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? |
| 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)? |
| 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)? |
| 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? |
| 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)? |
| 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? |
| 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? |
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 ████░░░░░░
List 3-5 changes that can be made immediately with high impact.
List 3-5 changes that require more effort but have significant impact.
List 3-5 longer-term strategic improvements.
Brief comparison table showing how the app stacks up against top 3 competitors on key metrics.
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 audittesting
Clarify requirements before implementing. Use when serious doubts arise.
tools
Complete reference and build guide for ASI:One (ASI1) — the AI platform by Fetch.ai built for agentic, Web3-native applications. Use this skill IMMEDIATELY and ALWAYS when the user mentions ASI1, ASI:One, Fetch.ai AI API, building with ASI1, integrating ASI:One, asking about ASI1 models, tool calling with ASI1, ASI1 image generation, ASI1 agentic LLM, Agentverse, uagents, Agent Chat Protocol, structured output with ASI1, or OpenAI-compatible wrappers for ASI1. Also trigger when the user says things like "use ASI1 instead of OpenAI", "build an app with ASI:One", "ASI1 API", or references docs.asi1.ai. This skill covers everything needed to build production apps - setup, all models, all API features, tool calling, image gen, agentic orchestration, structured data, session management, streaming, LangChain integration, uagents / Agent Chat Protocol, and TypeScript/Node.js patterns.
data-ai
When the user wants to analyze their own app's actual performance data from App Store Connect — real downloads, revenue, IAP, subscriptions, trials, or country breakdowns synced via Appeeky Connect. Use when the user asks about "my downloads", "my revenue", "how is my app performing", "ASC data", "sales and trends", "my subscription numbers", "App Store Connect metrics", or wants to compare periods or top markets. For third-party app estimates, see app-analytics. For subscription analytics depth, see monetization-strategy.
tools
Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.