Manage — App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and G
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Manage — App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and G
triggers
["ASO","app store optimization","app store ranking","app keywords","app metadata","play store optimization","app store listing","improve app rankings","app visibility","app store SEO","mobile app marketing","app conversion rate"]
Write subtitle (iOS) or short description (Android):
Focus on primary benefit
Include secondary keyword
Use action verbs
Optimize keyword field (iOS only):
Remove duplicates from title
Remove plurals (Apple indexes both forms)
No spaces after commas
Prioritize by score
Rewrite full description:
Hook paragraph with value proposition
Feature bullets with keywords
Social proof section
Call to action
Validate character counts for each field
Calculate keyword density (target 2-3% primary)
Validation: All fields within character limits; primary keyword in title; no keyword stuffing (>5%); natural language preserved
Platform Character Limits
Field
Apple App Store
Google Play Store
Title
30 characters
50 characters
Subtitle
30 characters
N/A
Short Description
N/A
80 characters
Keywords
100 characters
N/A
Promotional Text
170 characters
N/A
Full Description
4,000 characters
4,000 characters
What's New
4,000 characters
500 characters
Description Structure
PARAGRAPH 1: Hook (50-100 words)
├── Address user pain point
├── State main value proposition
└── Include primary keyword
PARAGRAPH 2-3: Features (100-150 words)
├── Top 5 features with benefits
├── Bullet points for scanability
└── Secondary keywords naturally integrated
PARAGRAPH 4: Social Proof (50-75 words)
├── Download count or rating
├── Press mentions or awards
└── Summary of user testimonials
PARAGRAPH 5: Call to Action (25-50 words)
├── Clear next step
└── Reassurance (free trial, no signup)
TEST ID: ASO-2025-001
ELEMENT: App Icon
HYPOTHESIS: A bolder color icon will increase conversion by 10%
START DATE: [Date]
END DATE: [Date]
RESULTS:
├── Control CVR: 4.2%
├── Treatment CVR: 4.8%
├── Lift: +14.3%
├── Significance: 97%
└── Decision: Implement treatment
LEARNINGS:
- Bold colors outperform muted tones in this category
- Apply to screenshot backgrounds for next test
Before/After Examples
Title Optimization
Productivity App:
Version
Title
Analysis
Before
"MyTasks"
No keywords, brand only (8 chars)
After
"MyTasks - Todo List & Planner"
Primary + secondary keywords (29 chars)
Fitness App:
Version
Title
Analysis
Before
"FitTrack Pro"
Generic modifier (12 chars)
After
"FitTrack: Workout Log & Gym"
Category keywords (27 chars)
Subtitle Optimization (iOS)
Version
Subtitle
Analysis
Before
"Get Things Done"
Vague, no keywords
After
"Daily Task Manager & Planner"
Two keywords, benefit clear
Keyword Field Optimization (iOS)
Before (Inefficient - 89 chars, 8 keywords):
task manager, todo list, productivity app, daily planner, reminder app
MyTasks is a comprehensive task management solution designed
to help busy professionals organize their daily activities
and boost productivity.
After:
Forget missed deadlines. MyTasks keeps every task, reminder,
and project in one place—so you focus on doing, not remembering.
Trusted by 500,000+ professionals.
Improvements:
Leads with user pain point
Specific benefit (not generic "boost productivity")
Manage — App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and G
When to Use
Use this skill when the task requires app store optimization capabilities.
What If Fails
If this skill fails to produce the expected output: (1) verify input completeness, (2) retry with more specific context, (3) fall back to the parent workflow without this skill.
