CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

A focused, actionable skill body with good structure, concrete code, and useful tables/templates. The main weakness is workflow_clarity: the recovery/prompt campaigns operate at scale on users but lack explicit validation checkpoints and feedback loops before prompting.

Suggestions

Add explicit validation gates to the prompt campaign (e.g. 'verify each user segment meets all session/crash criteria before prompting') and a validate→fix→retry loop for the recovery workflow.

Tighten the opening 'Why Ratings Matter' section, which lightly restates ASO concepts Claude already knows, to improve token efficiency.

Fill the Output Format placeholders with a short worked example so the template is immediately usable rather than schematic.

DimensionReasoningScore

Conciseness

Mostly lean and well-organized with tables and code that earn their place, though a few explanatory lines (e.g. 'Ratings are an App Store ranking signal and a conversion factor') lightly restate concepts Claude already knows.

4 / 5

Actionability

Provides concrete executable Swift and Kotlin snippets plus specific session/threshold criteria and an output template, with only minor gaps such as placeholder values that the user must fill in.

4 / 5

Workflow Clarity

Recovery and prompt campaigns are sequenced with a day-by-day timeline, but the batch 'aggressive prompt campaign' lacks validation checkpoints to verify criteria are met before prompting, and there is no explicit validate/fix/retry loop.

3 / 5

Progressive Disclosure

Well-structured with clear section headers and a concise overview, and it cleanly defers detail to related skills; no bundle files exist, so references are limited to sibling-skill pointers rather than separate detailed files.

4 / 5

Total

15

/

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 with explicit what/when structure, rich natural trigger terms, and clear boundaries against sibling skills. The only mild gap is that the listed actions are somewhat high-level relative to the tactics detailed in the body.

DimensionReasoningScore

Specificity

Lists several concrete actions (improve star rating, increase ratings volume, optimize review-prompt timing, recover from a bad rating period) but each stays at a fairly high level without enumerating the specific tactics in the body.

4 / 5

Completeness

Explicitly answers both what (improve rating, increase volume, optimize prompt timing, recover from bad period) and when via a 'Use when...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive coverage of natural phrases users would say, including synonyms and specific technical terms like 'SKStoreReviewRequest', 'In-App Review API', 'low rating', 'rating drop', and 'recover from 1-star'.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche with distinct triggers and explicitly boundaries itself against review-management and aso-audit skills, minimizing conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Eronred/aso-skills
Reviewed

Table of Contents

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.