CtrlK
BlogDocsLog inGet started
Tessl Logo

retention-optimization

When the user wants to reduce churn, improve user engagement, or increase lifetime value. Also use when the user mentions "retention", "churn", "users leaving", "engagement", "DAU/MAU", "user activation", or "why are users uninstalling". For onboarding-specific issues, see app-launch. For monetization, see monetization-strategy.

61

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/retention-optimization/SKILL.md
SKILL.md
Quality
Evals
Security

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.

The body is a well-structured, actionable retention playbook that supplies genuinely non-obvious domain data (benchmarks, message templates, cancellation flows) without over-explaining basics. It is consistently strong across dimensions with only minor tightening and organizational opportunities.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no preamble defining retention or mobile apps — and the benchmark tables and push-notification templates are domain-specific data Claude would not reliably know, so tokens mostly earn their place; minor overlap between the two notification tables could be trimmed.

4 / 5

Actionability

Provides concrete, executable guidance: category benchmark tables, day-by-day push-notification message templates, a specific cancellation-flow decision tree, and a copy-paste output-format template; minor gaps keep it just below fully-copy-paste-ready at 5.

4 / 5

Workflow Clarity

A clear sequence runs from Initial Assessment (numbered 1–5) through the four-phase framework (each with Diagnose/Optimize) to a structured Output Format; this advisory skill has no destructive/batch operations, so the missing-validation cap does not apply, and the assessment step acts as a soft checkpoint.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and a self-contained structure; no bundle files exist (references/, scripts/, assets/ absent), and the only external mentions are app-marketing-context.md and a Related Skills section, so it is appropriately structured but over the 50-line simple-skill threshold that would allow a 5.

4 / 5

Total

16

/

20

Passed

Description

67%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 excels at trigger-term coverage and distinctiveness with strong disambiguation, but it lacks an explicit statement of what the skill does, leaving the 'what' only weakly implied through outcome goals.

Suggestions

Lead with an explicit 'what' clause naming concrete actions, e.g. 'Diagnoses mobile app retention issues and produces a prioritized retention plan.'

Keep the strong trigger list but pair it with the action statement so both 'what' and 'when' are explicit.

Consider adding a brief scope qualifier (e.g. 'for mobile apps') to the opening sentence rather than burying it in implied context.

DimensionReasoningScore

Specificity

The description names the domain ("reduce churn, improve user engagement, or increase lifetime value") but states no concrete actions the skill performs — there is no verb describing what it does (e.g. diagnose, plan), only outcome goals, matching the 'names the domain but actions are minimal or generic' anchor.

2 / 5

Completeness

It has strong, explicit 'when' trigger guidance but only an implied 'what' (the goals in the opening clause); no statement of what the skill actually does, so it does not reach the both-what-and-when anchors at 4–5.

3 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including synonyms and acronyms — "retention", "churn", "users leaving", "engagement", "DAU/MAU", "user activation", and the natural phrase "why are users uninstalling" — matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

Clear mobile-retention niche with explicit disambiguation ("For onboarding-specific issues, see app-launch. For monetization, see monetization-strategy."), minimizing conflict risk with adjacent growth skills.

5 / 5

Total

15

/

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.