/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
$ npx -y skills add eronred/aso-skills --skill metadata-optimization --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/metadata-optimization
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
metadata-optimization.SKILL.mdname: 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
Read more
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
AI agent skills for App Store Optimization (ASO) and mobile app marketing. Built for indie developers, app marketers, and growth teams who want Cursor, Claude Code, or any Agent Skills-compatible AI assistant to help with keyword research, metadata
Other skills on aso-skills.
- /ab-test-store-listing
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For
Open skill - /android-aso
When the user wants to optimize their Google Play Store listing — title, short description, full description, keywords, ratings, or Play Store-specific features. Use when the user mentions "Google Play", "Android", "Play Store", "Play Console", "short description", "full
Open skill - /app-analytics
When the user wants to set up, interpret, or improve their app analytics and tracking. Also use when the user mentions "analytics", "tracking", "metrics", "KPIs", "App Store Connect analytics", "install tracking", "funnel", "attribution", or "how is my app performing". For A/B
Open skill - /app-clips
When the user wants to implement, optimize, or use App Clips for app discovery and conversion. Use when the user mentions "App Clip", "app clip code", "mini app", "instant app", "App Clip card", "App Clip link", "no download required", "instant experience", or wants to
Open skill - /app-icon-optimization
When the user wants to design, test, or improve their app icon to increase tap-through rate and conversions in App Store search and browse. Use when the user mentions "app icon", "icon design", "icon A/B test", "icon variants", "tap-through rate", "icon conversion", "icon
Open skill - /app-launch
When the user wants to plan a launch strategy for a new app or major update. Also use when the user mentions "app launch", "launch plan", "launch checklist", "pre-launch", "launch day", or "how to launch my app". For ongoing ASO after launch, see aso-audit. For paid acquisition
Open skill

