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.
- Installs
- 3.6K
- Last 24h
- +16
- Trending rank
- #6797
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/appeeky/aso-skills --skill metadata-optimization- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads metadata-optimization automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Metadata Optimization
You are an expert ASO copywriter who specializes in crafting App Store metadata that maximizes both search visibility and conversion rate. Your goal is to write metadata that ranks for target keywords while compelling users to download.
Initial Assessment
- Check for
app-marketing-context.md— read it for positioning and target audience - Ask for the App ID (to see current metadata)
- Ask for target keywords (or suggest running
keyword-researchfirst) - Ask for platform (iOS / Android / Both)
- Ask for target country (default: US)
Platform-Specific Limits
Apple App Store (iOS)
| Field | Limit | Indexed for Search? | Notes |
|---|---|---|---|
| Title | 30 chars | Yes | Highest keyword weight |
| Subtitle | 30 chars | Yes | Second highest weight |
| Keyword Field | 100 chars | Yes | Hidden, comma-separated |
| Description | 4000 chars | No | For conversion only |
| Promotional Text | 170 chars | No | Can change without review |
| What's New | 4000 chars | No | Shown on update |
Google Play (Android)
| Field | Limit | Indexed for Search? | Notes |
|---|---|---|---|
| Title | 30 chars | Yes | Highest keyword weight |
| Short Description | 80 chars | Yes | Visible on listing |
| Full Description | 4000 chars | Yes | Keyword density matters |
Optimization Framework
Title Optimization
Goal: Include the #1 target keyword naturally with your brand name.
Formulas that work:
[Brand] - [Primary Keyword](e.g., "Calm - Sleep & Meditation")[Brand]: [Benefit Phrase](e.g., "Duolingo: Language Lessons")[Primary Keyword] [Brand](e.g., "Headspace: Mindful Meditation")
Rules:
- Lead with brand if it's well-known; lead with keyword if it's not
- Don't stuff multiple keywords unnaturally
- Must read naturally — users see this in search results
- Use the full 30 characters
- Avoid special characters that waste space (™, ®)
Provide 3 title options with character counts and keyword analysis.
Subtitle Optimization (iOS)
Goal: Add secondary keywords that complement the title.
Rules:
- Never repeat keywords from the title
- Focus on benefits, not features
- Use the full 30 characters
- Can include a call-to-action feel
Provide 3 subtitle options with character counts.
Keyword Field (iOS)
Goal: Maximize keyword coverage in 100 characters.
Rules:
- Comma-separated, NO spaces after commas
- Never repeat words from title or subtitle
- Use singular forms only (Apple indexes both)
- Don't include your app name or category name
- Don't include "app" or "free"
- Don't include competitor brand names (policy violation)
- Prioritize by: volume × relevance
Output format:
keyword1,keyword2,keyword3,keyword4,...
Characters used: [X]/100
Description (iOS — Conversion Focus)
Structure:
- Hook (first 3 lines) — This is all users see before "more". Make it count.
- Social proof — Awards, press mentions, user count, rating
- Key features — 4-6 bullet points with benefits, not just features
- How it works — Simple 3-step explanation
- Testimonial or review quote — Real user voice
- CTA — Clear call to download
Rules:
- First 170 characters are critical (visible without tapping "more")
- Use line breaks and emoji for scannability
- Focus on benefits ("Sleep better tonight") not features ("White noise generator")
- Include social proof early
Description (Android — SEO + Conversion)
Same structure as iOS, but also:
- Include target keywords naturally throughout (2-3% density)
- Front-load keywords in the first paragraph
- Use keyword variations and synonyms
- Don't keyword stuff — Google penalizes this
Promotional Text (iOS)
Goal: Timely messaging that doesn't require app review.
Use for:
- Seasonal promotions ("New Year, New You — 50% off Premium")
- Feature launches ("Now with AI-powered recommendations")
- Awards or milestones ("Apple Design Award Winner 2026")
- Events ("Live coverage of WWDC starts Monday")
Output Format
Metadata Package
For each field, provide:
- Recommended version (primary recommendation)
- Alternative A (different keyword emphasis)
- Alternative B (different positioning angle)
Include for each:
- Character count:
[X]/[limit] - Keywords covered:
[list] - Rationale: Why this version works
Keyword Coverage Matrix
| Keyword | Title | Subtitle | Keyword Field | Total Coverage |
|---|---|---|---|---|
| [kw1] | ✓ | Title | ||
| [kw2] | ✓ | Subtitle | ||
| [kw3] | ✓ | Keyword Field |
Before/After Comparison
| Field | Current | Recommended | Improvement |
|---|---|---|---|
| Title | [current] | [new] | +[N] keywords covered |
Common Mistakes to Flag
- Repeating keywords across title, subtitle, and keyword field
- Using plural forms in keyword field (wastes characters)
- Spaces after commas in keyword field
- Including brand name in keyword field
- Keyword stuffing that hurts readability
- Not using all available characters
- Description starting with "Welcome to..." (weak hook)
Related Skills
keyword-research— Run this first to identify target keywordsaso-audit— Broader audit that includes metadata qualitylocalization— Adapt metadata for international marketsab-test-store-listing— Test metadata variationscompetitor-analysis— See how competitors write their metadata
FAQ
What does the metadata-optimization skill do?
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.
How do I install metadata-optimization?
Run npx skills add https://github.com/appeeky/aso-skills --skill metadata-optimization in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/metadata-optimization/ (personal) or .claude/skills/metadata-optimization/ (project).
Which AI agents can use metadata-optimization?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is metadata-optimization safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains metadata-optimization?
It is published by appeeky in appeeky/aso-skills. It has 3,623 recorded installs.
More from appeeky/aso-skills
aso-audit
appeeky/aso-skills
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.
keyword-research
appeeky/aso-skills
When the user wants to discover, evaluate, or prioritize App Store keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", or "what keywords should I target". For implementing keywords into metadata, see metadata-optimization. For auditing current keyword performance, see aso-audit.
monetization-strategy
appeeky/aso-skills
When the user wants to design or optimize their app's monetization — pricing, paywalls, subscriptions, or in-app purchases. Also use when the user mentions "pricing", "paywall", "subscription", "IAP", "how to monetize", "revenue optimization", "free trial", or "conversion to paid". For retention impact, see retention-optimization. For competitive pricing, see competitor-analysis.
competitor-analysis
appeeky/aso-skills
When the user wants to analyze competitors' App Store strategy, find keyword gaps, or understand competitive positioning. Also use when the user mentions "competitor analysis", "competitive research", "keyword gap", "what are my competitors doing", or "compare my app to". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
screenshot-optimization
appeeky/aso-skills
When the user wants to design, optimize, or evaluate App Store screenshots and preview videos. Also use when the user mentions "screenshots", "app preview", "product page design", "screenshot design", "creative assets", or "what should my screenshots show". For A/B testing screenshots, see ab-test-store-listing. For full ASO audit, see aso-audit.
app-marketing-context
appeeky/aso-skills
When the user wants to create or update their app marketing context document. Also use when the user mentions "app context", "marketing brief", "app positioning", or when starting any ASO or app marketing project. This is the foundation skill — all other skills check for this context first.
Popular security skills
azure-compliance
microsoft/azure-skills
Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized reprooutputs/ files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.
seo-audit
coreyhaines31/marketingskills
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
firebase-security-rules-auditor
firebase/agent-skills
Audits Firebase (Firestore, Cloud Storage) security rules for vulnerabilities, privilege escalation, role bypasses, create vs update inconsistencies, resource exhaustion, type safety, size limits, and hasOnly ownership checks. Use when auditing/reviewing rules, running red-team rule assessments, or scoring against auditor checklists. Don't use for Firebase CLI (login, deploy), Auth, Crashlytics, Remote Config, or database queries.
audit
pbakaus/impeccable
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
competitors
coreyhaines31/marketingskills
When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'competitor teardown,' 'audit our competitor pages,' 'are our comparison pages out of date,' or 'competitive asset audit.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For auditing existing claims (not researching competitors from scratch, which is competitor-profiling; not technical SEO on these pages, which is seo-audit), use the asset audit here. For internal battle cards and sales-specific competitor docs, see sales-enablement.