CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

73

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

The body is a well-structured, actionable audit rubric with concrete thresholds and a clear output template, scoring well on conciseness and actionability. It loses points on workflow clarity (no explicit validation checkpoints) and progressive disclosure (a large inline scoring rubric with no reference files to split it out).

Suggestions

Add an explicit validation checkpoint before scoring, e.g. 'Confirm data for all 10 factors is collected; if any is missing, request it from the user before computing the ASO Score.'

Move the detailed per-factor scoring rubric into a reference file (e.g. references/audit-factors.md) and keep SKILL.md as a lean overview that links to it, improving progressive disclosure.

Add a short feedback loop for data gaps — when the Appeeky MCP/API is unavailable and the user cannot supply metadata, document how to degrade gracefully per factor.

DimensionReasoningScore

Conciseness

The body is lean reference material — dense per-factor tables with numeric thresholds and scoring anchors — and avoids explaining ASO concepts Claude already knows, assuming Claude's competence; the only mild padding is the opening role line, which still earns its place.

3 / 3

Actionability

Though instruction-only (no executable code), the guidance is concrete and specific: numeric criteria (4.5+ stars, ~30 chars, all 100 keyword chars, top-10 rankings), a defined weighting scheme, and a copy-paste score-card output template.

3 / 3

Workflow Clarity

The flow (Initial Assessment → Data Collection → Audit Framework → Output) is clearly sequenced and the factor tables act as checklists, but there are no explicit validation/verification checkpoints or feedback loops, so it does not reach the level-3 anchor.

2 / 3

Progressive Disclosure

Sections are well-organized with no nested references, but the full 10-factor scoring rubric is substantial inline content that could live in a reference file; with no bundle files present there is no offloading, fitting the 'content that should be separate is inline' anchor.

2 / 3

Total

10

/

12

Passed

Description

100%

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

The description is strong across all dimensions: it names concrete actions, supplies natural trigger phrases, covers both what and when, and disambiguates from sibling skills. It uses third-person voice about the user with no first/second-person penalties.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'full ASO health audit', 'review their App Store listing quality', 'diagnose why their app isn't ranking' — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what (audit, review, diagnose) and when via a clear 'Also use when the user mentions...' clause with concrete triggers, satisfying the 'what AND when with explicit triggers' anchor.

3 / 3

Trigger Term Quality

Provides natural phrases users would say — 'ASO audit', 'ASO score', 'why am I not ranking', 'listing review', 'optimize my app store page' — giving good coverage of likely trigger language.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear ASO niche with distinct triggers and explicitly disambiguates adjacent skills ('For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.'), making misfires unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Eronred/aso-skills
Reviewed

Table of Contents

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.