CtrlK
BlogDocsLog inGet started
Tessl Logo

cohort-analysis

Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.

63

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./pm-data-analytics/skills/cohort-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body presents a clear, well-sequenced five-step cohort analysis workflow with useful examples and good organization. Its main weaknesses are verbosity in overlapping sections and a lack of executable code or templates despite mentioning script generation.

Suggestions

Trim redundant sections: 'Key Capabilities' and 'Output Format' restate the Step 1-5 content — consolidate or cut to improve conciseness.

Add at least one concrete, copy-paste-ready Python snippet (e.g., a pandas retention-rate pivot) instead of only describing that scripts will be generated.

Add an explicit validation feedback loop in Step 1 (e.g., 'If validation fails: report issues, request corrected data, do not proceed') to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

Mostly efficient bullet-listed steps with no padding of concepts Claude already knows, but sections like 'Key Capabilities' and 'Output Format' restate the step content and could be tightened.

3 / 5

Actionability

Provides concrete guidance on data formats, metrics to compute, and chart types, but describes outputs ('Generate Python analysis scripts using pandas and numpy if requested') rather than supplying executable code, leaving key implementation details missing.

3 / 5

Workflow Clarity

Clear five-step sequence with explicit data validation in Step 1, but lacks explicit error-recovery feedback loops between steps; the analysis is read-only so the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

Well-organized single-file structure with clear section headers and appropriately placed external 'Further Reading' links, though no one-level-deep bundle references exist and some content could be split out.

4 / 5

Total

14

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it states concrete capabilities and provides explicit, natural-language trigger guidance covering the main use cases. It is well-distinguished from other skills and concise without fluff.

DimensionReasoningScore

Specificity

Lists several concrete actions (retention curves, feature adoption trends, segment-level insights) with minor coverage gaps, matching the 'several specific actions' anchor rather than the comprehensive 5.

4 / 5

Completeness

Explicitly answers both what (cohort analysis, retention curves, feature adoption, segment insights) and when ('Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-phrase coverage ('user retention by cohort', 'feature adoption over time', 'churn patterns', 'engagement trends') that users would naturally say, though a few synonyms/variations are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (cohort analysis and retention) with distinct, specific triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
phuryn/pm-skills
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.