growth-hacker
Expert growth strategist specializing in rapid user acquisition through data-driven experimentation. Develops viral loops, optimizes conversion funnels, and finds scalable growth channels for exponential business growth.
32
16%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./marketing-growth-hacker/skills/SKILL.mdQuality
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.
This description reads more like a LinkedIn headline than a functional skill description. It relies heavily on marketing buzzwords ('exponential business growth', 'data-driven experimentation') without specifying concrete actions, and it completely lacks trigger guidance for when Claude should select this skill. The first-person framing issue isn't present, but the description uses an 'Expert growth strategist' persona framing that doesn't clearly communicate actionable capabilities.
Suggestions
Add an explicit 'Use when...' clause with natural trigger terms like 'growth strategy', 'user acquisition plan', 'conversion optimization', 'A/B test', 'marketing funnel'.
Replace buzzwords with concrete actions, e.g., 'Designs A/B test plans, maps conversion funnels, identifies referral loop mechanics, and prioritizes growth experiments using ICE/RICE frameworks'.
Remove the persona framing ('Expert growth strategist specializing in...') and instead use direct third-person action verbs describing what the skill does.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names some actions like 'develops viral loops', 'optimizes conversion funnels', and 'finds scalable growth channels', but these are still somewhat buzzword-heavy and not concrete enough to be truly specific actionable tasks. | 2 / 3 |
Completeness | Describes what it does (albeit vaguely), but completely lacks any 'Use when...' clause or explicit trigger guidance. Per the rubric, a missing 'Use when...' clause should cap completeness at 2, and since the 'what' is also weak and buzzword-laden, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms like 'viral loops', 'conversion funnels', 'growth channels', and 'user acquisition', but these are more industry jargon than natural user language. Missing common terms users might say like 'marketing strategy', 'A/B testing', 'landing page optimization', or 'growth hacking'. | 2 / 3 |
Distinctiveness Conflict Risk | The growth/marketing niche is somewhat specific, but terms like 'data-driven experimentation' and 'scalable growth channels' are broad enough to overlap with analytics skills, marketing skills, or general business strategy skills. | 2 / 3 |
Total | 7 / 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 reads like a job posting or role description rather than an actionable skill file. It lists capabilities, metrics, and buzzwords but provides zero concrete guidance on how to actually perform any growth hacking task. Claude already knows what these marketing concepts are; the skill adds no new, specific, or executable knowledge.
Suggestions
Replace the capability lists with concrete, step-by-step workflows for key tasks (e.g., 'How to design and run a growth experiment' with specific steps, templates, and validation checkpoints).
Add actionable templates or frameworks, such as a growth experiment brief template, a referral program design checklist, or a funnel analysis worksheet with specific metrics to calculate.
Remove all definitional content (what growth hacking is, what CAC means) and instead provide specific decision trees, code snippets for analytics, or example experiment designs that Claude can directly apply.
Structure the content with a quick-start section for the most common task, then reference separate files for detailed playbooks on specific growth tactics (viral loops, funnel optimization, etc.).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and describes concepts Claude already knows well (what growth hacking is, what A/B testing means, what CAC and LTV are). It reads like a job description or resume rather than actionable instructions. Nearly every bullet point explains a concept rather than providing new, specific guidance. | 1 / 3 |
Actionability | The entire skill is abstract descriptions and lists of capabilities with zero concrete steps, commands, code, templates, or executable guidance. Phrases like 'funnel optimization' and 'viral coefficient optimization' describe what to do but never how. There are no examples, no frameworks to apply, no templates to fill in. | 1 / 3 |
Workflow Clarity | There is no workflow, sequence, or process described anywhere. The content is entirely declarative lists of capabilities and metrics with no steps for how to actually execute a growth experiment, design a referral program, or optimize a funnel. No validation checkpoints exist. | 1 / 3 |
Progressive Disclosure | The content is a monolithic list of bullet points with no references to external files, no layered structure, and no navigation. All sections are at the same shallow depth of detail (surface-level descriptions) with no way to drill deeper into any topic. | 1 / 3 |
Total | 4 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- OpenRoster-ai/awesome-openroster
- Commit
09aef5d
- 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.