CtrlK
BlogDocsLog inGet started
Tessl Logo

metadata-optimization

When the user wants to optimize App Store metadata — title, subtitle, keyword field, or description. Also use when the user mentions "optimize my title", "ASO metadata", "keyword field", "character limits", "app description", or "write my subtitle". For keyword discovery, see keyword-research. For full ASO audits, see aso-audit.

70

Quality

85%

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

82%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 ASO copywriting skill with concrete templates, examples, and a mistake-checklist. It is efficient and clearly sequenced, with only minor room to tighten prose or split detailed reference material into bundle files.

Suggestions

Add an explicit validation step in the workflow (e.g., verify character counts against limits and confirm no keyword repetition across title/subtitle/keyword field) before producing the final output package.

Consider moving the platform-specific limit tables and per-field optimization frameworks into a reference bundle file to shorten SKILL.md and improve progressive disclosure.

Trim a few prescriptive 'Provide 3 options' directives or fold them into the Output Format section to reduce repetition.

DimensionReasoningScore

Conciseness

Largely lean, signal-dense content (character-limit tables, formulas, rules) that assumes ASO domain knowledge; only minor sections could be tightened further.

4 / 5

Actionability

Provides copy-paste-ready templates: title formulas with real examples, a keyword-field output format, character-count notation, and structured output deliverables (Metadata Package, Coverage Matrix, Before/After).

5 / 5

Workflow Clarity

Clear sequence from Initial Assessment (numbered 1-5) through per-field optimization to output, with a 'Common Mistakes to Flag' checklist acting as validation; minor gaps in explicit verification checkpoints.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with cohesive inline reference material; no bundle files exist, and the ~170-line body is appropriately structured though some detailed frameworks could optionally be split out.

4 / 5

Total

17

/

20

Passed

Description

87%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 that clearly states the skill's purpose, surfaces natural trigger phrases, and disambiguates from sibling skills via explicit cross-references. It is concise, third-person, and answers both 'what' and 'when'.

DimensionReasoningScore

Specificity

Names the domain ('optimize App Store metadata') and enumerates concrete fields ('title, subtitle, keyword field, or description'), giving several specific targets with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ('optimize App Store metadata — title, subtitle, keyword field, or description') and when ('Also use when the user mentions...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrases like 'optimize my title', 'ASO metadata', 'keyword field', 'character limits', 'app description', and 'write my subtitle'; good coverage though a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Clear ASO-metadata niche with distinct triggers and explicit boundary guidance ('For keyword discovery, see keyword-research. For full ASO audits, see aso-audit.'), minimizing conflict risk.

5 / 5

Total

18

/

20

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.