Communitygithub.com

asodevapp/skills

Use when the user wants Google Play Store or Android ASO: Play listing title, short description, full description, keyword strategy, feature graphic, screenshots, ratings/reviews, Play Store Experiments, localization, or Google Play-specific metadata via ASO.dev.

O que é skills?

skills is a Claude Code agent skill that use when the user wants Google Play Store or Android ASO: Play listing title, short description, full description, keyword strategy, feature graphic, screenshots, ratings/reviews, Play Store Experiments, localization, or Google Play-specific metadata via ASO.dev.

Funciona com~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/asodevapp/skills/tree/HEAD/skills/android-aso

Perguntar na sua IA favorita

Abre um novo chat com esta habilidade de agente já pré-carregada.

Documentação

Android ASO

Use this for Google Play Store optimization. Google Play differs from iOS: full descriptions are indexed, there is no hidden keyword field, and store listing experiments are native in Play Console.

MCP workflow

  1. Use app-store-connect-mcp.
  2. Read current Play metadata with get_google_editor_data.
  3. Read project context when positioning, audience, category, or monetization matters.
  4. Draft Google-specific metadata and creative recommendations.
  5. Validate with validate_ai_companion_data target googleMetadata.
  6. If asked to apply, fill with bulk_fill_google.

Google Play vs iOS

FactorGoogle PlayApple App Store
Indexed fieldsTitle, short description, full descriptionTitle, subtitle, keyword field
Hidden keyword fieldNoYes
Full descriptionIndexed and conversionConversion-focused
ExperimentsStore Listing ExperimentsPPO
Feature graphicImportant Play creative assetNot used
RatingsLong-running listing signalApp Store rating/review signal

Field limits

FieldLimitRole
Title30Highest keyword + conversion weight
Short description80Search result copy and indexed relevance
Full description4000Indexed relevance + conversion

Metadata strategy

Title

  • Use brand plus one strong keyword/descriptor when natural.
  • Do not keyword-stuff or make unverifiable "best" claims.
  • Keep readable in search results.

Short description

  • Use one compelling sentence.
  • Include 1-3 high-priority terms naturally.
  • Do not simply repeat the title.
  • Make the value clear without tapping through.

Full description

Recommended structure:

  1. Hook paragraph with core value and primary keyword early; the first ~250 characters should work before expansion.
  2. Benefit-led feature bullets.
  3. Trust/proof only if real.
  4. How it works or use cases.
  5. CTA.
  6. Natural keyword variants and long-tail terms.

Keyword guidance:

  • Use exact match, variants, and synonyms naturally.
  • Long-tail phrases can work because full description is indexed.
  • Do not create a visible keyword dump.
  • If keyword data is missing, use keyword-coverage before final copy.

Creative strategy

  • Feature graphic: communicate the core use case quickly; avoid tiny text; keep it aligned with title and short description.
  • Screenshots: at least 2 are required; first 2-3 should explain value, proof, and key workflow.
  • Use screenshot-brief for screenshot copy and creative direction.
  • Keep Play screenshots and feature graphic consistent with metadata claims.

Ratings and reviews

  • Low ratings hurt conversion and may affect visibility.
  • Use reviews-ratings for review analysis and replies.
  • Prompt users after positive value moments, not on cold start or after errors.
  • Do not incentivize ratings.

Play Store Experiments

Use Play Console experiments for:

  • icon
  • feature graphic
  • screenshots
  • short description
  • full description

Test one primary hypothesis at a time. Keep locale, traffic source, and seasonality in mind when interpreting results.

Localization

Google Play indexes listing text per language. Do not auto-translate keywords. Use localization-cross-localization for market choice and local keyword adaptation.

Output

# Google Play ASO Plan

App:
Package:
Country:
Locale:
Category:
Target keywords:

## Audit
| Area | Score | Issue | Fix |
|---|---:|---|---|

## Listing draft
### Title
`...`
Characters:

### Short description
`...`
Characters:

### Full description
...
Characters:

## Keyword coverage
| Keyword | Title | Short description | Full description | Notes |
|---|---|---|---|---|

## Creative recommendations
- Feature graphic:
- Screenshot sequence:
- Experiment idea:

## Validation
- Character limits:
- Keyword stuffing avoided:
- Unsupported claims removed:
- Localization checked:
- MCP validation:
- Ready for `bulk_fill_google`:

Rules

  • Do not invent Play Console data, rankings, install volume, ratings, or experiment results.
  • Do not use iOS-only keyword-field logic for Google Play.
  • Do not recommend review incentives or deceptive rating prompts.
  • Keep full description readable; indexed does not mean stuffed.

Individual skills in this repo

This repo contains 10 individual skills — each has its own dedicated page.

asodevapp/skills

Use when the user wants to interpret ASO.dev Measurements or App Store Connect metrics: downloads, impressions, product page views, conversion, revenue, retention, sessions, active devices, ratings, reviews, release markers, experiment impact, or before/after ASO performance.

asodevapp/skills

Use to read, create, or update ASO.dev per-app project context before metadata, localization, keywords, screenshots, IAP, subscriptions, pricing, In-App Events, nominations, or review work.

asodevapp/skills

Use when the user wants a full ASO audit or health check for an app: metadata, keyword coverage, cross-localization, screenshots, reviews, ratings, update history, In-App Events, IAP/subscriptions, CPP/PPO, competitors, rankings, or ASO.dev ASO Check interpretation.

asodevapp/skills

Use when the user wants App Store Custom Product Pages, Product Page Optimization, A/B testing, conversion rate optimization, product page variants, screenshot/icon/app preview tests, campaign pages, keyword/ad alignment, or CPP/PPO drafts in ASO.dev.

asodevapp/skills

Use when the user wants to create, plan, audit, optimize, localize, or fill App Store In-App Events in ASO.dev: event cards for Today/Games/Apps tabs, search, product pages, re-engagement, challenges, competitions, live events, premieres, seasons, major updates, and special events.

asodevapp/skills

Use for App Store consumable and non-consumable In-App Purchases: metadata, localization, pricing/availability notes, promoted IAP readiness, validation, and ASO.dev local MCP fill when that surface is available.

asodevapp/skills

Use for keyword ideas, keyword prioritization, keyword/search query CSV-derived shortlists, competitor keyword gaps, Search Ads Popularity interpretation, and keyword distribution across metadata/locales.

asodevapp/skills

Use when the user wants to write, rewrite, optimize, compare, validate, or bulk-fill Apple App Store or Google Play metadata in ASO.dev: title, subtitle, keyword field, description, promotional text, short description, full description, or What's New.

asodevapp/skills

Use when the user wants to analyze, respond to, report, or improve App Store reviews and ratings in ASO.dev: negative reviews, ratings trend, review replies, review complaints, review health, product insights, uploaded review CSV analysis, sentiment, missing feature requests, or rating prompt strategy.

asodevapp/skills

Use to prepare screenshot copy, screenshot order, creative briefs, and App Store / Google Play visual messaging.

Habilidades Relacionadas