aso-audit

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.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable audit framework with a clear output format, but it lacks validation/verification checkpoints in its batch workflow and leaves the data-fetch mechanism underspecified.

Suggestions

Add a validation checkpoint after Data Collection — confirm metadata and ranking data were retrieved before scoring, and add a verify step that the weighted factor scores reconcile to the reported overall ASO Score.

Specify how to fetch data (which Appeeky MCP tool/endpoint or exact API call) rather than 'fetch app metadata' so the data-collection step is executable, or define a clear fallback format for user-supplied metadata.

Trim the opening persona line and convert prose like 'Your goal is to perform a comprehensive ASO health audit...' into a direct instruction to save context tokens.

Dimension	Reasoning	Score
Conciseness	Mostly lean checklists and tables with no basic-concept padding, but the opening role-play line ('You are an expert in App Store Optimization...') and a few prose sentences could be trimmed.	4 / 5
Actionability	Concrete audit factors, a 0-10 scoring scheme, weights, and a copy-paste-ready score-card output format make the guidance actionable; the main gap is that the data-collection step ('If Appeeky MCP or API is available, fetch...') leaves the fetch mechanism unspecified.	4 / 5
Workflow Clarity	The Initial Assessment → Data Collection → Audit Framework → Output sequence is clear, but this batch analytical workflow has no validation checkpoints (e.g. verifying fetched data before scoring, or confirming scores reconcile to the weighted total), which caps the score per the rubric.	3 / 5
Progressive Disclosure	Well-organized single-file structure with clear section headers and a one-level-deep 'Related Skills' pointer list; no bundle files exist, so the long inline per-factor scoring tables are the only mild organization gap.	4 / 5
	Total	15 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with explicit what/when structure, natural trigger phrases, and clear disambiguation from related skills. The only mild gap is that the action list is solid but not exhaustive.

Dimension	Reasoning	Score
Specificity	Names the ASO domain and several concrete actions ('review their App Store listing quality', 'diagnose why their app isn't ranking'), but stops short of a fully comprehensive action list.	4 / 5
Completeness	Explicitly answers both what (full ASO health audit, review listing quality, diagnose ranking) and when, with a dedicated 'Use when the user mentions...' clause listing concrete trigger phrases.	5 / 5
Trigger Term Quality	Quotes natural user utterances with good synonym coverage — 'ASO audit', 'ASO score', 'why am I not ranking', 'listing review', 'optimize my app store page' — exactly the phrases a user would say.	5 / 5
Distinctiveness Conflict Risk	Has a clear ASO-audit niche with distinct triggers and explicitly routes adjacent needs to sibling skills ('see keyword-research', 'see metadata-optimization'), minimizing conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Eronred/aso-skills
Path: skills/aso-audit/SKILL.md
Commit: 4df730f

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.