Loading...
Loading...
Found 32 Skills
When the user's app or update was rejected by Apple App Review or Google Play Review and they need to diagnose why, fix it, and resubmit fast. Use when the user mentions "app rejected", "App Review rejection", "guideline violation", "Apple rejected my app", "Google Play rejected", "Play policy violation", "Resolution Center", "metadata rejection", "binary rejection", "guideline 2.1", "guideline 4.3", "guideline 5.1.1", "Sign in with Apple required", "Apple ID rejection", "Play Store suspension", "appeal", "I need to respond to App Review", or "expedited review". For pre-submission listing health, see aso-audit. For metadata-only fixes, see metadata-optimization.
Beta testing groups and tester management for Google Play closed testing tracks. Use when managing testers and beta groups.
Staged rollout orchestration and monitoring for Google Play releases. Use when implementing gradual release strategies.
Bulk-localize subscription display names, descriptions, and offer tags across all Google Play locales using gplay. Use when you want to fill in subscription metadata for every language without clicking through Play Console manually.
User and grant management for Google Play Console via gplay users and gplay grants commands. Use when asked to manage developer account users, permissions, or app-level access grants.
End-to-end release workflows for Google Play using gpd publish commands, tracks, rollouts, and edit lifecycle. Use when uploading builds or managing releases.
Use when managing Google Play Developer Console metadata, graphics, tracks, app bundles, reviews, subscriptions, or in-app products with the local `play` CLI. Trigger this for Moshi Android Play Store work, especially when editing `/Users/jyo/projects/ai/moshi/marketing/play` assets or debugging `/Users/jyo/projects/tools/play-cli`.
When the user wants to choose, change, or evaluate their App Store / Google Play category and subcategory — including primary vs secondary category trade-offs, chart-rank competitive analysis, category-driven discoverability, and how category choice affects featuring eligibility. Use when the user mentions "which category", "App Store category", "primary category", "secondary category", "change my category", "Health & Fitness vs Lifestyle", "Productivity vs Utilities", "rank higher in a smaller category", "category chart", "subcategory", "Play Store category", or "should I switch categories". For full ASO health beyond category, see aso-audit. For competitor analysis within the chosen category, see competitor-analysis. For chart movements within categories, see market-movers.