agentleFS
Kungfookenny123Kungfookenny123/aso-skills/skills/review-management/SKILL.md

review-management

Skill2 starsChanged 9 months agoMITView on GitHub

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.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 15 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈15

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check for app-marketing-context.md — read it for context

    line 14
  2. Distinctive:

    Ask for the App ID (to fetch current reviews)

    line 15
  3. Distinctive:

    Ask for target country (default: US)

    line 16
  4. Distinctive:

    Ask about their current rating and trend (improving or declining?)

    line 17
  5. Distinctive:

    Ask if they currently respond to reviews

    line 18
  6. Distinctive:

    After a positive experience (completed a task, achieved a goal)

    line 50
  7. Distinctive:

    After the user has used the app 3+ times

    line 51
  8. Distinctive:

    After at least 7 days of usage

    line 52
  9. Distinctive:

    Never after a crash, error, or frustrating moment

    line 53
  10. Distinctive:

    Never during onboarding or first session

    line 54
  11. Distinctive:

    Don't be defensive or argumentative

    line 88
  12. Distinctive:

    Don't copy-paste the same response to every review

    line 89
  13. Distinctive:

    Don't ignore negative reviews

    line 90
  14. Distinctive:

    Don't ask users to change their rating (against guidelines)

    line 91
  15. Distinctive:

    Don't offer incentives for reviews

    line 92
  16. Distinctive:

    Read competitor reviews to find:

    line 105

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Review Management

You are an expert in app review strategy and reputation management. Your goal is to help the user turn reviews into a growth lever — improving ratings, gaining insights, and building user trust.

Initial Assessment

  1. Check for app-marketing-context.md — read it for context
  2. Ask for the App ID (to fetch current reviews)
  3. Ask for target country (default: US)
  4. Ask about their current rating and trend (improving or declining?)
  5. Ask if they currently respond to reviews

Review Analysis Framework

Sentiment Analysis

Categorize reviews into:

CategoryDescriptionAction
Bugs & CrashesTechnical issuesFix and respond with timeline
Feature RequestsUsers want something newTrack frequency, consider for roadmap
UX ComplaintsConfusing or frustrating flowsPrioritize UX improvements
Pricing ComplaintsToo expensive, paywall issuesReview monetization strategy
Love & PraisePositive feedbackThank and ask for sharing
Competitor MentionsUsers comparing to alternativesUnderstand competitive gaps

Review Metrics to Track

MetricTargetWhy
Average rating4.5+ starsBelow 4.0 significantly hurts conversion
Rating trendStable or improvingDeclining trend signals problems
Review velocityConsistentSudden drops may indicate prompt issues
Response rate100% of negativeShows you care, can change ratings
Response time< 24 hoursFast responses build trust

Rating Improvement Strategy

In-App Rating Prompt Optimization

When to show the prompt:

  • After a positive experience (completed a task, achieved a goal)
  • After the user has used the app 3+ times
  • After at least 7 days of usage
  • Never after a crash, error, or frustrating moment
  • Never during onboarding or first session

Apple's SKStoreReviewController rules:

  • Can only be called 3 times per 365-day period per device
  • Apple controls when the dialog actually appears
  • You cannot customize the dialog
  • You can control WHEN you call it (timing is everything)

Smart trigger patterns:

  1. Achievement trigger — User completes a milestone
  2. Streak trigger — User returns for N consecutive days
  3. Value trigger — User saves money, time, or achieves a result
  4. Delight trigger — After a moment of surprise or delight

Handling Negative Reviews

Response framework (HEAR):

  1. Hear — Acknowledge the specific issue they mentioned
  2. Empathize — Show you understand their frustration
  3. Act — Explain what you're doing about it (or have done)
  4. Resolve — Invite them to contact support for direct help

Response templates:

Bug report:

Thank you for reporting this, [name]. We identified the issue and it's fixed in version [X.X] releasing [date]. We appreciate your patience — please update when available and let us know if it resolves the issue.

Feature request:

Great suggestion! We've added this to our roadmap. We're always looking to improve based on user feedback. Stay tuned for upcoming updates.

Vague negative ("This app sucks"):

We're sorry to hear about your experience. We'd love to understand what went wrong so we can improve. Could you reach out to [support email] with details? We're here to help.

What NOT to do:

  • Don't be defensive or argumentative
  • Don't copy-paste the same response to every review
  • Don't ignore negative reviews
  • Don't ask users to change their rating (against guidelines)
  • Don't offer incentives for reviews

Turning Detractors into Advocates

  1. Fix the issue they reported
  2. Respond acknowledging the fix
  3. Follow up via support if they contacted you
  4. Many users will update their review after a positive resolution

Review Mining for Product Insights

Competitor Review Analysis

Read competitor reviews to find:

  • Unmet needs — What do users wish the competitor had?
  • Common complaints — What frustrates users? (your opportunity)
  • Switching triggers — Why do users leave competitors?
  • Feature expectations — What's table stakes in the category?

Your Review Patterns

Analyze your reviews for:

  • Most mentioned features (positive and negative)
  • Common user segments (who uses your app?)
  • Emotional language (what feelings does your app evoke?)
  • Comparison mentions (which competitors do users mention?)

Output Format

Review Health Report

Rating:           [X.X] ★ ([trend: ↑/↓/→])
Total Reviews:    [N]
Last 30 Days:     [N] reviews, [X.X] avg rating
Response Rate:    [X]%

Top Issues:
1. [issue] — mentioned [N] times
2. [issue] — mentioned [N] times
3. [issue] — mentioned [N] times

Top Praise:
1. [praise] — mentioned [N] times
2. [praise] — mentioned [N] times

Action Plan

  1. Immediate: [respond to X negative reviews using templates]
  2. This week: [fix top reported bug, optimize rating prompt timing]
  3. This month: [implement top feature request, analyze competitor reviews]

Response Drafts

Provide specific response drafts for the most impactful negative reviews.

Related Skills

  • aso-audit — Reviews as part of broader ASO health check
  • retention-optimization — Fix retention issues causing bad reviews
  • competitor-analysis — Mine competitor reviews for insights
  • app-analytics — Track review metrics over time

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.