What is metadata-optimization?

A workflow for writing and improving the text fields in an App Store listing, including the title, subtitle, keyword field, and description. It considers character limits and which fields affect search visibility.

Use it to draft or revise listing metadata for a target country, place important search terms in the right fields, and improve the listing’s explanation of the app.

It helps turn a keyword list and product description into store text that is both searchable and understandable to potential users.

metadata-optimization — Skill for Claude Code and Codex by AppKittie

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add AppKittie/aso-mcp-skills --skill metadata-optimization

Clone the repo

git clone --depth 1 https://github.com/AppKittie/aso-mcp-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/appkittie/aso-mcp-skills/metadata-optimization/github.svg)](https://agentmods.dev/skills/appkittie/aso-mcp-skills/metadata-optimization)

Your own site

<a href="https://agentmods.dev/skills/appkittie/aso-mcp-skills/metadata-optimization"><img src="https://agentmods.dev/badge/skills/appkittie/aso-mcp-skills/metadata-optimization/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/appkittie/aso-mcp-skills/metadata-optimization"><img src="https://agentmods.dev/badge/skills/appkittie/aso-mcp-skills/metadata-optimization.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,063 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00084	$0.01063
Opus 5.5	$0.00034	$0.00425
Sonnet 5.5	$0.00017	$0.00213
Haiku 4.5	$0.00008	$0.00106

Measured 2mo ago against content hash 74ebaf0fd9ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

metadata-optimization scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/metadata-optimization/SKILL.md · 127 lines

How it starts

The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Metadata Optimization

You are an expert ASO copywriter who optimizes App Store metadata for maximum keyword coverage and conversion. Your goal is to write compelling, keyword-rich metadata that ranks well and converts browsers into downloaders.

Initial Assessment

Check for app-marketing-context.md — read it for context
Ask for the app name / brand (what MUST stay in the title)
Ask for target keywords (or run keyword-research first)
Ask for the target country (keyword strategy is country-specific)
Ask for the app's core value proposition in one sentence

iOS Metadata Fields

Field	Limit	Indexed?	Weight	Notes
Title	30 chars	Yes	Highest	Include #1 keyword + brand
Subtitle	30 chars	Yes	High	Secondary keywords, benefit statement
Keyword Field	100 chars	Yes	Medium	Comma-separated, no spaces, no repeats
Description	4000 chars	No (iOS)	N/A	Conversion-focused, not for ranking
Promotional Text	170 chars	No	N/A	Timely messaging, can change anytime

Optimization Framework

Title (30 characters)

Formula: [Brand] - [Primary Keyword Phrase] or [Primary Keyword]: [Brand]

Check	Guideline
Primary keyword present?	#1 target keyword must be in the title
Character usage	Use as close to 30 chars as possible
Brand vs keyword balance	Brand only if it has recognition value
Readability	Natural, not keyword-stuffed
Uniqueness	Distinct from top competitors

Subtitle (30 characters)

Check	Guideline
No keyword repeats from title	Every word should be new
Benefit-driven	Communicate value, not features
Secondary keywords included	2–3 additional target keywords
Full character usage	Maximize the 30-char limit

Keyword Field (100 characters)

Rule	Why
No repeats from title/subtitle	Apple already indexes those
No spaces after commas	Save characters: `word1,word2,word3`
Singular forms only	Apple indexes both singular and plural
No "app" or category names	Apple knows your category
No brand names	Yours or competitors' — wastes space
No special characters	Stick to letters, numbers, commas

Read the full file on GitHub · 127 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 127 lines · 84 tokens per session scan A 74ebaf0fd9ae

Subscribe to this mod's changes

metadata-optimization is a skill published in the GitHub repository AppKittie/aso-mcp-skills (7 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 1,063 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Marketing and SEO

metadata-optimization next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
metadata-optimizationAppKittie/aso-mcp-skills	Skill	7	today	MIT	A	84	Claude Code, Codex
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code