home / skills / eddiebe147 / claude-settings / growth-hacker
/skills/growth-hacker
This skill helps design and execute lean growth experiments using data-driven tactics to improve operations and outcomes.
npx playbooks add skill eddiebe147/claude-settings --skill growth-hackerReview the files below or copy the command above to add this skill to your agents.
---
name: Growth Hacker
slug: growth-hacker
description: Design and execute growth experiments using lean, data-driven tactics
category: business
complexity: simple
version: "1.0.0"
author: "ID8Labs"
triggers:
- "growth hacking"
- "growth experiments"
- "growth strategy"
- "viral growth"
- "growth tactics"
tags:
- growth
- hacking
- experiments
- acquisition
- viral
---
# Growth Hacker
Design and execute growth experiments using lean, data-driven tactics
## When to Use This Skill
Use this skill when you need to:
- Improve business operations and strategy
- Make data-driven business decisions
- Optimize processes and outcomes
**Not recommended for:**
- Tasks requiring creative design work
- technical coding
## Quick Reference
| Action | Command/Trigger |
|--------|-----------------|
| Create growth hacker | `growth hacking` |
| Review and optimize | `review growth hacker` |
| Get best practices | `growth hacker best practices` |
## Core Workflows
### Workflow 1: Initial Growth Hacker Creation
**Goal:** Create a high-quality growth hacker from scratch
**Steps:**
1. **Discovery** - Understand requirements and objectives
2. **Planning** - Develop strategy and approach
3. **Execution** - Implement the plan
4. **Review** - Evaluate results and iterate
5. **Optimization** - Refine based on feedback
### Workflow 2: Advanced Growth Hacker Optimization
**Goal:** Refine and optimize existing growth hacker for better results
**Steps:**
1. **Research** - Gather relevant information
2. **Analysis** - Evaluate options and approaches
3. **Decision** - Choose the best path forward
4. **Implementation** - Execute with precision
5. **Measurement** - Track success metrics
## Best Practices
1. **Start with Clear Objectives**
Define what success looks like before beginning work.
2. **Follow Industry Standards**
Leverage proven frameworks and best practices in business.
3. **Iterate Based on Feedback**
Continuously improve based on results and user input.
4. **Document Your Process**
Keep track of decisions and outcomes for future reference.
5. **Focus on Quality**
Prioritize excellence over speed, especially in early iterations.
## Checklist
Before considering your work complete:
- [ ] Objectives clearly defined and understood
- [ ] Research and discovery phase completed
- [ ] Strategy or plan documented
- [ ] Implementation matches requirements
- [ ] Quality standards met
- [ ] Stakeholders informed and aligned
- [ ] Results measured against goals
- [ ] Documentation updated
- [ ] Feedback collected
- [ ] Next steps identified
## Common Mistakes
| Mistake | Why It's Bad | Better Approach |
|---------|--------------|-----------------|
| Skipping research | Leads to misaligned solutions | Invest time in understanding context |
| Ignoring best practices | Reinventing the wheel | Study successful examples first |
| No clear metrics | Can't measure success | Define KPIs upfront |
## Integration Points
- **Tools**: Integration with common business platforms and tools
- **Workflows**: Fits into existing business operations workflows
- **Team**: Collaborates with leadership and operations stakeholders
## Success Metrics
Track these metrics to measure effectiveness:
- Quality of output
- Time to completion
- Stakeholder satisfaction
- Impact on business goals
- Reusability of approach
---
*This skill is part of the ID8Labs Skills Marketplace. Last updated: 2026-01-07*
This skill designs and executes lean, data-driven growth experiments to accelerate user acquisition, activation, and retention. It combines clear objectives, rapid testing, and measurable outcomes to improve business operations and strategy. Use it to turn hypotheses into prioritized experiments and repeatable growth motions.
I start by discovering your goals and constraints, then craft a focused plan that maps hypotheses to measurable experiments. Execution follows a sprint-like cadence: run tests, collect data, and analyze results. Each cycle ends with a review and optimization step so successful tactics scale and failures inform the next iteration.
What problems should I not use this skill for?
Avoid using this for creative design work or deep technical coding tasks; it focuses on strategy, experiments, and operational optimization.
How long before I see measurable results?
Small experiments can yield early signals within days to a few weeks; meaningful business impact typically requires several iterative cycles tracked against defined KPIs.