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
Install / Use
npx skills add appeeky/aso-skills --skill rating-prompt-strategyInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of rating-prompt-strategy
rating-prompt-strategy scores 93/100 on our quality scale, 708th of 4,700 Development & Engineering skills we index (top 16%).
Its SKILL.md is 6.4 KB long, well organised into 18 sections with 6 code examples: a thorough specification that gives an agent plenty to work with.
With 2,095 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 3 months ago, so rating-prompt-strategy is actively maintained.
- Our last check on 2026-10-26 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit ā read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk ā read a skill before letting an agent act on it.
rating-prompt-strategy compared with similar skills
All 4 of these similar skills score higher than rating-prompt-strategy; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| rating-prompt-strategy (this skill)by appeeky | 93 | 2.1k | 3mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
Frequently asked questions
- How do I install rating-prompt-strategy?
- Run
npx skills add appeeky/aso-skills --skill rating-prompt-strategy. The install tabs above show the steps for each supported agent. - Which AI agents does rating-prompt-strategy work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is rating-prompt-strategy safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is rating-prompt-strategy still maintained?
- The repository was last updated about 3 months ago, so rating-prompt-strategy is actively maintained.
Skill content
View source on GitHubname: rating-prompt-strategy description: 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. metadata: version: 1.0.0
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
import StoreKit
// Call at the right moment
if let scene = UIApplication.shared.connectedScenes.first as? UIWindowScene {
SKStoreReviewController.requestReview(in: scene)
}
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)
val manager = ReviewManagerFactory.create(context)
val request = manager.requestReviewFlow()
request.addOnCompleteListener { task ->
if (task.isSuccessful) {
val reviewInfo = task.result
val flow = manager.launchReviewFlow(activity, reviewInfo)
flow.addOnCompleteListener { /* proceed */ }
}
}
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:
Criteria to prompt:
ā Sessions >= 3 (not a first-time user)
ā Time since install >= 3 days
ā Has completed [activation event] at least once
ā No crash in last session
ā No negative signal (error, cancellation) in current session
ā Not already rated this version
Pre-Prompt Survey (Recommended)
Before triggering the native prompt, show a single in-app question:
"Are you enjoying [App Name]?"
[Yes, love it!] [Not really]
- "Yes" ā trigger
SKStoreReviewRequest/ Play In-App Review - "Not really" ā show a feedback form (email or in-app), do not trigger the native prompt
This filters out dissatisfied users before they can rate you 1ā2 stars.
Expected improvement: 0.3ā0.8 stars on average with a pre-prompt filter.
Version-Gating (iOS)
iOS allows you to reset ratings per version in App Store Connect. Use this strategically:
- Reset after a major improvement ā If you fixed the top-complained issues
- Do not reset after a controversial change that users disliked
- After a reset, run an aggressive (but filtered) prompt campaign in the first 7 days
- Target your most engaged users first (longest session history)
Recovering from a Rating Drop
Diagnosis
- Check which version caused the drop ā correlate with release dates
- Read the 1-star reviews for that period ā find the common complaint
- Fix the issue in the next release
- Reply to every 1ā3 star review (see
review-managementskill)
Recovery Campaign
After the fix is shipped:
- Reply to negative reviews: "Fixed in version X.X ā please update and let us know"
- Some users will update their rating after a reply
- Run a prompt campaign targeted at your most loyal users (highest session count)
- Do not prompt users who left a negative review
Timeline
Day 0: Issue identified ā hotfix or patch in progress
Day 1ā3: Reply to every negative review acknowledging the issue
Day 7: Fix shipped ā reply to previous negative reviews "Fixed in X.X"
Day 8+: Enable prompt for sessions >= 5, no crash last 7 days
Week 3: Monitor rating trend ā should recover 0.2ā0.5 stars in 2ā4 weeks
Prompt Frequency
| Platform | Maximum | Recommended | |----------|---------|-------------| | iOS | 3Ć per 365 days (Apple-enforced) | 1ā2Ć per version | | Android | No hard limit (Google throttles) | 1Ć per 30 days per user |
Never show the prompt twice in the same session.
Output Format
Rating Strategy Plan
Current rating: [X.X] ā
([N] ratings)
Platform: iOS / Android / Both
Success moments identified:
1. [Event name] ā fires when [condition]
2. [Event name] ā fires when [condition]
Pre-prompt survey: Yes / No
If yes: "Are you enjoying [App Name]?" ā Yes / Not really
Prompt trigger logic:
Sessions >= [N]
Days since install >= [N]
No crash in last [N] sessions
[Activation event] completed: yes
Already rated this version: no
Expected outcome: +[X] stars over [N] weeks
Recovery plan (if rating < 4.0):
1. [Fix] ā ship by [date]
2. [Reply strategy] ā [N] reviews to address
3. [Prompt campaign] ā start [date], target [segment]
Related Skills
review-managementā Respond to reviews to recover ratingonboarding-optimizationā Fix activation issues that drive 1-star reviewsandroid-asoā Play In-App Review API contextretention-optimizationā Engaged users give better ratings
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu ā one CLI, zero API fees.
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit ā see the Safety scan above for what the skill file itself contains.
