growth-analytics
Growth Analyst Agent. 성장 지표 분석, 코호트 분석, 퍼널 분석을 담당합니다.
Install with Tessl CLI
npx tessl i github:shaul1991/shaul-agents-plugin --skill growth-analytics37
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%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 identifies a clear domain (growth analytics) with three specific analysis types, but suffers from missing trigger guidance and limited natural language keywords. The Korean-only format limits discoverability for English queries, and the lack of explicit 'when to use' criteria significantly impacts its utility for skill selection.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios like 'when analyzing user retention, conversion funnels, cohort behavior, or growth metrics'
Include both Korean and English trigger terms to improve discoverability (e.g., 'retention analysis', 'conversion rate', 'user cohorts', 'AARRR metrics')
Expand concrete actions beyond '담당합니다' to specify what the skill actually does (e.g., 'calculates retention rates', 'visualizes funnel drop-off', 'segments users by acquisition date')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (growth analysis) and lists three specific types of analysis (성장 지표 분석/growth metrics, 코호트 분석/cohort analysis, 퍼널 분석/funnel analysis), but doesn't describe concrete actions beyond 'handles/is responsible for'. | 2 / 3 |
Completeness | Describes what it does (growth/cohort/funnel analysis) but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant Korean terms for growth metrics, cohort analysis, and funnel analysis, but lacks common variations, English equivalents, or natural phrases users might say like 'retention', 'conversion', 'user segments', or 'AARRR'. | 2 / 3 |
Distinctiveness Conflict Risk | The specific mention of cohort and funnel analysis provides some distinction, but 'growth metrics analysis' is broad enough to potentially overlap with general analytics or data analysis skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a role description rather than actionable guidance. It lists responsibilities (funnel analysis, cohort analysis, metrics tracking) without providing any concrete methods, code examples, formulas, or step-by-step processes. Claude would not know how to actually perform these analyses based on this content alone.
Suggestions
Add concrete code examples for each analysis type (e.g., SQL queries for cohort analysis, Python code for funnel calculations)
Define a clear workflow with steps: data extraction → analysis → validation → report generation, including specific validation checkpoints
Include example output formats or templates showing what a completed analysis report should contain
Link to or create reference documents for specific methodologies (e.g., COHORT_ANALYSIS.md, FUNNEL_ANALYSIS.md) with detailed implementation guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is brief but lacks substance - it's concise by omission rather than by efficient information density. The bullet points are high-level categories without actionable detail. | 2 / 3 |
Actionability | No concrete code, commands, formulas, or specific methodologies provided. The skill describes what to do ('코호트 분석', '퍼널 분석') but not how to do it - purely abstract descriptions without executable guidance. | 1 / 3 |
Workflow Clarity | No workflow or process steps defined. Missing any sequence for how to perform analyses, what tools to use, what validation to apply, or how to structure the output reports. | 1 / 3 |
Progressive Disclosure | References an output location but provides no links to detailed methodology documents, templates, or examples. No structure for discovering how to actually perform the analyses mentioned. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 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.