cohort-analysis-creator
Cohort Analysis Creator - Auto-activating skill for Data Analytics. Triggers on: cohort analysis creator, cohort analysis creator Part of the Data Analytics skill category.
31
0%
Does it follow best practices?
Impact
87%
1.00xAverage 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/cohort-analysis-creator/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 that provides no meaningful information beyond the skill's name and category. It lacks concrete actions, natural trigger terms, explicit usage guidance, and any detail that would help Claude distinguish it from other data analytics skills. It reads as auto-generated boilerplate rather than a useful skill description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Segments users into cohorts by signup date, calculates retention rates over time, and generates cohort retention heatmaps or tables.'
Add a 'Use when...' clause with natural trigger terms like 'cohort analysis', 'retention analysis', 'user retention', 'churn by cohort', 'customer lifecycle', 'signup cohort', or 'retention heatmap'.
Remove the redundant duplicate trigger term and replace with varied, natural phrases users would actually say when requesting this type of analysis.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Cohort Analysis Creator') and its category ('Data Analytics') but does not describe any concrete actions like creating retention tables, segmenting users by signup date, calculating churn rates, etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just a redundant repetition of the skill name rather than explicit trigger guidance. There is no 'Use when...' clause. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the skill name repeated twice ('cohort analysis creator'). It lacks natural user phrases like 'retention analysis', 'user cohorts', 'churn', 'customer segments', or 'cohort retention table'. | 1 / 3 |
Distinctiveness Conflict Risk | Being labeled generically under 'Data Analytics' with no specific capabilities described means it could easily conflict with any other analytics-related skill. The only distinguishing element is the phrase 'cohort analysis' in the title. | 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 consists entirely of boilerplate meta-descriptions that repeat the skill name without providing any actual instructions, code, examples, or workflows for performing cohort analysis. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable SQL examples showing how to build a cohort analysis (e.g., user retention cohorts by signup month with actual SQL queries).
Define a clear multi-step workflow: identify cohort dimension → write grouping query → calculate metrics → visualize results, with validation at each step.
Include at least one complete input/output example showing sample data and the expected cohort table or visualization output.
Remove all boilerplate sections (When to Use, Example Triggers, Capabilities) that describe the skill abstractly and replace with actionable technical content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'cohort analysis creator' excessively, and provides zero actual technical content or instructions. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no SQL queries, no examples of cohort analysis, no commands, no data structures. Every section is vague and abstract. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps. There are no sequences, validation checkpoints, or processes described. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative page with no references to detailed materials, no examples, and no structured navigation to deeper content. The sections present are all meta-descriptions rather than usable content. | 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
c8a915c
- 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.