SkillAgentSearch skills...

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.

Install / Use

npx skills add appeeky/aso-skills --skill metadata-optimization

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Supported Platforms

Universal

Tags

Our assessment of metadata-optimization

metadata-optimization scores 86/100 on our quality scale, 271st of 421 Education & Research skills we index.

Its SKILL.md is 5.8 KB long, well organised into 18 sections with 1 code example: a solid amount of guidance for an agent.

With 2,095 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
17/20
Description
15/15
Adoption
14/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so metadata-optimization is actively maintained.
  • Our last check on 2026-11-03 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

metadata-optimization compared with similar skills

All 4 of these similar skills score higher than metadata-optimization; compare them before choosing.

SkillScoreStarsUpdatedFormat
metadata-optimization (this skill)by appeeky862.1k3mo agoSKILL.md
last30days-skillby mvanhorn10068.0ktodayCLAUDE.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install metadata-optimization?
Run npx skills add appeeky/aso-skills --skill metadata-optimization. The install tabs above show the steps for each supported agent.
Which AI agents does metadata-optimization work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is metadata-optimization safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is metadata-optimization still maintained?
The repository was last updated about 3 months ago, so metadata-optimization is actively maintained.

name: metadata-optimization description: 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. metadata: version: 1.0.0

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

  1. Check for app-marketing-context.md — read it for positioning and target audience
  2. Ask for the App ID (to see current metadata)
  3. Ask for target keywords (or suggest running keyword-research first)
  4. Ask for platform (iOS / Android / Both)
  5. 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:

  1. Hook (first 3 lines) — This is all users see before "more". Make it count.
  2. Social proof — Awards, press mentions, user count, rating
  3. Key features — 4-6 bullet points with benefits, not just features
  4. How it works — Simple 3-step explanation
  5. Testimonial or review quote — Real user voice
  6. 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:

  1. Recommended version (primary recommendation)
  2. Alternative A (different keyword emphasis)
  3. 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 keywords
  • aso-audit — Broader audit that includes metadata quality
  • localization — Adapt metadata for international markets
  • ab-test-store-listing — Test metadata variations
  • competitor-analysis — See how competitors write their metadata

Related Skills

View on GitHub
GitHub Stars2.1k
CategoryEducation
Updated2mo ago
Forks126

Languages

MDX

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions