CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

74

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a well-structured, highly actionable review-management playbook with concrete templates and frameworks. It is slightly verbose in spots and could benefit from optional reference-file splits and more explicit validation checkpoints in the workflow.

Suggestions

Tighten the opening paragraph (e.g., remove the "You are an expert..." framing) and trim any elaborative sentences that restate what the tables already convey.

Add an explicit validation/verification checkpoint in the workflow (e.g., confirm review categorization before drafting responses, or verify response tone against the "What NOT to do" list before sending).

Consider moving the response template library and competitor-review-mining detail into a reference file (e.g., references/response-templates.md) and summarizing it inline, keeping SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

Mostly efficient using tables, frameworks (HEAR), and templates rather than prose, but the opening "You are an expert..." line and a few elaborative sentences could be trimmed for a fully lean result.

4 / 5

Actionability

Provides copy-paste-ready response templates with placeholders, a concrete HEAR framework, named trigger patterns, specific SKStoreReviewController rules, and a structured output format that cover the common cases.

5 / 5

Workflow Clarity

The Initial Assessment and Action Plan give clear sequenced steps with guardrails ("What NOT to do"), though explicit validation/checkpoint phrasing for the analysis-to-response loop could be stronger.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and inline tables/templates that are appropriate for a strategy skill, though some material (competitor review mining, full template library) could optionally be split into reference files.

4 / 5

Total

17

/

20

Passed

Description

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

The description is exemplary: it states concrete capabilities, provides numerous natural trigger phrases, answers both what and when explicitly, and disambiguates from sibling skills via routing clauses. No changes needed.

DimensionReasoningScore

Specificity

Names multiple concrete actions ("analyze, respond to, or improve their app reviews and ratings") with comprehensive coverage of the review-management domain, matching the anchor for several specific actions.

5 / 5

Completeness

Explicitly answers both what (analyze/respond/improve reviews and ratings) and when ("Also use when the user mentions...") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural phrases users actually say ("reviews", "ratings", "negative reviews", "how to get more reviews", "review response", "my rating is dropping") with synonyms, matching comprehensive natural-term coverage.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (app review management) and explicitly routes overlapping cases to aso-audit and retention-optimization, minimizing conflict risk.

5 / 5

Total

20

/

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.