CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill churn-analysis-helper
What are skills?

Overall
score

17%

Does it follow best practices?

Validation for skill structure

SKILL.md
Review
Evals

Activation

0%

This description is essentially a placeholder with no substantive content. It lacks any concrete capabilities, meaningful trigger terms, or guidance on when to use the skill. The only information provided is the skill name and a generic category label, making it nearly useless for skill selection among multiple options.

Suggestions

Add specific capabilities: 'Analyzes customer churn patterns, calculates retention rates, identifies at-risk customers, generates cohort analysis reports'

Include natural trigger terms users would say: 'Use when user mentions customer churn, retention analysis, attrition, customer loss, why customers leave, or subscription cancellations'

Add explicit 'Use when...' clause that distinguishes this from general data analytics skills, focusing on the customer retention/churn domain

DimensionReasoningScore

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-case guidance). The 'Triggers on' section just repeats the skill name.

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 users would say like 'customer churn', 'retention analysis', 'why are customers leaving', 'attrition rate'.

1 / 3

Distinctiveness Conflict Risk

The description is extremely generic - 'Data Analytics skill category' could apply to dozens of analytics skills. Nothing distinguishes this from other data analysis tools or clarifies its specific niche in churn/retention analysis.

1 / 3

Total

4

/

12

Passed

Implementation

0%

This skill is essentially an empty placeholder that describes what a churn analysis skill should do without providing any actual content. It contains no SQL queries, no analysis methodology, no visualization guidance, and no concrete examples. The entire content could be replaced with actual churn analysis instructions.

Suggestions

Add concrete SQL queries for calculating churn metrics (e.g., monthly churn rate, cohort retention)

Include specific steps for churn analysis workflow: data extraction, metric calculation, visualization, interpretation

Provide executable code examples for common churn visualizations (retention curves, cohort heatmaps)

Remove all generic boilerplate text and replace with actionable, domain-specific guidance for churn analysis

DimensionReasoningScore

Conciseness

The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need.

1 / 3

Actionability

The skill contains zero concrete guidance, no code examples, no SQL queries, no specific steps for churn analysis. It only describes what it claims to do without actually providing any executable instructions.

1 / 3

Workflow Clarity

There is no workflow defined at all. The skill mentions 'step-by-step guidance' but provides none. No sequence of operations, no validation steps, nothing actionable.

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 visualization guides that would be expected for a data analytics skill.

1 / 3

Total

4

/

12

Passed

Validation

69%

Validation11 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

description_trigger_hint

Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')

Warning

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata' field is not a dictionary

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

body_steps

No step-by-step structure detected (no ordered list); consider adding a simple workflow

Warning

Total

11

/

16

Passed

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.