community-marketing
Skill190 starsChanged 6 months agoMITView on GitHub
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.\"
We split this skill into the rules it gives an agent
5 rules. 4 are common, 0 are distinctive, and 1 is very specific to this project.
4
Common
Most of the 21 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older …
- Common: line 40
Always define: What identity does this community reinforce for its members?
- Common: line 44
Every community touchpoint should answer: *What does the member get from this?*
- Common: line 143
Always be specific. Generic advice ("be consistent," "provide value") is not useful.
- Common: line 153
Do you have existing users or customers to seed from?
“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
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
Other versions38 projects use a version of this.
Word for word · 14
- Nexus-JPF/note-companion★ 870100% same
- open-fox/agents★ 55100% same
- SZcalligrapher/slash-skills-subscription★ 32100% same
- TommyBez/skillsboard★ 8100% same
- agrivisionai/claude-skills★ 1100% same
- mahiunfiltered/claude-code-skills★ 1100% same
- ngothanhtung/claude-code-skills★ 1100% same
- productionx-in/Core-Skills★ 1100% same
- xeroc/skills★ 1100% same
- AayanHetam/chess-coach-ai★ 0100% same
4 more not listed
Edited · 21
- coreyhaines31/marketingskills★ 58k90% same
- ukunal91app/Marketing-Skills-by-Corey-Haines★ 2699% same
- anis-dr/skills★ 390% same
- mia-ppp/PMM-Skills★ 286% same
- Shri-Phnx/claude-skills★ 226% same
- ai-vita/skills★ 198% same
- jpoindexter/theft-kit★ 198% same
- patinaproject/skills★ 190% same
- SrajanYadav/claude-skills★ 148% same
- blueskynnn-cloud/claude-skills★ 098% same
11 more not listed
Wrote their own version · 3
- scayver/marketing-skills★ 8same name
- david-corroy/skills-marketing-fr★ 1same name
- Synthenova/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use marketing-council.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
coreyhaines31Skillmarketing-council
When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more). Also use when the user mentions 'marketing council,' 'board of advisors,' 'advisory board,' 'what would Seth Godin say,' 'what would Ogilvy think,' 'channel Hormozi,' 'get multiple perspectives,' 'debate this,' 'have the council review,' 'marketing mentors,' or asks how a famous marketer would approach their problem. The council gives each advisor's take through their documented frameworks, surfaces where they disagree, and synthesizes a recommendation. For executing the winning direction, hand off to positioning, offers, copywriting, ads, or the relevant skill.
Also in 17 projects that use this
In this repository46 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ab-testingSkill
- ad-creativeSkill
- adsSkill
- ai-seoSkill
- analyticsSkill
- asoSkill
- churn-preventionSkill
- cold-emailSkill
- co-marketingSkill
- competitor-profilingSkill
- competitorsSkill
- content-strategySkill
- copy-editingSkill
- copywritingSkill
- croSkill
- customer-researchSkill
- directory-submissionsSkill
- emailsSkill
- free-toolsSkill
- imageSkill
- launchSkill
- lead-magnetsSkill
- marketing-ideasSkill
- marketing-planSkill
- marketing-psychologySkill
- offersSkill
- onboardingSkill
- paywallsSkill
- popupsSkill
- pricingSkill
- product-marketingSkill
- programmatic-seoSkill
- prospectingSkill
- public-relationsSkill
- referralsSkill
- revopsSkill
- sales-enablementSkill
- schemaSkill
- seo-auditSkill
- signupSkill
- site-architectureSkill
- smsSkill
- socialSkill
- videoSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

