App Store Optimization (ASO) Skill workflow skill. Use this skill when the user needs Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
App Store Optimization (ASO) Skill workflow skill. Use this skill when the user needs Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/app-store-optimization from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
App Store Optimization (ASO) Skill This comprehensive skill provides complete ASO capabilities for successfully launching and optimizing mobile applications on the Apple App Store and Google Play Store.
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Capabilities, Input Requirements, Output Formats, How to Use, Scripts, Limitations.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
This skill is applicable to execute the workflow or actions described in the overview.
Use when the request clearly matches the imported source intent: Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store.
Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
Use when provenance needs to stay visible in the answer, PR, or review packet.
Use when copied upstream references, examples, or scripts materially improve the answer.
Use when the workflow should remain reviewable in the public intake repo before the private enhancer takes over.
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
HOW_TO_USE.md
Starts with the smallest copied file that materially changes execution
Supporting context
README.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
Read the overview and provenance files before loading any copied upstream support files.
Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
Validate the result against the upstream expectations and the evidence you can point to in the copied files.
Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.
Imported Workflow Notes
Imported: Capabilities
Research & Analysis
Keyword Research: Analyze keyword volume, competition, and relevance for app discovery
Competitor Analysis: Deep-dive into top-performing apps in your category
Market Trend Analysis: Identify emerging trends and opportunities in your app category
Review Sentiment Analysis: Extract insights from user reviews to identify strengths and issues
Category Analysis: Evaluate optimal category and subcategory placement strategies
Metadata Optimization
Title Optimization: Create compelling titles with optimal keyword placement (platform-specific character limits)
Description Optimization: Craft both short and full descriptions that convert and rank
Subtitle/Promotional Text: Optimize Apple-specific subtitle (30 chars) and promotional text (170 chars)
Keyword Field: Maximize Apple's 100-character keyword field with strategic selection
Category Selection: Data-driven recommendations for primary and secondary categories
Icon Best Practices: Guidelines for designing high-converting app icons
Screenshot Optimization: Strategies for creating screenshots that drive installs
Preview Video: Best practices for app preview videos
Localization: Multi-language optimization strategies for global reach
Conversion Optimization
A/B Testing Framework: Plan and track metadata experiments for continuous improvement
Visual Asset Testing: Test icons, screenshots, and videos for maximum conversion
Store Listing Optimization: Comprehensive page optimization for impression-to-install conversion
Call-to-Action: Optimize CTAs in descriptions and promotional materials
Rating & Review Management
Review Monitoring: Track and analyze user reviews for actionable insights
Response Strategies: Templates and best practices for responding to reviews
Rating Improvement: Tactical approaches to improve app ratings organically
Issue Identification: Surface common problems and feature requests from reviews
Launch & Update Strategies
Pre-Launch Checklist: Complete validation before submitting to stores
Launch Timing: Optimize release timing for maximum visibility and downloads
Update Cadence: Plan optimal update frequency and feature rollouts
Feature Announcements: Craft "What's New" sections that re-engage users
Seasonal Optimization: Leverage seasonal trends and events
Analytics & Tracking
ASO Score: Calculate overall ASO health score across multiple factors
Keyword Rankings: Track keyword position changes over time
Download Velocity: Track download trends and momentum
Performance Benchmarking: Compare against category averages and competitors
Platform-Specific Requirements
Apple App Store:
Title: 30 characters
Subtitle: 30 characters
Promotional Text: 170 characters (editable without app update)
Description: 4,000 characters
Keywords: 100 characters (comma-separated, no spaces)
What's New: 4,000 characters
Google Play Store:
Title: 50 characters (formerly 30, increased in 2021)
Short Description: 80 characters
Full Description: 4,000 characters
No separate keyword field (keywords extracted from title and description)
Examples
Example 1: Ask for the upstream workflow directly
Use @app-store-optimization to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @app-store-optimization against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @app-store-optimization for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @app-store-optimization using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
Volume vs. Competition: Balance high-volume keywords with achievable rankings
Relevance First: Only target keywords genuinely relevant to your app
Long-Tail Strategy: Include 3-4 word phrases with lower competition
Competitor Keywords: Don't copy blindly; ensure relevance to your features
Metadata Optimization
Front-Load Keywords: Place most important keywords early in title/description
Natural Language: Write for humans first, SEO second
Feature Benefits: Focus on user benefits, not just features
A/B Test Everything: Test titles, descriptions, screenshots systematically
Update Regularly: Refresh metadata every major update
Character Limits: Use every character—don't waste valuable space
Apple Keyword Field: No plurals, duplicates, or spaces between commas
Visual Assets
Icon: Must be recognizable at small sizes (60x60px)
Screenshots: First 2-3 are critical—most users don't scroll
Captions: Use screenshot captions to tell your value story
Consistency: Match visual style to app design
A/B Test Icons: Icon is the single most important visual element
Reviews & Ratings
Respond Quickly: Reply to reviews within 24-48 hours
Professional Tone: Always courteous, even with negative reviews
Address Issues: Show you're actively fixing reported problems
Thank Supporters: Acknowledge positive reviews
Prompt Strategically: Ask for ratings after positive experiences
Launch Strategy
Soft Launch: Consider launching in smaller markets first
PR Timing: Coordinate press coverage with launch
Update Frequently: Initial updates signal active development
Monitor Closely: Track metrics daily for first 2 weeks
Iterate Quickly: Fix critical issues immediately
Localization
Prioritize Markets: Start with English, Spanish, Chinese, French, German
Native Speakers: Use professional translators, not machine translation
Cultural Adaptation: Some features resonate differently by culture
Test Locally: Have native speakers review before publishing
Measure ROI: Track downloads by locale to assess impact
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/app-store-optimization, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
@00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/n/a
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/n/a
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
{"app_name":"MyApp","category":"Productivity","target_keywords":["task manager","productivity","todo list"],"competitors":["Todoist","Any.do","Microsoft To Do"],"language":"en-US"}
Hey Claude—I just added the "app-store-optimization" skill. Can you research the best keywords for a productivity app targeting professionals? Focus on keywords with good search volume but lower competition.
Optimize App Store Listing
Hey Claude—I just added the "app-store-optimization" skill. Can you optimize my app's metadata for the Apple App Store? Here's my current listing: [provide current metadata]. I want to rank for "task management" and "productivity tools".
Analyze Competitor Strategy
Hey Claude—I just added the "app-store-optimization" skill. Can you analyze the ASO strategies of Todoist, Any.do, and Microsoft To Do? I want to understand what they're doing well and where there are opportunities.
Review Sentiment Analysis
Hey Claude—I just added the "app-store-optimization" skill. Can you analyze recent reviews for my app (com.myapp.ios) and identify the most common user complaints and feature requests?
Calculate ASO Score
Hey Claude—I just added the "app-store-optimization" skill. Can you calculate my app's overall ASO health score and provide specific recommendations for improvement?
Plan A/B Test
Hey Claude—I just added the "app-store-optimization" skill. I want to A/B test my app icon and first screenshot. Can you help me design the test and determine how long to run it?
Pre-Launch Checklist
Hey Claude—I just added the "app-store-optimization" skill. Can you generate a comprehensive pre-launch checklist for submitting my app to both Apple App Store and Google Play Store?
Imported: Scripts
keyword_analyzer.py
Analyzes keywords for search volume, competition, and relevance. Provides strategic recommendations for primary and secondary keywords.
Keyword search volume estimates are approximate (no official data from Apple/Google)
Competitor data may be incomplete for private apps
Review analysis limited to public reviews (can't access private feedback)
Historical data may not be available for new apps
Platform Constraints
Apple App Store keyword changes require app submission (except Promotional Text)
Google Play Store metadata changes take 1-2 hours to index
A/B testing requires significant traffic for statistical significance
Store algorithms are proprietary and change without notice
Industry Variability
ASO benchmarks vary significantly by category (games vs. utilities)
Seasonality affects different categories differently
Geographic markets have different competitive landscapes
Cultural preferences impact what works in different countries
Scope Boundaries
Does not include paid user acquisition strategies (Apple Search Ads, Google Ads)
Does not cover app development or UI/UX optimization
Does not include app analytics implementation (use Firebase, Mixpanel, etc.)
Does not handle app submission technical issues (provisioning profiles, certificates)
When NOT to Use This Skill
For web apps (different SEO strategies apply)
For enterprise apps not in public stores
For apps in beta/TestFlight only
If you need paid advertising strategies (use marketing skills instead)
Imported: Integration with Other Skills
This skill works well with:
Content Strategy Skills: For creating app descriptions and marketing copy
Analytics Skills: For analyzing download and engagement data
Localization Skills: For managing multi-language content
Design Skills: For creating optimized visual assets
Marketing Skills: For coordinating broader launch campaigns
Imported: Version & Updates
This skill is based on current Apple App Store and Google Play Store requirements as of November 2025. Store policies and best practices evolve—verify current requirements before major launches.
Key Updates to Monitor:
Apple App Store Connect updates (apple.com/app-store/review/guidelines)
Google Play Console updates (play.google.com/console/about/guides/releasewithconfidence)
iOS/Android version adoption rates (affects device testing)
Store algorithm changes (follow ASO blogs and communities)
