retention-calculator
Retention Calculator - Auto-activating skill for Data Analytics. Triggers on: retention calculator, retention calculator Part of the Data Analytics skill category.
33
0%
Does it follow best practices?
Impact
93%
1.03xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/12-data-analytics/retention-calculator/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder with no substantive content. It names the skill and its category but provides zero information about what it actually calculates, what inputs it expects, what outputs it produces, or when it should be selected. The trigger terms are just the skill name duplicated.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Calculates customer retention rates, generates cohort retention tables, analyzes churn over time periods, and visualizes retention curves.'
Add a 'Use when...' clause with natural trigger terms like 'retention rate', 'churn analysis', 'cohort retention', 'customer retention', 'user retention', 'how many users came back'.
Remove the duplicated trigger term and expand with varied natural language phrases users would actually say when needing retention analysis.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Retention Calculator') and its category ('Data Analytics') but does not describe any concrete actions like calculating retention rates, analyzing cohorts, generating reports, etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no explicit 'when should Claude use it' clause with meaningful trigger guidance. The 'Triggers on' line is just the skill name repeated. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'retention calculator' repeated twice. There are no natural variations users might say such as 'churn rate', 'customer retention', 'cohort analysis', 'retention rate', or 'user retention'. | 1 / 3 |
Distinctiveness Conflict Risk | Being labeled generically under 'Data Analytics' with no specific actions or distinct triggers means this could easily conflict with any other data analytics skill. Nothing distinguishes it from other calculator or analytics tools. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no substantive content. It contains only generic boilerplate text that could apply to any topic—there are no retention calculation formulas, no SQL examples (e.g., cohort retention queries), no definitions of retention metrics, and no actionable guidance of any kind. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable SQL examples for common retention calculations (e.g., cohort-based retention, rolling retention, day-N retention queries).
Define the key retention metrics and formulas (e.g., retention rate = returning users / cohort size) with specific input/output examples.
Include a clear workflow: 1) Define cohorts, 2) Write retention query, 3) Validate results against expected ranges, 4) Visualize output.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that add no actionable information and replace with actual domain content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know and provides zero domain-specific information about retention calculation. Every section restates the same vague concept without adding value. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no SQL queries, no formulas, no code examples, no specific steps for calculating retention. It describes rather than instructs, with phrases like 'Provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to examples, SQL templates, or related documentation. There is no meaningful structure beyond generic headings. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
4dee593
- 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.