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.

72

Quality

87%

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, lean strategy playbook with concrete templates, benchmark data, and a clear diagnostic-to-output workflow. The main weakness is that several tactics are listed as categories rather than actionable steps.

Suggestions

Expand category-level Optimize tactics (e.g., "Social hooks", "Loyalty rewards", "Personalization") with one concrete implementation example or decision criterion each to raise actionability.

For each Optimize bullet, add a brief measurable signal (e.g., target metric or A/B test hypothesis) so the tactic translates directly into an executable experiment.

DimensionReasoningScore

Conciseness

Information-dense tables and templates with virtually no concept-explanation padding; benchmark data and message copy earn their tokens, and the few generic maxims are brief connectors.

3 / 3

Actionability

Provides concrete templates (push-notification copy, output format, cancellation reason→response mapping, benchmark table) but many Optimize tactics stay at category level (e.g., "Social hooks", "Loyalty rewards") without implementation detail, leaving guidance partially incomplete.

2 / 3

Workflow Clarity

Clear lifecycle-staged sequence (Initial Assessment → per-stage Diagnose/Optimize → prioritized Week/Month/Quarter output) with numbered diagnostic checklists and benchmark comparison; no destructive/batch ops requiring validation caps.

3 / 3

Progressive Disclosure

Well-organized into clearly headed sections with easy navigation and no nested references; no bundle files exist to split, and the one `app-marketing-context.md` reference is conditionally checked and one level deep.

3 / 3

Total

11

/

12

Passed

Description

90%

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, well-scoped description with explicit trigger terms and active disambiguation against neighboring skills. Its only gap is framing capabilities as outcomes rather than concrete actions.

DimensionReasoningScore

Specificity

Names the domain and outcomes ("reduce churn, improve user engagement, or increase lifetime value") but describes goals rather than listing concrete actions like diagnose/benchmark/design, so it stops short of the multi-action anchor.

2 / 3

Completeness

Explicitly answers what it does (reduce churn, improve engagement, increase LTV) and when to use it via an explicit "Also use when the user mentions..." clause, so it is not capped at 2.

3 / 3

Trigger Term Quality

Strong natural-term coverage a user would actually say: "retention", "churn", "users leaving", "engagement", "DAU/MAU", "user activation", and "why are users uninstalling".

3 / 3

Distinctiveness Conflict Risk

Clear niche with explicit disambiguation routing ("For onboarding-specific issues, see app-launch. For monetization, see monetization-strategy."), making wrong-skill triggering unlikely.

3 / 3

Total

11

/

12

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.