Retention Calculator - Auto-activating skill for Data Analytics. Triggers on: retention calculator, retention calculator Part of the Data Analytics skill category.
35
Quality
3%
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
7%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 severely underdeveloped and essentially just restates the skill name without providing any meaningful information. It lacks concrete actions, natural trigger terms, and explicit usage guidance. Claude would struggle to know when to select this skill or what it actually does.
Suggestions
Add specific actions the skill performs, e.g., 'Calculates customer retention rates, analyzes cohort retention over time, measures churn metrics, and generates retention reports.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user asks about customer retention, churn analysis, cohort retention, user drop-off, or retention metrics.'
Specify the type of retention (customer, user, employee) and the outputs/deliverables to distinguish from other analytics skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Retention Calculator') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of calculating, analyzing, measuring, or any specific operations. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' guidance is just a redundant repetition of the skill name. There is no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'retention calculator' repeated twice. This is extremely narrow and misses natural variations users might say like 'customer retention', 'churn rate', 'user retention analysis', 'cohort analysis', or 'retention metrics'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'retention calculator' is somewhat specific as a concept, the lack of detail about what kind of retention (customer, employee, data) or what calculations are performed creates potential overlap with other analytics skills. The category mention 'Data Analytics' is too broad to help distinguish it. | 2 / 3 |
Total | 5 / 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 entirely meta-content describing what a retention calculator skill would do, without providing any actual retention calculation guidance. It lacks SQL queries for cohort analysis, retention formulas, visualization examples, or any concrete implementation details. The content is essentially a placeholder that would provide no value to Claude when activated.
Suggestions
Add concrete SQL examples for calculating retention (e.g., cohort-based retention queries, DAU/MAU calculations, churn rate formulas)
Include specific retention metric definitions and calculation methods (Day-N retention, rolling retention, bracket retention)
Provide example output formats showing how to present retention data (tables, visualization recommendations)
Remove all meta-description content ('This skill provides...', 'When to Use...') and replace with actionable instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no SQL queries, no code examples, no specific retention calculation formulas or methods. The skill describes what it claims to do rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. Claims to provide 'step-by-step guidance' but contains no actual steps for calculating retention metrics. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no structure pointing to actual implementation details, examples, or reference materials. | 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 | |
0c08951
Table of Contents
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.