Agent skill

Community Marketing

by Nexus-JPF in Nexus-JPF/note-companion

Build and leverage online communities to drive product growth and brand loyalty.

MITAuto-check passedMarketing & SEO

Install Community Marketing

skills CLI
$ npx skills add Nexus-JPF/note-companion --skill community-marketing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Nexus-JPF/note-companion community-marketing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/community-marketing .claude/skills/community-marketing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
community-marketing
GitHub stars
870
Used in
4 other repos
Token cost
~2.2k tokens
SKILL.md length
1,097 words
Files
2
Skills in repo
18
Repo updated
First seen
Licence
MIT

At a glance

Build and leverage online communities to drive product growth and brand loyalty.

  • Works in 5 steps: What is the product or brand? — What… → What community platform(s) are in play?… → What stage is the community at? —… → …
  • The user wants to create a community strategy
  • SKILL.md covers Before You Start, Community Strategy Principles, Playbooks by Goal and Platform Selection Guide, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Community Marketing is an agent skill from Nexus-JPF/note-companion. 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,"…

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `evals/evals.json`).

It sits in Marketing & SEO. It works with Discord, Slack and Reddit. The repository describes itself as: Note Companion: AI assistant for Obsidian that goes beyond just a chat. (prev File Organizer 2000). The licence is MIT.

When your agent uses it

  • The user wants to create a community strategy
  • Slack community
  • Build brand advocates
  • Increase word-of-mouth

Example prompts

  • “build a community,”
  • “community strategy,”
  • “Discord community,”
  • “/community-marketing”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  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

What it can do on your machine

Read from SKILL.md and the folder at commit 9cad635. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Community Marketing loads about 2.2k tokens when it runs. Until then it costs about 157 tokens; SKILL.md has 1,097 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~157
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Nexus-JPF/note-companion at commit 9cad635, republished under its MIT licence (© Nexus-JPF). 1,097 words, ~2,214 tokens.

Download SKILL.mdSave it as .claude/skills/community-marketing/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
community-marketing
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."
metadata.version
2.0.0

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.
Show full SKILL.md (444 more words)Show less
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?

  • 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

© Nexus-JPF, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/community-marketing of Nexus-JPF/note-companion.

  • SKILL.md
  • evals/evals.json

Open the folder on GitHubat commit 9cad635

Used in 4 other repositories

We found 6 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 4 other GitHub owners. This page covers the copy in Nexus-JPF/note-companion, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Community Marketing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Community Marketing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Community Marketing this skillNexus-JPF/note-companion8704 repos~2.2kAutomated safety check: PassMIT
Community Seeding Planminhnv0807/ai-business-skills609—~3.2kAutomated safety check: PassMIT
Suede Community MarketingJasonColapietro/suede-creator-skills127—~3kAutomated safety check: PassMIT
Community Moderation Policymohitagw15856/pm-claude-skills1.4k—~1.1kAutomated safety check: PassMIT
Community Discoveryshawnpang/startup-founder-skills343—~1.8kAutomated safety check: PassMIT
Happycapy Social Publisherhappycapy-ai/Happycapy-skills137—~3.6kAutomated safety check: NotesMIT

Similar skills

  • Community Seeding Plan

    minhnv0807/ai-business-skills

    Plans honest participation in outside communities such as Reddit, Discord and Facebook Groups, with a rules-based community list, roster, posts, replies and calendar.

    609 GitHub stars~3.2k tokensUpdated 29 days ago
    Marketing & SEOAuto-check passed
  • Suede Community Marketing

    JasonColapietro/suede-creator-skills

    Suede-owned community-growth discipline for member purpose, platform choice, seeding, rituals, moderation, health metrics, and earned advocacy.

    127 GitHub stars~3k tokensUpdated yesterday
    Marketing & SEOAuto-check passed
  • Community Moderation Policy

    mohitagw15856/pm-claude-skills

    Write a fair, enforceable community moderation policy. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Legal & ComplianceAuto-check passed
  • Community Discovery

    shawnpang/startup-founder-skills

    When the user wants to find Slack groups, Discord servers, Reddit communities, forums, or online communities where their target audience hangs out.

    343 GitHub stars~1.8k tokensUpdated 6 mo ago
    Auto-check passed
  • Happycapy Social Publisher

    happycapy-ai/Happycapy-skills

    HappyCapy-specific skill for publishing content to 13+ social media platforms (Instagram, Twitter, LinkedIn, Threads, Facebook, TikTok, YouTube, Pinterest, Reddit, Telegram, Discord, etc.)…

    137 GitHub stars~3.6k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check: notes
  • Participation Warmup Planner

    aaron-he-zhu/aaron-marketing-skills

    A skill your agent uses when the user asks to "plan the participation ramp before we promote", "how much account history or karma do we need in this community", or "design entry incentives and…

    2.9k GitHub stars~3.6k tokensUpdated yesterday
    Marketing & SEOAuto-check passed

