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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable body with executable code, specific thresholds, and a well-sequenced recovery workflow. The main costs are token spend on ASO common knowledge and near-boilerplate platform snippets, and some reference-worthy material inlined in a single file.

Suggestions

Trim the 'Why Ratings Matter for ASO' section and the opening paragraph — Claude already knows that ratings affect ranking and conversion; keep only the iOS-reset vs Android-permanent contrast, which is non-obvious.

Move the Swift/Kotlin API snippets and the app-type prompt-moment table into a references/ file (e.g., references/platform-apis.md), keeping only the behavioral rules (3x/year limit, no prompt after errors) inline.

Add an explicit post-campaign verification step to the recovery timeline (e.g., 'Week 4: compare rating pre/post campaign; if < 0.2 star gained, re-examine targeting criteria') to close the workflow's feedback loop.

Dimension	Reasoning	Score
Conciseness	The 'Why Ratings Matter for ASO' section and intro restate ASO common knowledge ('a 4.8 beats 4.2 at a glance'), and the Swift/Kotlin snippets are near-boilerplate. Mostly efficient, but these sections could be trimmed.	3 / 5
Actionability	Copy-paste-ready SKStoreReviewController and Play In-App Review snippets, a concrete prompt-gate checklist with specific thresholds (Sessions >= 3, Time since install >= 3 days), per-app-type prompt-moment tables, platform frequency limits, and a fill-in output template.	5 / 5
Workflow Clarity	The recovery flow is a sequenced timeline (Day 0 through Week 3) with diagnosis steps, an explicit monitoring checkpoint, and the prompt criteria act as a validation gate. Minor gaps: no explicit re-check step after the prompt campaign concludes.	4 / 5
Progressive Disclosure	Well-organized sections, tables, and clear headers, but at ~180 lines with no reference files, platform API details and the app-type prompt-moment table are candidates for extraction into separate files.	4 / 5
	Total	16 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete capabilities, an explicit 'Use when' clause with a rich set of natural and technical trigger terms, and clear boundary routing to adjacent skills. The only weakness is that the stated actions are goal-level rather than fully concrete operations.

Dimension	Reasoning	Score
Specificity	Lists four distinct actions ('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'), but they are goal-level rather than fully concrete operations, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what (the four capabilities) and when ('Use when the user mentions...') with concrete trigger phrases, plus boundary routing to review-management and aso-audit.	5 / 5
Trigger Term Quality	Ten quoted trigger phrases span natural user language ('ask for review', 'get more reviews', 'rating drop'), synonyms ('low rating', 'recover from 1-star'), and both platform API names ('SKStoreReviewRequest', 'In-App Review API') — comprehensive coverage.	5 / 5
Distinctiveness Conflict Risk	Clear niche (rating prompt timing/targeting) with distinct triggers, and it actively disambiguates its closest neighbors ('For responding to reviews, see review-management. For overall ASO health, see aso-audit.') rather than overlapping them.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Eronred/aso-skills
Path: skills/rating-prompt-strategy/SKILL.md
Commit: 8de1ee1

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.