Back to Skills

review-management

When the user wants to analyze, respond to, or improve their app reviews and ratings. Also use when the user mentions "reviews", "ratings", "negative reviews", "how to get more reviews", "review response", or "my rating is dropping". For broader ASO audit, see aso-audit. For retention issues causing bad reviews, see retention-optimization.

1,520stars100forksUpdated 6/23/2026

Security Assessment

Safe(100/100)
Security Score100/100

About review-management

The review-management skill helps a developer analyze, respond to, and improve their app reviews and ratings, turning reviews into a growth lever for ratings, insights, and user trust. It assesses the app's current rating, trend, and whether the developer currently responds.

It provides a review analysis framework that categorizes feedback (bugs and crashes, feature requests, UX complaints, pricing complaints, praise, competitor mentions) with recommended actions, plus review metrics and targets. For ratings improvement it covers in-app rating prompt timing and Apple's SKStoreReviewController rules, smart trigger patterns, and a HEAR response framework (Hear, Empathize, Act, Resolve) with response templates and explicit do-nots such as never asking users to change their rating or offering incentives. It also covers mining your own and competitor reviews for product insights, and outputs a review health report, an action plan, and specific response drafts.

It is most useful for app developers and marketers who want to raise their rating, respond effectively to negative reviews, and extract product insights from review data.

FAQ

When should I use this skill?

When you want to analyze, respond to, or improve your app reviews and ratings, especially if your rating is dropping or you want more reviews.

How does it categorize reviews?

Into bugs and crashes, feature requests, UX complaints, pricing complaints, love and praise, and competitor mentions, each with a recommended action.

How should I respond to negative reviews?

Using the HEAR framework (Hear, Empathize, Act, Resolve) with tailored templates, never being defensive, copy-pasting, ignoring, or asking users to change their rating.

When should the in-app rating prompt appear?

After a positive experience and several uses, never after a crash or during onboarding, and within Apple's limit of three prompts per device per year.

What does it output?

A review health report (rating, trend, top issues and praise, response rate), an action plan, and specific response drafts for the most impactful negative reviews.

Install review-management

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill