- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add rshankras/claude-code-apple-skills --skill ratings-mechanics -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add rshankras/claude-code-apple-skills --skill ratings-mechanics -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add rshankras/claude-code-apple-skills --skill ratings-mechanics -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add rshankras/claude-code-apple-skills --skill ratings-mechanics -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/rshankras/claude-code-apple-skills/tree/HEAD/skills/app-store/ratings-mechanicsFrom the publisher
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.Two ASC toggles turn a bad build from a rating catastrophe into a contained incident:
requestReview — never at launch, never mid-task. Aim the
moment, cap the frequency, and localize what "success" means per market. Implementation:
generators/review-prompt.app-store/review-response-writer.When auditing an app's ratings posture, report per storefront:
Storefront | Rating (count) | Unanswered 1–3★ (90d) | Prompt localized? | Phased+manual habit?
flagging: fresh storefronts with no prompting plan, any reset consideration (🔴 stop), and releases going out unphased.
generators/review-prompt, app-store/review-response-writer, product/localization-strategy, growth/store-growth-auditHow 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/repl
---name: ratings-mechanicsdescription: How App Store ratings actually behave — per-storefront isolation (your US stars show nowhere else), the…---# skills/app-store/ratings-mechanics/SKILL.mdOverview
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. Use when planning ratings strategy for new markets, considering a ratings reset, setting release options, or diagnosing "why is my rating missing in country X.
FAQ
Download skills/app-store/ratings-mechanics/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/rshankras/claude-code-apple-skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.