churn-analysis-helper
Churn Analysis Helper - Auto-activating skill for Data Analytics. Triggers on: churn analysis helper, churn analysis helper Part of the Data Analytics skill category.
36
Quality
3%
Does it follow best practices?
Impact
97%
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/churn-analysis-helper/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 is an extremely weak skill description that provides almost no useful information for skill selection. It consists primarily of the skill name, a redundant trigger phrase, and a category label without any actual description of capabilities or usage guidance. Claude would have no meaningful basis to select this skill over others.
Suggestions
Add specific capabilities: describe what the skill actually does (e.g., 'Analyzes customer churn patterns, calculates retention rates, identifies at-risk customers, generates churn prediction models')
Add a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when analyzing customer retention, predicting churn, investigating why customers leave, or working with subscription/attrition data')
Include natural keyword variations users might mention: 'customer churn', 'retention analysis', 'attrition rate', 'customer loss', 'subscription cancellation'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only the name 'Churn Analysis Helper' and category 'Data Analytics'. There are no specific capabilities listed like 'analyze customer retention', 'identify churn patterns', or 'generate churn reports'. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' (no capabilities listed) and 'when should Claude use it' (no explicit use-when clause, only a redundant trigger phrase). Both components are essentially missing. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'churn analysis helper' repeated twice, which is the skill name itself rather than natural user language. Missing obvious terms like 'customer churn', 'retention analysis', 'attrition', 'customer loss', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'churn analysis' is a specific domain, the lack of detail means it could overlap with general data analytics skills. The mention of 'Data Analytics skill category' suggests potential conflicts with other analytics skills. | 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 churn analysis skill would do, without providing any actual churn analysis guidance. It contains no executable code, no SQL examples, no metrics definitions, no cohort analysis techniques, and no actionable instructions. The content is essentially a placeholder template that fails every dimension of the rubric.
Suggestions
Add concrete SQL examples for calculating churn rate (e.g., monthly active users who didn't return, subscription cancellations by cohort)
Include specific churn metrics definitions and formulas (e.g., customer churn rate = lost customers / total customers at period start)
Provide a clear workflow: 1) Define churn criteria, 2) Query churned users, 3) Segment by attributes, 4) Visualize trends, 5) Identify leading indicators
Add example output formats showing what a churn analysis report should contain (retention curves, cohort tables, risk scores)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about churn analysis. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no SQL queries, no analysis steps, no code examples, no specific techniques for identifying or measuring churn. The skill describes what it claims to do rather than actually instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. There are no steps for conducting churn analysis, no validation checkpoints, and no sequence of operations. The 'step-by-step guidance' mentioned in capabilities is never actually delivered. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no actual content to organize. There are no references to detailed materials, no examples file, and no structured breakdown of churn analysis topics. | 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
0c08951
- 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.