CtrlK
BlogDocsLog inGet started
Tessl Logo

improve-retention

Diagnose and fix retention problems using behavior design (B=MAP). Use when the user mentions "users sign up but dont stick around", "activation rate", "onboarding friction", "retention metrics", "why users dont complete", "churn analysis", or "aha moment". Also trigger when analyzing cohort retention curves, designing activation milestones, reducing time-to-value for new users, or investigating why users quit after their first session. Covers the Ability Chain, prompt design, and tiny behaviors that compound. For habit loops and variable rewards, see hooked-ux. For intrinsic motivation, see drive-motivation.

75

Quality

92%

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%Weight 40%Scale 1-3

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

A well-structured, actionable skill body that uses progressive disclosure effectively and gives a clear sequenced workflow with diagnostic checkpoints. Its only weakness is mild verbosity from repeated Action Line explanation and the author bio.

Suggestions

Consolidate the duplicate Action Line explanations (core principle vs. the dedicated 'The Action Line' section) to reduce redundancy and save tokens.

Trim or move the 'About the Author' block out of the main body — it is biographical context, not task guidance, and competes with the context window.

Consider removing or shrinking the ASCII Action Line chart if the same mechanics are covered more compactly in references/behavior-model.md.

DimensionReasoningScore

Conciseness

Mostly high-signal (tables, copy patterns, recipe), but the Action Line is explained twice and the ASCII chart plus the 'About the Author' block add length that does not advance the task — could be tightened.

2 / 3

Actionability

Concrete, executable guidance throughout: a Tiny Habits recipe template, diagnostic tables mapping metrics to B=MAP actions, copy patterns, and a starter-step table — copy-paste ready instruction.

3 / 3

Workflow Clarity

The five-step Behavior Design Process is clearly sequenced, and the Quick Diagnostic plus Scoring section provides explicit pass/fail checkpoints with named failing rows — a validation-style feedback loop.

3 / 3

Progressive Disclosure

A clear overview body signals seven one-level-deep references (all verified to exist), each introduced with 'See: ...when/for...' so navigation is easy and content is appropriately split.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 precise, trigger-rich description that clearly states what the skill does and when to invoke it, with explicit routing away from adjacent skills. It avoids fluff and third-person voice is maintained throughout.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Diagnose and fix retention problems', 'analyzing cohort retention curves, designing activation milestones, reducing time-to-value' — matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what ('Diagnose and fix retention problems using behavior design (B=MAP)') and when (a full 'Use when...' plus 'Also trigger when...' clause), the top anchor.

3 / 3

Trigger Term Quality

Rich natural trigger phrases a user would actually say — "activation rate", "onboarding friction", "retention metrics", "churn analysis", "aha moment" — giving good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

Clear niche (retention via behavior design) with explicit deconfliction ('For habit loops and variable rewards, see hooked-ux. For intrinsic motivation, see drive-motivation.'), making wrong-skill triggering unlikely.

3 / 3

Total

12

/

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
wondelai/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.