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.
33
0%
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
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 is an extremely weak description that functions essentially as a placeholder. It provides no information about what the skill actually does, lists no natural trigger terms beyond its own name (duplicated), and completely lacks any 'Use when...' guidance. It would be nearly impossible for Claude to reliably select this skill from a pool of analytics-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Analyzes customer churn patterns, calculates retention rates, identifies at-risk segments, builds churn prediction models, and generates cohort retention reports.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about customer churn, attrition rates, retention analysis, subscriber loss, cohort analysis, or customer lifetime value.'
Remove the duplicated trigger term and replace with diverse natural language variations users would actually say, such as 'churn rate', 'customer retention', 'why customers leave', 'attrition', 'user drop-off'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. It only names itself ('Churn Analysis Helper') and its category ('Data Analytics') without describing what it actually does—no mention of specific analyses, metrics, outputs, or operations. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the skill's own name repeated twice ('churn analysis helper'). There are no natural user keywords like 'customer retention', 'attrition rate', 'subscriber loss', 'churn prediction', or 'cohort analysis' that users would naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | While 'churn analysis' is somewhat specific as a domain, the description is so vague that it could overlap with any data analytics skill. Without concrete actions or clear triggers, it provides no meaningful differentiation from other analytics-related skills. | 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 template with no substantive content. It contains only generic boilerplate that repeats the skill name without providing any actual guidance on churn analysis — no SQL queries, no statistical methods, no visualization techniques, no example datasets, and no actionable steps. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable SQL examples for common churn analysis patterns (e.g., cohort retention queries, churn rate calculations, survival analysis queries).
Include a clear multi-step workflow for performing churn analysis: data extraction → cohort definition → metric calculation → visualization → interpretation, with validation at each step.
Provide specific code examples for data visualization (e.g., retention curves, churn heatmaps) using common libraries like matplotlib or a BI tool.
Remove all boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actionable content that teaches Claude how to actually perform churn analysis.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the trigger phrase 'churn analysis helper' excessively, and provides zero domain-specific information about churn analysis. | 1 / 3 |
Actionability | There is no concrete guidance, no code, no SQL queries, no statistical methods, no examples of actual churn analysis. Every section is vague and abstract — it describes what the skill supposedly does without ever doing it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or any sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no references to supporting files, no structured navigation, and no meaningful content organization. No bundle files exist to support it either. | 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
3a2d27d
- 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.