Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rshankras/ratings-mechanics
How App Store ratings actually behave — per-storefront isolation (your US stars show nowhere else), the never-reset rule, phased release + manual release as rating protection, and where prompting/replying fit.
Passed 22 of 23 test cases with the skill, and 18 of 23 without it.
and 2 more in the full report
5 fixed17 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
When auditing an App Store Connect setup where a team plans to reset the rating summary on release, what explicit indicator should be raised in the audit report?
| Checked | Without skill | With skill |
|---|---|---|
| Flags the rating reset proposal with a explicit stop warning sign. | Missed | Passed |
The instructions your model reads when the skill loads.
The rating is an asset with mechanics most developers learn the hard way. This skill covers the
four rules that aren't obvious from the ASC UI. Prompting code lives in
generators/review-prompt; reply writing lives in app-store/review-response-writer — this
skill is the strategy layer that tells you when each matters.
product/localization-strategyYour 4.8★ from 2,000 US ratings renders as no rating at all on the Japanese storefront until Japanese users rate the app there. Every storefront starts from zero.
Consequences:
requestReview triggers by storefront maturity — a market with 12 ratings needs the
prompt more than the home market with 5,000.ASC offers a reset when you release a new version. It is almost always a mistake:
review-response-writer) and by the What's New copy.test cases passed, vs 18 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.