metadata-optimization
Skill2.2k starsChanged 9 months agoMITView on GitHub
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.
5 other projects use a version of this.
Trending
Quiet since March.thin dataabout the whole repository
Most recently taken up by
- AppKittie/aso-mcp-skillstheir own version, first seen Nov 8, 2026
- Nirusan/claude-configtheir own version, first seen Oct 13, 2026
- trysonar/skillstheir own version, first seen Oct 1, 2026
- appeeky/aso-skillsword for word, first seen Feb 27, 2026
- Kungfookenny123/aso-skillsword for word, first seen Feb 27, 2026
Who's talking about Eronred/aso-skills
The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.
Used with
Projects with it also use revenue-analysis and review-analysis.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
trysonarSkillrevenue-analysis
When the user wants to estimate or benchmark app revenue and downloads — validating an app idea, sizing a niche, comparing monetization across apps, or reading their own App Store Connect sales on the App Store or Google Play. Also use when the user mentions "how much does this app make", "revenue estimate", "app downloads estimate", "market size", "is this niche profitable", or "my sales". For finding the apps to benchmark, see market-discovery. For full competitor teardowns, see competitor-analysis.
Also in 3 projects that use this
liangdabiaoSkillreview-analysis
对亚马逊商品评论进行深度分析,自动识别产品痛点、分析退货原因,生成改进建议和客服回复模板。Invoke when user uses /review-analysis command with a product ASIN.
Also in 3 projects that use this
Other versions5 projects use a version of this.
Word for word · 2
- appeeky/aso-skills★ 2.2k100% same
- Kungfookenny123/aso-skills★ 2100% same
Edited · 0
None found.
Wrote their own version · 3
- AppKittie/aso-mcp-skills★ 8same name
- Nirusan/claude-config★ 7same name
- trysonar/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository41 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- ab-test-store-listingSkill
- android-asoSkill
- app-analyticsSkill
- app-clipsSkill
- app-icon-optimizationSkill
- app-launchSkill
- apple-search-adsSkill
- app-marketing-contextSkill
- app-preview-videoSkill
- app-rejection-recoverySkill
- app-store-featuredSkill
- asc-metricsSkill
- aso-auditSkill
- aso-routerSkill
- attribution-setupSkill
- category-positioningSkill
- competitor-analysisSkill
- competitor-trackingSkill
- crash-analyticsSkill
- creator-ugc-marketingSkill
- custom-product-pagesSkill
- in-app-eventsSkill
- keyword-researchSkill
- localizationSkill
- market-moversSkill
- market-pulseSkill
- monetization-strategySkill
- onboarding-optimizationSkill
- paywall-optimizationSkill
- press-and-prSkill
- rating-prompt-strategySkill
- referral-programSkill
- retention-optimizationSkill
- review-managementSkill
- screenshot-optimizationSkill
- seasonal-asoSkill
- subscription-lifecycleSkill
- ua-campaignSkill
- web-to-app-funnelSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. 0 are common, 18 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
18
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Check for app-marketing-context.md — read it for positioning and target audience
- Distinctive: line 15
Ask for the App ID (to see current metadata)
- Very specific: line 16
Ask for target keywords (or suggest running keyword-research first)
- Distinctive: line 17
Ask for platform (iOS / Android / Both)
- Distinctive: line 18
Ask for target country (default: US)
- Distinctive: line 54
Don't stuff multiple keywords unnaturally
- Distinctive: line 55
Must read naturally — users see this in search results
- Distinctive: line 56
Use the full 30 characters
- Distinctive: line 57
Avoid special characters that waste space (™, ®)
- Distinctive: line 63
Goal: Add secondary keywords that complement the title.
- Distinctive: line 66
Never repeat keywords from the title
- Distinctive: line 79
Never repeat words from title or subtitle
- Distinctive: line 80
Use singular forms only (Apple indexes both)
- Distinctive: line 81
Don't include your app name or category name
- Distinctive: line 82
Don't include "app" or "free"
- Distinctive: line 83
Don't include competitor brand names (policy violation)
- Distinctive: line 104
Use line breaks and emoji for scannability
- Distinctive: line 113
Use keyword variations and synonyms
- Distinctive: line 114
Don't keyword stuff — Google penalizes this
- Distinctive: line 161
Not using all available characters
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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]/100Description (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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

