growth
Use this skill when the user needs to design a product-led growth strategy, build viral loops, improve activation metrics, or reduce churn. Covers PLG funnels, activation metrics, viral mechanics, retention strategies, and growth systems.
Best use case
growth is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use this skill when the user needs to design a product-led growth strategy, build viral loops, improve activation metrics, or reduce churn. Covers PLG funnels, activation metrics, viral mechanics, retention strategies, and growth systems.
Teams using growth should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/growth/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How growth Compares
| Feature / Agent | growth | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use this skill when the user needs to design a product-led growth strategy, build viral loops, improve activation metrics, or reduce churn. Covers PLG funnels, activation metrics, viral mechanics, retention strategies, and growth systems.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
SKILL.md Source
# Growth & Product-Led Growth
In PLG, the product is your best salesperson. This skill helps you design growth into your product — with concrete tactics and prompts you can hand to Claude Code.
## Core Principles
- Growth is a system, not a hack. Build loops, not one-time campaigns.
- Activation is the most important metric. A user who never experiences value is already lost.
- Virality is engineered, not accidental. Design sharing into the product.
- Retention is the foundation. Growing on top of a leaky bucket is a losing game.
- For a solo founder: pick ONE growth lever, make it work, then add the next.
---
## The PLG Funnel
Acquisition → Activation → Retention → Revenue → Referral
**The most common mistake:** Founders focus on Acquisition first. Focus on Activation and Retention first — there's no point driving signups into a leaky bucket.
---
## Activation (Start Here)
### Define Your Aha Moment
The specific action where users first experience core value:
| Product Type | Example Aha Moment |
|-------------|-------------------|
| Project management | Created first project + added a task |
| Email tool | Sent first campaign |
| Analytics | Saw first dashboard with real data |
| Design tool | Exported first design |
| Scheduling | Booked first meeting through the tool |
**Your aha moment:** [Action that makes users say "I get it, this is useful"]
### Drive Users to Aha Fast
Every screen between signup and the aha moment is a drop-off risk.
**Tell AI:**
```
Design the onboarding flow to get users to [your aha moment] in under 3 minutes:
1. After signup, skip the "check your email" screen — go directly to the product
2. Show a setup wizard (3-5 steps max) that collects only what's needed to deliver value
3. Pre-populate with sample data or templates so the product looks useful immediately
4. Add a progress checklist: "Complete your setup: ☑ Create [X] ☐ [Next step] ☐ [Final step]"
5. Show an empty state with a clear CTA on every empty page ("Create your first [X]")
```
### Activation Emails
Pair your in-product onboarding with a 5-email welcome sequence that nudges unactivated users. See the **email** skill for the full welcome sequence template with ready-to-paste copy for each email.
---
## Acquisition Strategies
Pick ONE that matches your product. Don't spread across all of them.
| Strategy | Best For | Effort | Time to Results |
|----------|----------|--------|-----------------|
| Free tool / calculator | Products that solve measurable problems | Medium | 1-3 months |
| Template gallery | Products with customizable outputs | Medium | 2-4 months |
| Content-as-product | Products in information-heavy spaces | High | 3-6 months |
| Community-driven | Products with passionate niche users | High | 3-6 months |
| Integrations | Products that connect to other tools | Medium | 1-2 months per integration |
| Freemium | Products where free use drives word-of-mouth | Low | Immediate (but slow growth) |
**Tell AI:**
```
Build a [free tool / template gallery / calculator] that:
- Solves a specific problem our ICP has (related to our product)
- Requires no signup to use
- Shows a teaser of our full product's value
- Includes a CTA: "Want more? [Product name] does this automatically."
- Is SEO-optimized so it attracts organic traffic
```
---
## Viral Loop Design
A viral loop has 4 parts: User gets value → Has reason to share → New user sees value → Converts → Loop repeats.
### Viral Mechanics for SaaS
| Mechanic | How It Works | Example |
|----------|-------------|---------|
| Collaboration invites | Product requires multiple users | "Invite your team to edit this" |
| Shared outputs | User creates something shareable | Reports, links, dashboards with "Made with [Product]" |
| Referral rewards | Incentivized invitations | "Give $20, get $20" |
| Public pages | User content is SEO-indexable | Public profiles, portfolios, pages |
| Embeds | Widget on user's site links back | Badges, chat widgets, forms |
**Tell AI:**
```
Add a sharing/invite mechanic to our product:
- After a user completes [key action], prompt: "Share this with your team" or "Invite a collaborator"
- Make shared links show a preview of the output (not just a signup page)
- Add "Made with [Product]" branding on shared/public outputs with a link to our homepage
- Track invite sends, invite accepts, and invite-to-signup conversion
```
---
## Retention Mechanics
### Build Habit Loops
| Component | What It Is | Example |
|-----------|-----------|---------|
| Trigger | What brings them back | Email digest, notification, calendar event |
| Action | What they do in the product | Check dashboard, respond to comment, update status |
| Reward | Value they get | New insight, progress indicator, completed task |
| Investment | What makes leaving harder | More data, more connections, more history |
**Tell AI:**
```
Build retention mechanics into the product:
1. Weekly email digest: summarize what happened this week + one insight or action item
2. Activity notifications: "[Name] commented on your [item]" — not time-based ("It's been 3 days")
3. Progress indicators: Show users their cumulative value ("You've saved 14 hours this month")
4. Data investment: The more they use it, the more valuable their data becomes (history, reports, trends)
```
### Feature Drips
Don't show everything on day 1. Reveal features as users are ready:
**Tell AI:**
```
Implement progressive feature disclosure:
- Week 1: Show only core features (the ones needed for the aha moment)
- Week 2: Surface advanced feature with a tooltip: "Now that you've [done X], try [advanced feature]"
- Week 3+: Unlock remaining features with brief explanations
- Gate premium features with a gentle upgrade prompt at the moment of need
```
---
## Metrics to Track
Set these up in your analytics tool (see analytics-instrumentation skill):
| Stage | Key Metric | How to Calculate |
|-------|-----------|-----------------|
| Acquisition | Signup rate | Visitors → Signups |
| Activation | Activation rate | Signups → Completed aha moment |
| Activation | Time to aha | Average hours/days from signup to key action |
| Retention | D1/D7/D30 | % of users returning on day 1, 7, 30 |
| Revenue | Free-to-paid | Free users → Paying users |
| Referral | Viral coefficient | Invites sent × invite conversion rate |
**Tell AI:**
```
Set up growth tracking:
- Track signup events with source attribution (organic, paid, referral, direct)
- Track [aha moment action] completion with timestamp
- Calculate time-to-activate for each user
- Build a daily dashboard showing: signups, activations, D7 retention, free-to-paid conversion
- Alert me if activation rate drops below [X]% or D7 retention drops below [Y]%
```
---
## Growth Experiments
When you want to improve a metric, frame it as a hypothesis:
1. **Hypothesis:** "If we [change], then [metric] will [improve] because [reason]."
2. **Metric:** What specifically will you measure?
3. **Duration:** Run for 1-2 weeks minimum, or until 100+ users have been through the flow.
4. **Decide:** Did the metric improve? Ship it or revert.
5. **Document:** Write down what you learned, even (especially) from failures.
For A/B test setup, implementation, and reading results, see the **conversion** skill's A/B testing section.
---
## Common Mistakes
| Mistake | Fix |
|---------|-----|
| Focusing on acquisition before activation | Fix activation first — no point driving users into a broken onboarding |
| Building viral features nobody uses | Viral loops must be part of the core workflow, not a sidebar feature |
| Measuring vanity metrics (signups) | Track activation rate and retention, not just signups |
| Trying all channels at once | Pick ONE, make it work, then add another |
| Complex A/B testing infrastructure | Use simple feature flags. You don't need Optimizely at 100 users |
---
## Related Skills
- **conversion** — Funnel optimization, A/B testing, and signup flow CRO
- **email** — Welcome sequences and lifecycle emails that drive activation
- **analytics** — Set up the tracking that powers growth metrics
- **retention** — Deep-dive on churn prevention and win-back
- **pricing** — Pricing tiers and expansion revenue mechanicsRelated Skills
validate
Use this skill when the user needs to validate a business idea, test demand before building, run a smoke test, create an MVP experiment, or decide whether an idea is worth pursuing. Covers demand validation, smoke tests, fake-door tests, landing page experiments, and go/no-go decision frameworks for bootstrapped founders.
ux-design
Use this skill when flows feel clunky, users are confused, navigation needs planning, onboarding needs design, or accessibility needs implementation. Covers information architecture, user flows, interaction patterns, progressive disclosure, and error handling UX.
ui-patterns
Use this skill when the user needs to build a dashboard, settings page, data table, or any page layout. Also use when choosing component libraries, implementing responsive design, dark mode, or handling UI states (loading, empty, error). Covers component selection, page composition, and responsive implementation.
translate
Use this skill when the user is a domain expert (lawyer, doctor, contractor, accountant, etc.) who wants to turn their professional knowledge into a software product. Also use when the user says 'I have an idea for my industry,' 'I know this problem exists,' 'I want to build something for [profession],' or is struggling to describe what they want the software to do. Helps identify which professional pain is worth building for, then translates it into requirements AI tools can execute.
test
Use this skill when the user needs to test features before deployment, create test scenarios, find edge cases, or verify bug fixes. Covers manual testing workflows, cross-browser testing, edge case identification, and testing checklists for non-technical founders.
technical-seo
Use this skill to implement technical SEO optimizations in code — meta tags, schema markup, Core Web Vitals, crawlability, robots.txt, sitemaps, and GEO (Generative Engine Optimization) for AI search engines. This is the implementation skill — for strategy see seo, for content writing see seo-content, for auditing see seo-audit.
support
Use this skill when the user needs to create help docs, build a knowledge base, set up self-serve support, or reduce support tickets. Covers documentation strategy, help center structure, support tone, and scaling support without hiring.
social-media
Use this skill when the user needs to grow a social media presence, create content for Twitter/X, LinkedIn, or other platforms, build a founder brand, or use social media as a distribution channel. Covers platform strategy, content frameworks, posting cadence, and audience building for bootstrapped SaaS founders.
seo
Use this skill when the user needs to plan SEO content, do keyword research, build a content calendar, map search intent to page types, or create an internal linking strategy. Also use when the user says 'how do I rank higher,' 'what should I write about for SEO,' 'SEO plan,' 'what keywords should I target,' or 'how to get organic traffic.' This is the strategy and planning skill — for writing content see seo-content, for technical implementation see technical-seo, for auditing see seo-audit.
seo-content
Use this skill when the user needs to write SEO content — blog posts, landing pages, feature pages, comparison pages, how-to guides, or any content meant to rank in search and get cited by AI. Covers content briefs, humanized writing that avoids AI detection, SERP feature targeting, entity optimization, content refresh, and quality self-checks. This is the writing skill — for strategy see seo, for technical implementation see technical-seo, for auditing see seo-audit.
seo-audit
Audit a codebase for SEO and AI-answer visibility, then produce a prioritized fix-it plan. Use this skill whenever a user says things like "audit my SEO", "check my site for search visibility", "how do I rank better", "optimize for Google", "optimize for AI answers", "SEO review", "GEO audit", "run the SEO agent", or anything about improving organic traffic or search rankings. Also trigger when someone mentions wanting visibility in AI-generated answers (ChatGPT, Gemini, Perplexity, Claude). Works on any web project — static sites, Next.js, Astro, Hugo, WordPress themes, or anything that outputs HTML.
secure
Use this skill when the user needs to secure their SaaS app, implement authentication, protect user data, secure APIs, or check for vulnerabilities. Also use when the user says 'is my app secure,' 'security check,' 'I'm worried about hackers,' 'how do I protect user data,' or 'security before launch.' Covers OWASP Top 10, auth best practices, data protection, and security checklists for apps built with AI tools.