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.
A skill your agent uses to build a genuine community — turning an audience into people who interact with each other, not just with the brand.
Install Community Management
$ npx skills add social-media-skills/skills --skill community-management -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install social-media-skills/skills community-management --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/social-media-skills/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/community-management .claude/skills/community-management && rm -rf skills-srcUse ~/.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/
Install the "community-management" agent skill from https://github.com/social-media-skills/skills/tree/main/skills/community-management into .claude/skills/community-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "community-management", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/social-media-skills/skills/tree/main/skills/community-managementType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add social-media-skills/skills --skill community-management -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install social-media-skills/skills community-management --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/social-media-skills/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/community-management .agents/skills/community-management && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "community-management" agent skill from https://github.com/social-media-skills/skills/tree/main/skills/community-management into .agents/skills/community-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "community-management", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add social-media-skills/skills --skill community-management -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install social-media-skills/skills community-management --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/social-media-skills/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/community-management .cursor/skills/community-management && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "community-management" agent skill from https://github.com/social-media-skills/skills/tree/main/skills/community-management into .cursor/skills/community-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "community-management", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/social-media-skills/skills.git --path skills/community-management--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add social-media-skills/skills --skill community-management -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install social-media-skills/skills community-management --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/social-media-skills/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/community-management .gemini/skills/community-management && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "community-management" agent skill from https://github.com/social-media-skills/skills/tree/main/skills/community-management into .gemini/skills/community-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "community-management", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install social-media-skills/skills community-managementInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add social-media-skills/skills --skill community-management -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/social-media-skills/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/community-management .github/skills/community-management && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "community-management" agent skill from https://github.com/social-media-skills/skills/tree/main/skills/community-management into .github/skills/community-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "community-management", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add social-media-skills/skills --skill community-management -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install social-media-skills/skills community-management --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/social-media-skills/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/community-management .opencode/skills/community-management && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "community-management" agent skill from https://github.com/social-media-skills/skills/tree/main/skills/community-management into .opencode/skills/community-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "community-management", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
community-management- GitHub stars
- 134
- Token cost
- ~1.7k tokens
- SKILL.md length
- 660 words
- Files
- 6 (incl. references)
- Skills in repo
- 106
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses to build a genuine community — turning an audience into people who interact with each other, not just with the brand.
- Works in 5 steps: Read the context → Diagnose: audience or community? → Choose the space (by audience + purpose,… → …
- Build a genuine community — turning an audience into people who interact with each other
- SKILL.md covers Step 0 — Read the context, Step 1 — Diagnose: audience or…, Step 2 — Choose the space (by… and Step 3 — Build belonging with…, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Community Management is an agent skill from social-media-skills/skills. Use to build a genuine community — turning an audience into people who interact with each other, not just with the brand. Run when the user asks how to build community, foster belonging/loyalty, create superfans, start a group/Discord channel, get members talking to each other, or move beyond chasing followers/virality. Reads brand-profile/social-strategy/audience-research. Community outperforms virality, measured by relationship depth/retention, not follower count. Covers the audience-to-community distinction…
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `evals/evals.json`, `references/audience-to-community.md` and `references/building-belonging.md`).
It sits in Marketing & SEO, covering Social media marketing, Market research and OKRs and executive reporting. It works with Discord and Slack. The repository describes itself as: 106 social media skills for AI agents - strategy, writing, video, design, platform growth, publishing, and analytics. Works with Claude, Cursor, OpenClaw, Hermes & 40+ agents. The licence is MIT.
When your agent uses it
- Build a genuine community — turning an audience into people who interact with each other
- Not just with the brand
- Asks how to build community
- Foster belonging/loyalty
Example prompts
- “/community-management”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 6e30eeb. 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 Management loads about 1.7k tokens when it runs, and up to ~4.7k if it reads all its reference files. Until then it costs about 253 tokens; SKILL.md has 660 words of instructions outside code blocks.
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 social-media-skills/skills at commit 6e30eeb, republished under its MIT licence (© social-media-skills). 660 words, ~1,674 tokens.
Download SKILL.mdSave it as
.claude/skills/community-management/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- community-management
- description
- Use to build a genuine community — turning an audience into people who interact with each other, not just with the brand. Run when the user asks how to build community, foster belonging/loyalty, create superfans, start a group/Discord channel, get members talking to each other, or move beyond chasing followers/virality. Reads brand-profile/social-strategy/audience-research. Community outperforms virality, measured by relationship depth/retention, not follower count. Covers the audience-to-community distinction (member-to-member interaction), choosing the space (in-feed -> semi-owned -> owned groups/Discord), recurring rituals, building belonging, and nurturing superfans into advocates. KPIs read natively, never fabricated. Advisory: WoopSocial schedules the content but does NOT run Discord/Slack or show analytics — the human runs the community, the agent drafts. Never fake community; get consent before spotlighting. Pairs with reply-and-comment-writer and crisis-and-moderation.
- metadata.version
- 1.0.0
- license
- MIT
Community Management
Turn an audience into a community — the strategy layer of the engagement cluster. The tactical
skills handle the brand talking to people (reply-and-comment-writer = craft, engagement-routine =
cadence, crisis-and-moderation = when it goes wrong). This skill builds the space where members talk
to each other.
The 2026 shift is broadcasting → belonging: community outperforms virality, it's algorithm-proof (closed spaces aren't suppressed by feed changes), and it's measured by relationship depth, not follower count. A real community is a moat; an audience is rented.
Step 0 — Read the context
Load brand-profile.md, social-strategy.md, audience-research.md: who these people are, what they
care about, and where they already gather.
Step 1 — Diagnose: audience or community?
The marker is member-to-member. Diagnostic: is your comment section all brand replies, or are
members talking to each other? The goal is a self-sustaining space where members help each
other. Then define the purpose — the clear reason this community exists (no purpose → it plateaus).
See references/audience-to-community.md.
Step 2 — Choose the space (by audience + purpose, not hype)
Pick along the spectrum — in-feed comment culture → semi-owned (broadcast channels/DMs) → owned
(groups/Discord/Substack/newsletter) — by where the audience already is and whether there's a
clear promise to join. Don't launch a Discord because a competitor did. Max out in-feed first;
graduate the engaged into an owned space you can commit to (it needs moderation from day one →
crisis-and-moderation). See references/where-community-lives.md.
Step 3 — Build belonging with rituals
Run the seven moves (initiate conversations, exclusive spaces, shared identity/inside language,
respond personally, feature members, surprise-and-delight, facilitate member-to-member connections)
on a backbone of recurring rituals (weekly thread, AMA, challenge, member spotlight, resource drop)
— consistency over scattered activity. Schedule the ritual content via scheduling-and-queue. See
references/building-belonging.md.
Step 4 — Nurture superfans
Find the devoted core, nurture them (recognition, access, status/roles, collaboration), and
elevate them into advocates (lurker → regular → advocate). A small core beats broad reach. See
references/superfans-and-honest-scope.md.
Measure community, not vanity
Active members, returning members/retention, member-to-member interaction, response time, advocacy — not follower count. Read natively (no WoopSocial analytics); never fabricate a number. Community is a long game — judged over months.
Honest scope (always)
- WoopSocial schedules the community content (rituals, prompts, spotlights, announcements) via
scheduling-and-queue— that's its real role. It does not run Discord/Slack/groups, manage a broadcast channel or inbox, identify superfans from data, or show analytics. The human runs the space in-platform; the agent advises + drafts/schedules. - No fake community — no bought members, pods, or astroturfing (fake, detected, trust-destroying).
- Consent & privacy — get permission before spotlighting a member; don't expose member data.
- Sustainable — don't open a space you can't keep tending (boundaries →
engagement-routine).
Show full SKILL.md (242 more words)Show less
Quality bar — self-check
- Did I diagnose audience vs community (member-to-member marker) and define a purpose?
- Did I choose the space by audience + purpose, not hype, and max out in-feed before an owned space?
- Did I design recurring rituals + belonging moves that get members connecting with each other?
- Did I plan to nurture superfans into advocates, and measure by community signals (not vanity, not fabricated)?
- Did I keep it advisory + genuine (WoopSocial schedules content; human runs the space; no fake community; consent)?
Edge cases & pushback
- "Big following = community?" → no; the marker is member-to-member, self-sustaining interaction.
- "Competitor has a Discord, should we?" → purpose gate + where the audience is; commitment/moderation.
- "How do I measure it?" → community signals read natively; no vanity, no fabricated numbers.
- "Buy members / run a pod to look active" → refuse; genuine belonging only; consent for spotlights.
- "Run our Discord / find my top members via WoopSocial" → WoopSocial schedules content, doesn't run spaces/inbox or show analytics; human runs it, agent drafts.
Related
reply-and-comment-writer— the personal replies that build belonging;engagement-routine— the cadence + boundaries.crisis-and-moderation— protecting/moderating the community;content-pillars— a "community" pillar.scheduling-and-queue— schedule the ritual/spotlight content;profile-optimization— the community's front door.audience-research,social-strategy,brand-profile— who the community is for and why.
References
references/audience-to-community.md— the core distinction, why it matters, purpose, and community KPIs.references/where-community-lives.md— the in-feed → semi-owned → owned spectrum and choosing by audience + purpose.references/building-belonging.md— the seven moves, the rituals engine, UGC/live, and how WoopSocial helps.references/superfans-and-honest-scope.md— finding/nurturing/elevating superfans, and the genuine-only honest scope.
© social-media-skills, 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 5 other files (references) in skills/community-management of social-media-skills/skills.
- SKILL.md
- evals/evals.json
- references/audience-to-community.md
- references/building-belonging.md
- references/superfans-and-honest-scope.md
- references/where-community-lives.md
Open the folder on GitHubat commit 6e30eeb
Compare with similar skills
Community Management 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Community Management this skillsocial-media-skills/skills | 134 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Community Seeding Planminhnv0807/ai-business-skills | 609 | — | ~3.2k | Automated safety check: Pass | MIT | |
| Suede Community MarketingJasonColapietro/suede-creator-skills | 127 | — | ~3k | Automated safety check: Pass | MIT | |
| Paw Mkt Communitypawbytes/skill-suites | 113 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Community Moderation Policymohitagw15856/pm-claude-skills | 1.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Blog DiscourseAgriciDaniel/claude-blog | 2.3k | 1 repos | ~3.4k | Automated safety check: Warn | MIT |
Similar skills
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.
Paw Mkt Community
pawbytes/skill-suites
Builds and manages owned community platforms. An agent skill from pawbytes/skill-suites.
Community Moderation Policy
mohitagw15856/pm-claude-skills
Write a fair, enforceable community moderation policy. An agent skill from mohitagw15856/pm-claude-skills.
Blog Discourse
AgriciDaniel/claude-blog
Research what people are actually saying about a topic in the last 30 days across Reddit, X / Twitter, YouTube, Hacker News, dev.to, Medium, and other public discourse platforms.
Community Marketing
Nexus-JPF/note-companion
Build and leverage online communities to drive product growth and brand loyalty.
More from social-media-skills/skills
All 106 skills in this repoAI Image Editing
social-media-skills/skills
The AI image-editing router — inpainting/object removal, background removal, upscaling, outpainting, old-photo restoration, and retouch, routed task-first to the right engine.
AI Music And Sound
social-media-skills/skills
The AI music + sound-design skill for social -- original/licensed audio beds and sound design for Reels/TikToks/Shorts/videos.
AI Search Optimization
social-media-skills/skills
A skill your agent uses to get a brand and its content CITED and RECOMMENDED by AI answer engines — the GEO (Generative Engine Optimization) / AI-search-visibility skill.
AI Video
social-media-skills/skills
The model-agnostic AI-video router and brief — the counterpart to image-prompt.
AI Voiceover
social-media-skills/skills
The AI narration / voiceover mini-skill (ElevenLabs-led). An agent skill from social-media-skills/skills.
Analytics And Reporting
social-media-skills/skills
Social media analytics and reporting — read native platform data honestly and turn it into next actions.
Related
Categories
Questions about Community Management
What does Community Management do?
A skill your agent uses to build a genuine community — turning an audience into people who interact with each other, not just with the brand. Community Management is an agent skill from social-media-skills/skills. Use to build a genuine community — turning an audience into people who interact with each other, not just with the brand.
When should I use Community Management?
Community Management fits situations like: build a genuine community — turning an audience into people who interact with each other; not just with the brand; asks how to build community; foster belonging/loyalty.
How do I install Community Management in Claude Code?
Run `npx skills add social-media-skills/skills --skill community-management -a claude-code`. Or copy the skill folder (skills/community-management in social-media-skills/skills) into .claude/skills/community-management in your project. Claude Code loads it when a task matches its description.
How do I install Community Management in Codex?
Run `npx skills add social-media-skills/skills --skill community-management -a codex`. Or copy the skill folder (skills/community-management in social-media-skills/skills) into .agents/skills/community-management in your project. Codex loads it when a task matches its description.
Can I use Community Management 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 social-media-skills/skills --skill community-management -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-management, .gemini/skills/community-management, .github/skills/community-management and .opencode/skills/community-management in your project.
What does Community Management need to run?
SKILL.md names no scripts, command-line tools or credentials: Community Management is instructions for the agent only.
Does Community Management 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 Management 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 Management use?
Community Management is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Community Management use?
About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3k tokens, read only when the agent opens those files.
What are the alternatives to Community Management?
Skills that share tags, products or a category with Community Management: Community Seeding Plan (minhnv0807/ai-business-skills, 609 stars), Suede Community Marketing (JasonColapietro/suede-creator-skills, 127 stars), Paw Mkt Community (pawbytes/skill-suites, 113 stars) and Community Moderation Policy (mohitagw15856/pm-claude-skills, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Community Management?
social-media-skills (a GitHub organization) maintains it in social-media-skills/skills, which has 134 GitHub stars. The repository holds 106 skills in this directory. The repository was last updated on October 1, 2026.
Source: social-media-skills/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.