Agent skill · marketing growth · eronred
rating-prompt-strategy
When the user wants to improve their app's star rating, increase ratings volume, optimize when and how they prompt users for a review, or recover from a bad rating period. Use when the user mentions "app rating", "star rating", "review prompt", "SKStoreReviewRequest", "In-App Review API", "ask for review", "low rating", "rating drop", "get more reviews", or "recover from 1-star". For responding to reviews, see review-management. For overall ASO health, see aso-audit.
Why this skill is useful
Provides specific strategies and code snippets for optimizing app review prompts that are not widely known.
What it needs
About 4k tokens when loaded. Last updated 2026-07-27. 1,725 stars on the source repository.
What this skill does
Rating Prompt Strategy You optimize when, how, and to whom an app shows review prompts — maximizing high ratings while minimizing negative ones. Ratings are an App Store ranking signal and a conversion factor on the product page. Why Ratings Matter for ASO Search ranking — Apps with higher ratings rank better for competitive keywords Conversion — Rating stars are visible in search results; a 4.8 beats 4.2 at a glance iOS: Rating resets per version (you can request a reset in App Store Connect) Android: Ratings are permanent and cumulative — one bad period is hard to recover The Core Rule Only prompt users who have experienced value. Prompting too early produces low ratings. Prompting at a success moment produces 4–5 star ratings. iOS — SKStoreReviewRequest Apple's native prompt. Rules: Shows at most 3 times per year regardless of how many times you call it Apple controls the display logic — calling it doesn't guarantee it shows Never prompt after an error, crash, or frustrating moment Cannot customize the prompt UI Android — Play In-App Review API Google's native prompt. Rules: No hard limits, but Google throttles it if called too often Show after a clear positive moment Cannot determine if the user actually rated (privacy) Timing Framework The Success Moment Trigger Define 1–3 "success moments" in your app where users are most satisfied: App Type Good Prompt Moments Bad Prompt Moments ---------- -------------------- -------------------- Fitness After completing a workout After skipping a session Productivity After completing a project/task After a failed save or sync error Games After winning a level or beating a boss After losing or failing Finance After first successful transaction After a confusing error Meditation After completing a session On cold open Shopping After a successful purchase/delivery After a failed checkout Session-Based Rules Only prompt users who meet all criteria: Pre-Prompt Survey (Recommended) Before triggering the native prompt, show a sing …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills eronred/rating-prompt-strategy