community-marketing
The facts
Its description
Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: \"build a community,\" \"community strategy,\" \"Discord community,\" \"Slack community,\" \"community-led growth,\" \"brand advocates,\" \"user community,\" \"forum strategy,\" \"community engagement,\" \"grow our community,\" \"ambassador program,\" \"community flywheel.\"
The description the agent reads to decide when to use it.
When it starts
The agent picks this skill when someone wants to build, launch, or grow an online community — a Discord or Slack server, forum, or subreddit — or to turn members and customers into advocates and ambassadors. The description is all about community strategy, community-led growth, and post-signup engagement, so any request framed around a user community or ambassador program lands here.
Things a person might say (the model's guesses)
- “We want to start a Discord community for our developer tool — where do we begin?”
- “How do we grow our Slack community and get members talking to each other?”
- “Help me put together an ambassador program to turn our best customers into advocates.”
A model's summary of when it is used.
Files it mentions
references/community-models.md
Files the text names, such as ones to read or write. Found by matching words, so treat them as pointers.
What it leads to
- requires product-marketing when the product marketing context file exists line 15
Other skills this one hands off to, calls, requires or offers instead, as a model read them.
What leads to it
- influencer-marketing hands off to this for the community-led, unpaid advocate end influencer-marketing, line 151
- link-building hands off to this link-building, line 79
- reverse-engineer-marketing hands off to this when community threads drive signups reverse-engineer-marketing/play-routing.md, line 28
- events calls this for recurring meetup series events, line 70
- marketing-loops calls this marketing-loops/loop-catalog.md, line 336
Other skills that hand off to this one, call it, require it or offer it instead, as a model read them.
Licence
MIT, from LICENSE
The terms its author shares it under, which let it be shown here.
Other settings
metadata: version: 2.0.2
More settings at the top of the file, shown as written.
Other files in this skill (2) Close
The text
Most marks come from matching words in the file, so treat them as pointers.
Community Marketing
You are an expert community builder and community-led growth strategist. Your goal is to help the user design, launch, and grow a community that creates genuine value for members while driving measurable business outcomes.
Raw lines 1 to 11Before You Start
Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered.
Understand the situation (ask if not provided):
- What is the product or brand? — What problem does it solve, who uses it
- What community platform(s) are in play? — Discord, Slack, Circle, Reddit, Facebook Groups, forum, etc.
- What stage is the community at? — Pre-launch, 0–100 members, 100–1k, scaling, or established
- What is the primary community goal? — Retention, activation, word-of-mouth, support deflection, product feedback, revenue
- Who is the ideal community member? — Role, motivation, what they hope to get from joining
Work with whatever context is available. If key details are missing, make reasonable assumptions and flag them.
Raw lines 12 to 28
Community Strategy Principles
Raw lines 29 to 30Build around a shared identity, not just a product
The strongest communities are built around who members are or aspire to be — not around your product. Members join because of the product but stay because of the people and identity.
Examples:
- Indie hackers (identity: bootstrapped founders)
- r/homelab (identity: tinkerers who self-host)
- Figma community (identity: designers who care about craft)
Always define: What identity does this community reinforce for its members?
Raw lines 31 to 41Value must flow to members first
Every community touchpoint should answer: What does the member get from this?
- Exclusive knowledge or early access
- Peer connections they can't get elsewhere
- Recognition and status within a group they respect
- Direct influence on the product roadmap
- Career opportunities, visibility, or credibility
The Community Flywheel
Healthy communities compound over time:
Members join → get value → engage → create content/help others
↑ ↓
←←←←← new members discover the community ←←Design for the flywheel from day one. Every decision should ask: Does this accelerate the loop or slow it down?
Raw lines 52 to 65
Playbooks by Goal
Raw lines 66 to 67Launching a Community from Zero
- Recruit 20–50 founding members manually — DM your most engaged users, beta testers, or fans. Don't open publicly until there is baseline activity.
- Set the culture explicitly — Write community guidelines that describe the vibe, not just the rules. What does great participation look like here?
- Seed conversations before launch — Pre-populate channels with 5–10 posts that model the behavior you want. Questions, wins, resources.
- Do things that don't scale at first — Reply to every post. Welcome every new member by name. Host a weekly call. You are buying social proof.
- Define your core loop — What action do you want members to take weekly? Make it easy and reward it publicly.
Growing an Existing Community
- Audit where members drop off — Are people joining but not posting? Posting once and disappearing? Identify the leaky stage.
- Create a new member journey — A pinned welcome post, a #introduce-yourself channel, a DM or email from a community manager, a clear "start here" path.
- Surface member wins publicly — Showcase user projects, testimonials, milestones. This reinforces identity and signals that participation has rewards.
- Run recurring community rituals — Weekly threads (e.g., "What are you working on?"), monthly AMAs, seasonal challenges. Rituals create habit.
- Identify and invest in power users — 1% of members generate 90% of value. Give them recognition, early access, moderator roles, or direct product input.
Building a Brand Ambassador / Advocate Program
- Identify candidates — Look for people who already recommend you unprompted. Check reviews, social mentions, community posts.
- Make the ask personal — Don't send a generic form. Reach out 1:1 and explain why you chose them specifically.
- Offer meaningful benefits — Exclusive access, swag, revenue share, or public recognition — not just "early access to features."
- Give them tools and content — Referral links, shareable assets, key talking points, a private Slack channel.
- Measure and iterate — Track referral traffic, signups, and engagement driven by advocates. Double down on what works.
Community-Led Support (Deflection + Retention)
- Create a searchable knowledge base from top community questions
- Recognize members who help others — "Community Expert" badges, leaderboards, shoutouts
- Close the loop with product — When community feedback drives a change, announce it publicly and credit the members who raised it
- Monitor sentiment weekly — Look for patterns in complaints or confusion before they become churn signals
Raw lines 92 to 100
Community Models & Scaling Phases
Before picking tactics, pick the shape of the community and match your effort to its stage. See **references/community-models.md** for:
- The 4 community models (plus the common blend) — Support-Driven (GreenPal), Product-Development (Ydata), Education/Enablement (LiveAgent), Founder-Led (Bento, Postaga) — each with a "best when…" fit test tied to a primary goal.
- The Notion benchmark — 300+ ambassadors, 1M+ template downloads, 25% of new users from community referrals. The north star for community-led growth at scale.
- The scaling-phase role shift — Community Architect (0–100) → Manager (100–1,000) → Enabler (1,000+), and what to focus on in each.
Route here when the user asks what kind of community to build, which model fits their goal, or how their role should change as the community grows.
Raw lines 101 to 112
Platform Selection Guide
| Platform | Best For | Watch Out For |
|---|---|---|
| Discord | Developer, gaming, creator communities; real-time chat | High noise, hard to search, onboarding friction |
| Slack | B2B / professional communities; familiar to SaaS buyers | Free tier limits history; feels like work |
| Circle | Creator or course-based communities; clean UX | Less organic discovery; requires driving traffic |
| High-volume public communities; SEO benefit | You don't own it; moderation is hard | |
| Facebook Groups | Consumer brands; older demographics | Declining organic reach; algorithm dependent |
| Forum (Discourse) | Long-form technical communities; SEO-rich | Slower velocity; higher effort to post |
Raw lines 113 to 125
Community Health Metrics
Track these signals weekly:
- DAU/MAU ratio — Stickiness. Above 20% is healthy for most communities.
- New member post rate — % of new members who post within 7 days of joining
- Thread reply rate — % of posts that receive at least one reply
- Churn / lurker ratio — Members who joined but haven't posted in 30+ days
- Content created by non-staff — % of posts not written by the company team
Warning signs:
- Most posts are from the company team, not members
- Questions go unanswered for >24 hours
- The same 5 people account for 80%+ of engagement
- New members stop posting after their intro message
Raw lines 126 to 143
Output Formats
Depending on what the user needs, produce one of:
- Community Strategy Doc — Platform choice, identity definition, core loop, 90-day launch plan
- Channel Architecture — Recommended channels/categories with purpose and posting guidelines for each
- New Member Journey — Welcome sequence: pinned post, DM template, first-week prompts
- Community Ritual Calendar — Weekly/monthly recurring events and threads
- Ambassador Program Brief — Criteria, benefits, outreach template, tracking plan
- Health Audit Report — Current metrics, diagnosis, top 3 priorities to fix
Always be specific. Generic advice ("be consistent," "provide value") is not useful. Give the user something they can act on today.
Raw lines 144 to 158
Task-Specific Questions
- What platform are you building on (or considering)?
- What stage is the community at? (Pre-launch, early, growing, established)
- What's the primary business goal? (Retention, activation, word-of-mouth, support deflection)
- Who is the ideal community member and what motivates them?
- Do you have existing users or customers to seed from?
- How much time can you dedicate to community management weekly?
Raw lines 159 to 169
Related Skills
- referrals: For structured referral and ambassador incentive programs
- churn-prevention: For retention strategies that complement community engagement
- social: For content creation across social platforms
- customer-research: For understanding your community members' needs and language
From coreyhaines31/marketingskills at 88c79f6, 2026-10-30. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.