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.
34
Quality
3%
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
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 description is essentially a placeholder that provides almost no useful information for skill selection. It relies entirely on the skill name without explaining capabilities, use cases, or meaningful trigger terms. The duplicate trigger term suggests this may be auto-generated boilerplate rather than a thoughtfully crafted description.
Suggestions
Add specific actions the skill performs, e.g., 'Creates retention cohort tables, segments users by signup date/week/month, calculates period-over-period retention rates, visualizes cohort matrices'
Replace duplicate trigger with natural user terms: 'retention analysis', 'user cohorts', 'customer lifetime analysis', 'churn by signup date', 'cohort retention'
Add explicit 'Use when...' clause: 'Use when analyzing user retention over time, segmenting customers by acquisition period, or tracking how behavior changes across cohort groups'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Cohort Analysis Creator') without describing any concrete actions. There are no specific capabilities listed like 'segments users by signup date', 'calculates retention rates', or 'generates cohort tables'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. The 'Triggers on' line just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The triggers listed are just the skill name repeated twice ('cohort analysis creator, cohort analysis creator'). Missing natural user terms like 'retention analysis', 'user cohorts', 'customer segments', 'churn analysis', or 'time-based grouping'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'cohort analysis' is a specific domain term that provides some distinctiveness, the lack of detail about what kind of cohort analysis (retention, behavioral, revenue) and the generic 'Data Analytics' category could cause overlap 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 a placeholder template with no actual content about cohort analysis. It contains only generic meta-descriptions of what a skill should do without any concrete guidance, code examples, SQL queries, or workflows for performing cohort analysis. The content fails on all dimensions by describing capabilities rather than providing them.
Suggestions
Add concrete SQL examples showing how to create cohort analysis queries (e.g., user retention cohorts by signup month)
Include a clear workflow: 1) Define cohort criteria, 2) Write grouping query, 3) Calculate metrics, 4) Visualize results
Provide specific output format examples showing what a cohort analysis table/matrix should look like
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual cohort analysis techniques
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about cohort analysis. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that waste tokens without adding value. | 1 / 3 |
Actionability | No concrete code, SQL queries, examples, or specific instructions are provided. The skill describes what it claims to do but never shows how to actually perform cohort analysis - no executable guidance whatsoever. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill mentions 'step-by-step guidance' but provides none. There are no steps, no sequence, and no validation checkpoints for creating cohort analyses. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, examples, or related documentation. It mentions 'Related Skills' but provides no actual links or navigation. | 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.