growth-hacker
Growth Hacker Agent. 성장 전략 수립, 빠른 실험 설계, 그로스 해킹을 담당합니다.
Install with Tessl CLI
npx tessl i github:shaul1991/shaul-agents-plugin --skill growth-hacker37
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
22%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 too abstract and lacks the specificity needed for Claude to reliably select it from a large skill library. It fails to provide concrete actions, natural trigger terms users would say, and explicit guidance on when to use the skill. The Korean language content is acceptable but the substance is insufficient.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about growth experiments, A/B testing, conversion optimization, user acquisition strategies, or funnel analysis'
Replace abstract terms with concrete actions such as 'Design rapid experiments, analyze growth metrics, create A/B test plans, optimize conversion funnels, develop viral loops'
Include natural keywords users would say in both Korean and English: 'growth metrics', 'conversion rate', 'user retention', 'viral coefficient', '전환율', '사용자 획득'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like '성장 전략 수립' (growth strategy development) and '그로스 해킹' (growth hacking) without listing concrete actions. No specific tasks like 'analyze funnel metrics', 'design A/B tests', or 'optimize conversion rates' are mentioned. | 1 / 3 |
Completeness | The description only partially addresses 'what' with abstract terms and completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords like '성장 전략' (growth strategy), '실험' (experiment), and '그로스 해킹' (growth hacking), but misses common variations users might say such as 'conversion', 'funnel', 'A/B test', 'user acquisition', or 'retention'. | 2 / 3 |
Distinctiveness Conflict Risk | While 'growth hacking' is somewhat specific, terms like '성장 전략' (growth strategy) could overlap with general business strategy, marketing, or product management skills. The boundaries are not clearly defined. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads as a job description rather than actionable instructions. It lists responsibilities and trigger keywords but provides zero concrete guidance on how to perform growth hacking tasks, design experiments, or calculate ICE scores. Claude would not know what to actually do when triggered.
Suggestions
Add a concrete workflow for designing growth experiments (e.g., 1. Identify metric → 2. Form hypothesis → 3. Calculate ICE score → 4. Design MVP test → 5. Define success criteria)
Include an executable example of ICE scoring with actual formula and sample calculation
Provide a template or example output for experiment documentation that should go in docs/growth/experiments/
Add specific growth hacking techniques with concrete implementation steps rather than just listing '그로스 해킹 기법 적용'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is brief and doesn't over-explain concepts, but it's essentially a role description rather than actionable skill content. The bullet points are lean but lack substance. | 2 / 3 |
Actionability | The skill provides no concrete guidance, code, commands, or examples. It only lists abstract responsibilities like '성장 전략 수립' without explaining how to actually perform these tasks or what outputs look like. | 1 / 3 |
Workflow Clarity | No workflow or process is defined. There's no sequence of steps, no validation checkpoints, and no guidance on how to actually execute growth hacking experiments or apply ICE scoring. | 1 / 3 |
Progressive Disclosure | The skill mentions output locations (docs/growth/strategy/, docs/growth/experiments/) which suggests some structure, but there are no references to detailed guides, templates, or examples that would help Claude execute the tasks. | 2 / 3 |
Total | 6 / 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.