Marketer pack
Claude Skill
Community-Led Growth Strategist
Designs a community built on a shared member identity — where value flows to members first and growth compounds from it.
What it does
Helps design, launch, or revive a community (Discord, Slack, forum, subreddit) around who members are or aspire to be, not around the product, with one clear primary goal — retention, activation, word-of-mouth, or feedback — and value that flows to members first. Built to avoid the dead-channel trap where a "community" is just a broadcast list.
When to use
- ✓Building or growing a user community as a growth motion
- ✓Turning customers into advocates and word-of-mouth
- ✓An existing community has gone quiet and needs a revival plan
When not to use
- ✗You need a fast acquisition channel — community is slow-compounding
- ✗No one can show up and facilitate consistently
Install
Download the .zip, then unzip into your Claude skills folder.
mkdir -p ~/.claude/skills
unzip ~/Downloads/community-led-growth-strategist.zip -d ~/.claude/skills/
# Restart Claude Code session.
# Skill is now available — Claude will use it when relevant.SKILL.md
SKILL.md
---
name: community-led-growth-strategist
description: Use when designing, launching, or growing an online community for product growth. Triggers on "build a community", "community strategy", "community-led growth", "Discord/Slack community", "ambassador program", "revive our community".
---
# Community-Led Growth Strategist
The strongest communities are built around an identity — who members are or want to be — not around your product. People join because of the product and stay because of the people. Define the identity first: what does belonging here say about a member?
## Value flows to members first
A community is not a broadcast channel. If the dominant activity is the company posting announcements, it's a newsletter with extra steps. Members must get value from each other — answers, status, connections, early access — before the business gets anything back.
## Pick one primary goal
Retention, activation, word-of-mouth, support deflection, or product feedback — choose one to design around. A community optimizing for everything optimizes for nothing.
## The cold start (0 → 100)
- Seed with real people you invite individually, not a public launch announcement
- Create reasons to return: rituals, recurring threads, member spotlights — not a one-time welcome
- Be present and facilitate; an unfacilitated community dies in week three
- Make early members feel like founders, because they are
## Measure what matters
Returning members and member-to-member interactions beat raw signup count. A 5,000-member dead channel is worth less than 80 people who show up weekly.
## Anti-patterns
- Building around the product instead of a member identity
- Broadcasting instead of facilitating
- Chasing member count as a vanity metric
- Launching publicly before there's any activity to walk into
- No one owning consistent presence
Example prompts
Once installed, try these prompts in Claude:
- Design a community strategy for our open-source dev tool — what identity, what platform, and a plan for the first 100 members.
- Our Slack community is a ghost town. Diagnose why and give me a revival plan.