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.

Quality

82%

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

65%

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

A well-structured, highly actionable ASO copywriting framework with concrete rules, formulas, and output templates, weakened mainly by absent validation checkpoints in the workflow and a monolithic body that does not split detail into reference files.

Suggestions

Add an explicit verification step to the workflow — e.g., after drafting metadata, check each field against its character limit, confirm no keyword overlap across title/subtitle/keyword field, and validate against the 'Common Mistakes' list before delivering.

Split the detailed field-limit tables and output-format templates (keyword coverage matrix, before/after comparison) into a reference file under references/ and point to it from SKILL.md to improve progressive disclosure.

Tighten repeated guidance such as 'Use the full 30 characters' (stated in multiple sections) and trim soft commentary like 'Make it count' to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly dense and actionable with no beginner-concept fluff, but contains mild padding ('Make it count', repeated 'Use the full 30 characters') and a few sections that could be tightened, fitting the 'mostly efficient but could be tightened' anchor rather than the lean top anchor.	2 / 3
Actionability	Provides fully concrete, copy-paste-ready guidance — exact character limits, title formulas like '[Brand] - [Primary Keyword]', specific keyword-field rules (no spaces after commas, singular forms), and explicit output templates (keyword coverage matrix, before/after table).	3 / 3
Workflow Clarity	The 'Initial Assessment' gives a clear numbered intake sequence, and the output format defines a structured deliverable, but there are no explicit validation/verification checkpoints and the sequence is intake-only rather than a full produce-then-verify loop.	2 / 3
Progressive Disclosure	Content is well-organized into clear sections with one-level-deep inline references (app-marketing-context.md, Related Skills), but it is a ~163-line monolithic single file carrying detailed tables and matrices that could be split into reference bundles, and no bundle files are present.	2 / 3
	Total	9 / 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.

A strong, concrete description that clearly states what the skill does and when to use it, with natural trigger terms and explicit cross-references to avoid conflicts with related ASO skills. It hits the top anchor on every dimension.

Dimension	Reasoning	Score
Specificity	Names multiple concrete, specific actions and fields — 'optimize App Store metadata — title, subtitle, keyword field, or description' — rather than vague abstractions, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both 'what' (optimize App Store metadata fields) and 'when' ('Also use when the user mentions...') with explicit trigger guidance, satisfying the top anchor.	3 / 3
Trigger Term Quality	Includes natural phrases a user would actually say — 'optimize my title', 'ASO metadata', 'keyword field', 'character limits', 'app description', 'write my subtitle' — giving good coverage of real-world trigger terms.	3 / 3
Distinctiveness Conflict Risk	A clear ASO-metadata niche with distinct triggers, plus explicit routing to sibling skills ('For keyword discovery, see keyword-research. For full ASO audits, see aso-audit') that reduces overlap and misfiring.	3 / 3
	Total	12 / 12 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/metadata-optimization/SKILL.md
Commit: f97c943

Reviewed: about 4 hours 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.