More from Nexus-JPF/note-companion

All 18 skills in this repo
  • Analytics

    Nexus-JPF/note-companion

    When the user wants to set up, improve, or audit analytics tracking and measurement.

    870 GitHub starsUsed in 7 repos~2.2k tokens
    Auto-check passed
  • Customer Research

    Nexus-JPF/note-companion

    When the user wants to conduct, analyze, or synthesize customer research.

    870 GitHub starsUsed in 6 repos~3.2k tokens
    Auto-check passed
  • Marketing Plan

    Nexus-JPF/note-companion

    When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.

    870 GitHub starsUsed in 5 repos~5.2k tokens
    Auto-check passed
  • Competitor Profiling

    Nexus-JPF/note-companion

    When the user wants to research, profile, or analyze competitors from their URLs.

    870 GitHub starsUsed in 4 repos~3.5k tokens
    Auto-check passed
  • Onboarding

    Nexus-JPF/note-companion

    When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value.

    870 GitHub starsUsed in 4 repos~1.6k tokens
    Auto-check passed
  • Image

    Nexus-JPF/note-companion

    When the user wants to create, generate, edit, or optimize images for marketing — blog heroes, social graphics, product mockups, profile banners, listing visuals, or brand assets.

    870 GitHub starsUsed in 3 repos~3.9k tokens
    Auto-check passed

Categories

Questions about Community Marketing

What does Community Marketing do?

Build and leverage online communities to drive product growth and brand loyalty. Community Marketing is an agent skill from Nexus-JPF/note-companion. Build and leverage online communities to drive product growth and brand loyalty.

When should I use Community Marketing?

Community Marketing fits situations like: the user wants to create a community strategy; slack community; build brand advocates; increase word-of-mouth.

How do I install Community Marketing in Claude Code?

Run `npx skills add Nexus-JPF/note-companion --skill community-marketing -a claude-code`. Or copy the skill folder (.agents/skills/community-marketing in Nexus-JPF/note-companion) into .claude/skills/community-marketing in your project. Claude Code loads it when a task matches its description.

How do I install Community Marketing in Codex?

Run `npx skills add Nexus-JPF/note-companion --skill community-marketing -a codex`. Or copy the skill folder (.agents/skills/community-marketing in Nexus-JPF/note-companion) into .agents/skills/community-marketing in your project. Codex loads it when a task matches its description.

Can I use Community Marketing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Nexus-JPF/note-companion --skill community-marketing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/community-marketing, .gemini/skills/community-marketing, .github/skills/community-marketing and .opencode/skills/community-marketing in your project.

What does Community Marketing need to run?

SKILL.md names no scripts, command-line tools or credentials: Community Marketing is instructions for the agent only.

Does Community Marketing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Community Marketing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Community Marketing use?

Community Marketing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Community Marketing use?

About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Community Marketing?

Skills that share tags, products or a category with Community Marketing: Community Seeding Plan (minhnv0807/ai-business-skills, 609 stars), Suede Community Marketing (JasonColapietro/suede-creator-skills, 127 stars), Community Moderation Policy (mohitagw15856/pm-claude-skills, 1.4k stars) and Community Discovery (shawnpang/startup-founder-skills, 343 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Community Marketing?

Nexus-JPF (a GitHub organization) maintains it in Nexus-JPF/note-companion, which has 870 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 7, 2026.

Source: Nexus-JPF/note-companion on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.