Source profileQuality 75/100

coreyhaines31/marketingskills/skills/community-marketing/SKILL.md

community-marketing

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

Source repository stars
42,015
Declared platforms
0
Static risk flags
0
Last source update
2026-07-27
Source checked
2026-07-28

Decision brief

What it does—and where it fits

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.

Best for

  • 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…

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/coreyhaines31/marketingskills --skill "skills/community-marketing"
Safe inspection promptEditorial

Inspect the Agent Skill "community-marketing" from https://github.com/coreyhaines31/marketingskills/blob/7868cb9251fad80a73d26e488a5ad5f6c4a9f335/skills/community-marketing/SKILL.md at commit 7868cb9251fad80a73d26e488a5ad5f6c4a9f335. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    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 c…

    What is the product or brand? — What problem does it solve, who uses itWhat 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
  2. 02

    Community Strategy Principles

    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.

    Indie hackers (identity: bootstrapped founders)r/homelab (identity: tinkerers who self-host)Figma community (identity: designers who care about craft)
  3. 03

    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.

    Indie hackers (identity: bootstrapped founders)r/homelab (identity: tinkerers who self-host)Figma community (identity: designers who care about craft)
  4. 04

    Value must flow to members first

    Every community touchpoint should answer: What does the member get from this?

    Exclusive knowledge or early accessPeer connections they can't get elsewhereRecognition and status within a group they respect
  5. 05

    The Community Flywheel

    Healthy communities compound over time:

    Healthy communities compound over time:Design for the flywheel from day one. Every decision should ask: Does this accelerate the loop or slow it down?

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score75/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars42,015SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
coreyhaines31/marketingskills
Skill path
skills/community-marketing/SKILL.md
Commit
7868cb9251fad80a73d26e488a5ad5f6c4a9f335
License
MIT
Collected
2026-07-28
Default branch
main
View the original SKILL.md

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):

  1. What is the product or brand? — What problem does it solve, who uses it
  2. What community platform(s) are in play? — Discord, Slack, Circle, Reddit, Facebook Groups, forum, etc.
  3. What stage is the community at? — Pre-launch, 0–100 members, 100–1k, scaling, or established
  4. What is the primary community goal? — Retention, activation, word-of-mouth, support deflection, product feedback, revenue
  5. 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

  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.
  2. Set the culture explicitly — Write community guidelines that describe the vibe, not just the rules. What does great participation look like here?
  3. Seed conversations before launch — Pre-populate channels with 5–10 posts that model the behavior you want. Questions, wins, resources.
  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.
  5. Define your core loop — What action do you want members to take weekly? Make it easy and reward it publicly.

Growing an Existing Community

  1. Audit where members drop off — Are people joining but not posting? Posting once and disappearing? Identify the leaky stage.
  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.
  3. Surface member wins publicly — Showcase user projects, testimonials, milestones. This reinforces identity and signals that participation has rewards.
  4. Run recurring community rituals — Weekly threads (e.g., "What are you working on?"), monthly AMAs, seasonal challenges. Rituals create habit.
  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.

Building a Brand Ambassador / Advocate Program

  1. Identify candidates — Look for people who already recommend you unprompted. Check reviews, social mentions, community posts.
  2. Make the ask personal — Don't send a generic form. Reach out 1:1 and explain why you chose them specifically.
  3. Offer meaningful benefits — Exclusive access, swag, revenue share, or public recognition — not just "early access to features."
  4. Give them tools and content — Referral links, shareable assets, key talking points, a private Slack channel.
  5. Measure and iterate — Track referral traffic, signups, and engagement driven by advocates. Double down on what works.

Community-Led Support (Deflection + Retention)

  1. Create a searchable knowledge base from top community questions
  2. Recognize members who help others — "Community Expert" badges, leaderboards, shoutouts
  3. Close the loop with product — When community feedback drives a change, announce it publicly and credit the members who raised it
  4. Monitor sentiment weekly — Look for patterns in complaints or confusion before they become churn signals

Platform Selection Guide

PlatformBest ForWatch Out For
DiscordDeveloper, gaming, creator communities; real-time chatHigh noise, hard to search, onboarding friction
SlackB2B / professional communities; familiar to SaaS buyersFree tier limits history; feels like work
CircleCreator or course-based communities; clean UXLess organic discovery; requires driving traffic
RedditHigh-volume public communities; SEO benefitYou don't own it; moderation is hard
Facebook GroupsConsumer brands; older demographicsDeclining organic reach; algorithm dependent
Forum (Discourse)Long-form technical communities; SEO-richSlower 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

  1. What platform are you building on (or considering)?
  2. What stage is the community at? (Pre-launch, early, growing, established)
  3. What's the primary business goal? (Retention, activation, word-of-mouth, support deflection)
  4. Who is the ideal community member and what motivates them?
  5. Do you have existing users or customers to seed from?
  6. 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

Alternatives

Compare before choosing

Computed 1007

event4u-app/agent-config

design-intelligence

Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.

Computed 9827

MoizIbnYousaf/marketing-cli

higgsfield-generate

Use when the user wants to generate an image or video via Higgsfield AI. Covers 30+ models: Soul V2, Seedance 2.0, Kling 3.0, Veo 3.1, GPT Image 2, Nano Banana 2. Also covers Marketing Studio — branded ad video/image with avatars and products. Use whenever: "generate an image", "make a video", "animate this photo", "image-to-video", "img2vid", "edit this image with AI", "produce a clip", "create an ad", "make a UGC video", "marketing video", "brand video", "TV spot", "import product from URL", "

Computed 9727

MoizIbnYousaf/marketing-cli

create-skill

Create new marketing skills for the mktg playbook. Use when the agent needs to add a new capability, someone says 'create a skill', 'new skill', 'add a marketing skill', 'extend the playbook', 'I need a skill for X', 'build a skill', 'make a skill for Y', or 'add capability for Z'. Also use when someone wants to capture a marketing workflow they just did into a reusable skill, or when they say 'turn this into a skill'. Reads the skill contract, generates SKILL.md with correct frontmatter and str

Computed 9727

MoizIbnYousaf/marketing-cli

creative

Generate visual asset briefs, ad copy variants, AI image prompts, video scripts, and storyboards. Full creative production system with 5 specialized modes: product photos, product video, social graphics, talking heads, and ad creative. Make sure to use this skill whenever the user mentions any visual or creative marketing need — ad creative, image prompts, video scripts, thumbnails, banners, social graphics, product photography, storyboards, or marketing visuals of any kind. Even if they just sa