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 distinguishing details that would help Claude select it appropriately from a pool of skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates cohort retention tables, segments users by signup date or acquisition channel, calculates retention and churn rates over time periods, and generates cohort visualizations.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about cohort analysis, retention rates, user segmentation by time period, churn analysis, or customer lifecycle metrics.'
Remove the duplicate trigger term ('cohort analysis creator' is listed twice) and expand with varied natural language terms users might use, such as 'retention analysis', 'user cohorts', 'customer segments', 'time-based grouping'.
| 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 both 'what does this do' (no specific capabilities listed) and 'when should Claude use it' (no explicit 'Use when...' clause or meaningful trigger guidance beyond the skill name). | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the skill name repeated twice ('cohort analysis creator'). There are no natural user keywords like 'retention', 'user cohorts', 'churn', 'segmentation', or 'customer lifecycle' that a user would naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic — 'Data Analytics' could overlap with dozens of other analytics skills. Without specific capabilities or distinct triggers, there is high conflict risk with any other data analysis skill. | 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 contains only generic boilerplate descriptions of what a cohort analysis skill might do, without any actual instructions, code, SQL examples, visualization guidance, or analytical methodology. It provides zero value beyond what Claude already knows about cohort analysis.
Suggestions
Add concrete, executable SQL examples for cohort analysis (e.g., retention cohorts with date_trunc, pivot tables for cohort matrices) that Claude can adapt to user schemas.
Include a clear multi-step workflow: define cohorts → write SQL query → generate cohort matrix → visualize results, with specific code at each step.
Add example output formats (e.g., a cohort retention table structure, a visualization specification) so Claude knows what to produce.
Remove all generic boilerplate ('This skill provides automated assistance...') and replace with domain-specific guidance on cohort analysis patterns, common pitfalls, and best practices for different cohort types (acquisition, behavioral, etc.).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no domain-specific information about cohort analysis, and wastes tokens on generic placeholder text like 'Provides step-by-step guidance' without actually providing any. | 1 / 3 |
Actionability | There is zero actionable content—no SQL queries, no code examples, no concrete steps for performing cohort analysis. Every section is vague and abstract, describing what the skill supposedly does rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no bundle files to support it. There is no meaningful content to organize. | 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.