Community Marketing
Corey HainesCommunityCreated by Corey Haines
- Skill
- Guidelines
- Business and productivity
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a comprehensive approach to community-led growth, helping users design, launch, and scale online communities. It emphasizes building around shared identities rather than just products, ensuring value flows to members, and utilizing a community flywheel to drive engagement. The skill includes specific playbooks for launching from zero, growing existing communities, managing ambassador programs, and implementing community-led support. It also offers guidance on platform selection, health metrics, and the evolution of the community manager's role as the community scales.
What it does
- Defines community strategy based on shared member identity and value exchange.
- Provides step-by-step playbooks for launching and growing communities.
- Offers guidance on building brand ambassador and advocate programs.
- Outlines methods for community-led support and feedback loops.
- Suggests appropriate platforms based on specific community goals.
- Defines key health metrics and warning signs for community management.
When to use it
- When you need to build a community from scratch to drive product growth.
- When you want to increase brand loyalty and turn customers into evangelists.
- When you need to improve user retention or reduce support ticket volume.
- When you are looking to scale an existing community and need to shift your management role.
- When you need to establish a structured ambassador or advocate program.
Advantages
- Focuses on sustainable growth through a community flywheel.
- Provides actionable, stage-specific guidance for different community sizes.
- Helps align community goals with measurable business outcomes.
- Offers clear frameworks for platform selection and member engagement.
Usage examples
- “We are a SaaS startup with 50 users and want to build a Discord community. How do we start?”
- The agent will guide you through the 'Launching a Community from Zero' playbook, focusing on recruiting founding members, setting culture, and seeding initial conversations.
- “Our Slack community is stagnant. How can we increase engagement?”
- The agent will help you audit the member journey, suggest recurring rituals, and identify power users to revitalize the community.
- “How do I turn our most active users into brand ambassadors?”
- The agent will provide a strategy for identifying candidates, making a personal ask, offering meaningful benefits, and providing them with the right tools.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/coreyhaines31/community-marketing/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip community-marketing.zip -d .agents/skills
Documentation by Corey Haines
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.
Before 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.
Community Strategy Principles
Build 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?
Value 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?
Playbooks by Goal
Launching 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
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.
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 |
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
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.
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?
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
Files
- ATTRIBUTION.mdAdded by AutoGineer899 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md9.6 KiB
- evals/evals.json9.2 KiB
- references/community-models.md4.0 KiB
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Corey Haines
- Publisher
- Corey Haines (Community)
- Source
- coreyhaines31/marketingskills · skills/community-marketing · commit 96798cf
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Corey Haines or Corey Haines.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download community-marketing.zip