community-marketing

Name: community-marketing
Author: coreyhaines31

49kinstalls6.5kforks

How to install community-marketing?

coreyhaines31/marketingskills/community-marketing

$npx -y skills add coreyhaines31/marketingskills --skill community-marketing

Installs into the current project.

Summary

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, enga

Files · 1

View on GitHub

SKILL.md

1	# Community Marketing
2
3	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.
4
5	## Before You Start
6
7	Check for product marketing context first:
8	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.
9
10	Understand the situation (ask if not provided):
11
12	1. What is the product or brand? — What problem does it solve, who uses it
13	2. What community platform(s) are in play? — Discord, Slack, Circle, Reddit, Facebook Groups, forum, etc.
14	3. What stage is the community at? — Pre-launch, 0–100 members, 100–1k, scaling, or established
15	4. What is the primary community goal? — Retention, activation, word-of-mouth, support deflection, product feedback, revenue
16	5. Who is the ideal community member? — Role, motivation, what they hope to get from joining
17
18	Work with whatever context is available. If key details are missing, make reasonable assumptions and flag them.
19
20	---
21
22	## Community Strategy Principles
23
24	### Build around a shared identity, not just a product
25
26	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.
27
28	Examples:
29	- Indie hackers (identity: bootstrapped founders)
30	- r/homelab (identity: tinkerers who self-host)
31	- Figma community (identity: designers who care about craft)
32
33	Always define: What identity does this community reinforce for its members?
34
35	### Value must flow to members first
36
37	Every community touchpoint should answer: What does the member get from this?
38
39	- Exclusive knowledge or early access
40	- Peer connections they can't get elsewhere
41	- Recognition and status within a group they respect
42	- Direct influence on the product roadmap
43	- Career opportunities, visibility, or credibility
44
45	### The Community Flywheel
46
47	Healthy communities compound over time:
48
49	```
50	Members join → get value → engage → create content/help others
51	↑ ↓
52	←←←←← new members discover the community ←←
53	```
54
55	Design for the flywheel from day one. Every decision should ask: Does this accelerate the loop or slow it down?
56
57	---
58
59	## Playbooks by Goal
60
61	### Launching a Community from Zero
62
63	1. Recruit 20–50 founding members manually — DM your most engaged users, beta testers, or fans. Don't open publicly until there is baseline activity.
64	2. Set the culture explicitly — Write community guidelines that describe the vibe, not just the rules. What does great participation look like here?
65	3. Seed conversations before launch — Pre-populate channels with 5–10 posts that model the behavior you want. Questions, wins, resources.
66	4. 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.
67	5. Define your core loop — What action do you want members to take weekly? Make it easy and reward it publicly.
68
69	### Growing an Existing Community
70
71	1. Audit where members drop off — Are people joining but not posting? Posting once and disappearing? Identify the leaky stage.
72	2. 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.
73	3. Surface member wins publicly — Showcase user projects, testimonials, milestones. This reinforces identity and signals that participation has rewards.
74	4. Run recurring community rituals — Weekly threads (e.g., "What are you working on?"), monthly AMAs, seasonal challenges. Rituals create habit.
75	5. Identify and invest in power users — 1% of members generate 90% of value. Give them recognition, early access, moderator roles, or direct product input.
76
77	### Building a Brand Ambassador / Advocate Program
78
79	1. Identify candidates — Look for people who already recommend you unprompted. Check reviews, social mentions, community posts.
80	2. Make the ask personal — Don't send a generic form. R

People who liked this also viewed

6 picks

Type

community-marketing

49kinstalls6.5kforks

View on GitHub

How to install community-marketing?

coreyhaines31/marketingskills/community-marketing

$npx -y skills add coreyhaines31/marketingskills --skill community-marketing

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Community Marketing
2
3	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.
4
5	## Before You Start
6
7	Check for product marketing context first:
8	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.
9
10	Understand the situation (ask if not provided):
11
12	1. What is the product or brand? — What problem does it solve, who uses it
13	2. What community platform(s) are in play? — Discord, Slack, Circle, Reddit, Facebook Groups, forum, etc.
14	3. What stage is the community at? — Pre-launch, 0–100 members, 100–1k, scaling, or established
15	4. What is the primary community goal? — Retention, activation, word-of-mouth, support deflection, product feedback, revenue
16	5. Who is the ideal community member? — Role, motivation, what they hope to get from joining
17
18	Work with whatever context is available. If key details are missing, make reasonable assumptions and flag them.
19
20	---
21
22	## Community Strategy Principles
23
24	### Build around a shared identity, not just a product
25
26	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.
27
28	Examples:
29	- Indie hackers (identity: bootstrapped founders)
30	- r/homelab (identity: tinkerers who self-host)
31	- Figma community (identity: designers who care about craft)
32
33	Always define: What identity does this community reinforce for its members?
34
35	### Value must flow to members first
36
37	Every community touchpoint should answer: What does the member get from this?
38
39	- Exclusive knowledge or early access
40	- Peer connections they can't get elsewhere
41	- Recognition and status within a group they respect
42	- Direct influence on the product roadmap
43	- Career opportunities, visibility, or credibility
44
45	### The Community Flywheel
46
47	Healthy communities compound over time:
48
49	```
50	Members join → get value → engage → create content/help others
51	↑ ↓
52	←←←←← new members discover the community ←←
53	```
54
55	Design for the flywheel from day one. Every decision should ask: Does this accelerate the loop or slow it down?
56
57	---
58
59	## Playbooks by Goal
60
61	### Launching a Community from Zero
62
63	1. Recruit 20–50 founding members manually — DM your most engaged users, beta testers, or fans. Don't open publicly until there is baseline activity.
64	2. Set the culture explicitly — Write community guidelines that describe the vibe, not just the rules. What does great participation look like here?
65	3. Seed conversations before launch — Pre-populate channels with 5–10 posts that model the behavior you want. Questions, wins, resources.
66	4. 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.
67	5. Define your core loop — What action do you want members to take weekly? Make it easy and reward it publicly.
68
69	### Growing an Existing Community
70
71	1. Audit where members drop off — Are people joining but not posting? Posting once and disappearing? Identify the leaky stage.
72	2. 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.
73	3. Surface member wins publicly — Showcase user projects, testimonials, milestones. This reinforces identity and signals that participation has rewards.
74	4. Run recurring community rituals — Weekly threads (e.g., "What are you working on?"), monthly AMAs, seasonal challenges. Rituals create habit.
75	5. Identify and invest in power users — 1% of members generate 90% of value. Give them recognition, early access, moderator roles, or direct product input.
76
77	### Building a Brand Ambassador / Advocate Program
78
79	1. Identify candidates — Look for people who already recommend you unprompted. Check reviews, social mentions, community posts.
80	2. Make the ask personal — Don't send a generic form. R

People who liked this also viewed

6 picks

Type