New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Community Seeding Plan

by minhnv0807 in 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.

MITAuto-check passedMarketing & SEO

Install Community Seeding Plan

skills CLI
$ npx skills add minhnv0807/ai-business-skills --skill 38-community-seeding-global -a claude-code

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

GitHub CLI
$ gh skill install minhnv0807/ai-business-skills 38-community-seeding-global --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/minhnv0807/ai-business-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/en/38-community-seeding-global .claude/skills/38-community-seeding-global && 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
38-community-seeding-global
GitHub stars
609
Token cost
~3.2k tokens
SKILL.md length
1,378 words
Files
2 (incl. references)
Skills in repo
142
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 4 steps: Community research and rules mapping (1… → Participant setup and warm-up (2-4 weeks) → Participation content (ongoing) → …
  • Planning how a team joins relevant subreddits, groups and forums without spamming
  • SKILL.md covers Information gathering, Principles, Workflow — 4 phases and Output structure, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

The skill treats community marketing as participation rather than placement. It first reads the product marketing context and customer insight files, then asks up to four questions about what is being marketed, the objective, who on the team will participate under their real name and any history of removals or bans. The deliverable is a prioritized community list with each space's rules, a named participant roster, full post types, reply scripts, a participation calendar and red lines.

Principles include real people with one account each, roughly nine useful contributions for every promotional one, reading the rules before posting, disclosing any material connection in the post itself, and never writing reviews as if they came from customers, citing FTC rules. `references/platform-rules.md` covers per-platform rules, disclosure mechanics and cadence limits. It is not for building your own community, social listening or briefing paid creators, which have separate skills.

When your agent uses it

  • Planning how a team joins relevant subreddits, groups and forums without spamming
  • Writing replies and post types that follow a community's self-promotion rules
  • Recovering after a brand was removed or banned from a group

Example prompts

  • “Build a Reddit and Discord seeding plan for our open-source invoicing tool.”
  • “Write reply scripts our two founders can use in Facebook Groups, with disclosure included.”
  • “We got banned from a subreddit, so plan how to participate properly from here.”

Requirements

  • A product marketing context file such as `.agents/product-marketing-context-global.md`

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Community research and rules mapping (1 week)
  2. Participant setup and warm-up (2-4 weeks)
  3. Participation content (ongoing)
  4. Measurement

What it can do on your machine

Read from SKILL.md and the folder at commit 0360adc. 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 (its code samples are markdown).

    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 Seeding Plan loads about 3.2k tokens when it runs, and up to ~5.3k if it reads all its reference files. Until then it costs about 183 tokens; SKILL.md has 1,378 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~183
When it runs · the whole SKILL.md, loaded when a task matches
~3.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.3k

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 minhnv0807/ai-business-skills at commit 0360adc, republished under its MIT licence (© minhnv0807). 1,378 words, ~3,224 tokens.

Download SKILL.mdSave it as .claude/skills/38-community-seeding-global/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
38-community-seeding-global
description
Use when the user wants to show up in OTHER communities without astroturfing — Reddit, Facebook Groups, Discord, Slack, LinkedIn groups, Quora, and niche forums: a prioritized community list with the rules of each space, a named participant roster, post types written in full, reply scripts, a participation calendar, and red lines. Trigger on 'community marketing', 'Reddit marketing', 'seeding plan', 'post in Facebook groups', 'answer questions on Quora', 'we got banned from a group'. Not for — building your OWN paid or private community, see `28-community-building-global`; monitoring mentions across the web, see `15-social-listening-global`; briefing paid creators, see `06-ugc-egc-brief-global`.
metadata.version
1.0.1
metadata.category
content
license
MIT
triggers
community marketing, Reddit marketing, seeding plan, post in groups, community strategy, forum marketing, Discord communities, Quora answers
output
File .md — prioritized community list with rules, named participant roster, 4 post types written in full, response scripts, participation calendar…
related
product-marketing-context-global, 09-customer-insight-global, 15-social-listening-global, 35-brand-voice-global, 37-social-caption-global…

Community Seeding (Global)

Community marketing done properly is participation, not placement. A brand earns the right to mention itself by being useful first, under a real name, in communities whose rules it has actually read. Manufactured engagement — sockpuppets, brand-written reviews, coordinated voting — is both against every major platform's rules and, in the US, against FTC rules. Getting caught is a bigger loss than never posting.

Full per-platform rules, disclosure mechanics, and cadence limits: read references/platform-rules.md.

Information gathering

Read .agents/product-marketing-context-global.md and the insight file (09-customer-insight-global) first. If information is missing, ask up to 4 questions:

  1. What is being marketed, and which communities does the target audience actually spend time in? (subreddits, Discord servers, Slack groups, Facebook Groups, LinkedIn groups, Quora topics, niche forums)
  2. What is the objective? Awareness / qualified leads / traffic / genuine social proof / product feedback
  3. Who on the team will participate under their real name, and how much time per week can they give?
  4. Has the brand posted in these communities before — what happened, and was anything removed or banned?

Principles

  1. Real people, real names, one account each. Every participant is an actual member of the team using a single account with their own identity. No personas, no second accounts, no purchased or aged accounts.
  2. Value first, at roughly 9:1. For every promotional or self-referential post, contribute nine genuinely useful ones. This ratio is Reddit's long-standing self-promotion norm and travels well to every other community.
  3. Read the rules before the first post. Every subreddit, server, and group has its own self-promotion policy. Many require flair, a specific thread, or a minimum tenure. Rules override this plan.
  4. Disclose the material connection every time. If the person works for, is paid by, or holds equity in the brand, that must be clear in the post itself — not buried in a bio. This is FTC 16 CFR Part 255.
  5. Never write a review as if it came from a customer. Brand-authored or employee-authored reviews presented as independent are prohibited under the FTC fake-review rule (16 CFR Part 465) and carry civil penalties. Customer stories must come from the customer, with permission on file.
  6. No vote manipulation or coordinated engagement. No asking colleagues to upvote, no brigading, no cross-account replies to your own posts. Platforms detect this reliably.
  7. Warm up before you contribute anything promotional. Minimum two weeks of ordinary participation per community; four is better.
  8. Measurable or it does not count. UTM where links are permitted, a "how did you hear about us" field, and a log of removals and bans.

Workflow — 4 phases

Phase 1 — Community research and rules mapping (1 week)

Selection criteria:

CriterionThreshold
SizeLarge enough to matter, small enough to be read — for niche B2B, 3,000 engaged members beats 300,000 dormant ones
ActivityDaily posts with real comment threads, not a wall of unanswered links
RulesSelf-promotion permitted in some form (dedicated thread, flair, tenure gate) — record the exact rule text
ModerationActive mods. Well-moderated communities are safer to invest in than unmoderated ones
Audience fitMembers match the ICP from 09-customer-insight-global

Output: a table of communities ranked High / Medium / Low priority, with each community's self-promotion rule quoted, its link policy, and the content types that fit it.

Phase 2 — Participant setup and warm-up (2-4 weeks)

Each participant needs:

  • A real profile: real name, real photo, a bio that states where they work. Affiliation visible before anyone has to ask.
  • Genuine history: joined, commented, answered questions 3-5 times a week, without mentioning the brand.
  • A consistent area of expertise that matches what they actually know — a support lead answers support questions, a founder answers business-model questions.
  • No brand mention at all during warm-up.

A new account with no history is not usable for this work. If nobody on the team can commit the time, do not run the plan — hand the objective to 06-ugc-egc-brief-global and work with creators who are already members of those communities, under a disclosed paid arrangement.

Phase 3 — Participation content (ongoing)

Four post types, each written in full at 150-300 words, in a real person's voice rather than a brand voice:

TypePurposeBrand mention rule
1. Genuine question / research postLearn from the community, surface demand languageNo brand mention at all
2. Expertise share / teardownGive real, specific value; earn recognitionAffiliation stated up front; product mentioned only if it is genuinely the answer
3. Answering an existing threadHelp someone who already askedDisclose the connection in the same comment, in plain words
4. Customer story amplificationReal social proofWritten by the customer, posted by the customer or clearly attributed with permission. Never brand-authored

What performs in communities: open questions, specific how-we-did-it write-ups with numbers, short guides, teardowns, and honest post-mortems including what did not work.

Response handling for every post:

  • Prepare honest answers to the 3-5 questions members will realistically ask (pricing, availability, whether it actually works, alternatives — including competitors).
  • Reply within the first few hours. Early real engagement is what most feeds reward.
  • If someone asks whether you work there, answer plainly. Never deflect.
  • Recommend the product only when a member has described a problem it genuinely solves, and disclose in the same breath.
Show full SKILL.md (510 more words)Show less
Phase 4 — Measurement
MetricHow to capture
Post reach and engagementNative post stats per community; screenshot where no export exists
Inbound DMs and mentionsAsk "how did you hear about us" at first contact; log the community
TrafficUTM per community, only where links are allowed by the rules
Leads and revenueCRM source field set to the community name
Removals, warnings, bansLog every one with the rule cited — this is the risk signal that decides whether to keep investing in that community
SentimentTrack how the brand is spoken about unprompted, via 15-social-listening-global

Output structure

File name: community-seeding-[product]-[YYYYMMDD].md

markdown
# Community Seeding Plan — [Product] — [Period]

## I. Target communities
| Community | Platform | Size | Activity | Self-promotion rule (quoted) | Link policy | Priority | Content types that fit |
|-----------|----------|------|----------|------------------------------|-------------|----------|------------------------|
| | | | | | | High/Med/Low | |

## II. Participant roster
| Person | Role | Account | Expertise area | Warm-up status | Communities owned | Weekly time |
|--------|------|---------|----------------|----------------|-------------------|-------------|
| | | | | Not started / In progress / Ready | | |

## III. Four post types — written in full
### Type 1 — Genuine question (no brand mention)
[Full post, 150-300 words, real person's voice]

### Type 2 — Expertise share (affiliation stated up front)
[Full post — real insight, specific, not an advertisement]

### Type 3 — Answering an existing thread (connection disclosed inline)
[Full reply — answers the question first, mentions the product only if it is the honest answer]

### Type 4 — Customer story amplification (customer-authored, permission on file)
[The customer's own words + where permission is recorded]

## IV. Response scripts
| Likely question | Honest prepared answer | Who answers |
|-----------------|------------------------|-------------|
| | | |

## V. Participation calendar
| Date | Community | Post type | Participant | Summary | Target engagement |
|------|-----------|-----------|-------------|---------|-------------------|
| | | | | | |

## VI. Measurement
| Post | Community | Engagement | DMs | Leads | Removed / warned | Notes |
|------|-----------|------------|-----|-------|------------------|-------|
| | | | | | | |

## VII. Compliance log
| Post | Disclosure used | Rule checked | Approver |
|------|-----------------|--------------|----------|
| | | | |

Red lines — never do these

  • Never create or use a persona, sockpuppet, or second account. One real person, one account.
  • Never write a review, testimonial, or "just a happy customer" post on behalf of a customer.
  • Never ask colleagues to upvote, like, or reply to make a post look organic. That is vote manipulation on Reddit and coordinated inauthentic behavior on Meta.
  • Never omit the material-connection disclosure when a participant is an employee, contractor, affiliate, or equity holder.
  • Never post an identical block of text across multiple communities. Spam filters and members both notice.
  • Never drop a product link in the first post to a community, or in any community whose rules forbid links.
  • Never cold-DM members who have not asked to be contacted.
  • Never argue with moderators. If a post is removed, read the rule, adjust, and move on.

Risks to manage: post removal or account ban (lost warm-up time — prevent by following rules); public exposure as astroturfing (severe brand damage — prevent by never doing it, and by answering affiliation questions honestly); community rule changes (re-read rules monthly); FTC enforcement on undisclosed endorsements and fake reviews (prevent with the compliance log in section VII).

  • 09-customer-insight-global: identifies which communities the ICP actually uses and supplies their real language.
  • 15-social-listening-global: tells you what the community is already discussing, so the angle fits an active conversation.
  • 35-brand-voice-global: types 2 and 3 still have to match the brand's core message, even written in a personal register.
  • 06-ugc-egc-brief-global: the paid alternative — working with creators and community members through a disclosed paid arrangement.
  • 37-social-caption-global: owned-channel posts, which follow different rules from community posts.
  • 39-content-audit-global: feed community results into the periodic audit to decide which communities to keep.

Quality checklist

  • Every community's self-promotion rule is quoted verbatim, not summarized from memory.
  • Every participant is a real, named person with one account and a stated affiliation.
  • Warm-up of at least two weeks completed before any promotional participation.
  • All 4 post types written in full — no outlines.
  • Posts read as a person wrote them, not a brand page.
  • No brand-authored customer reviews anywhere in the plan.
  • Material connection disclosed in every post where one exists, in the post itself.
  • Value-to-promotion ratio across the calendar is at least 9:1.
  • Cadence respects each community's rules and does not repeat identical text.
  • Measurement defined per post (UTM where permitted, source field, DM attribution).
  • Removal and ban log in place.
  • No red line is crossed anywhere in the plan.

© minhnv0807, 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 (references) in skills/en/38-community-seeding-global of minhnv0807/ai-business-skills.

  • SKILL.md
  • references/platform-rules.md

Open the folder on GitHubat commit 0360adc

Compare with similar skills

Community Seeding Plan 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 Seeding Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Community Seeding Plan this skillminhnv0807/ai-business-skills609—~3.2kAutomated safety check: PassMIT
Community Moderation Policymohitagw15856/pm-claude-skills1.4k—~1.1kAutomated safety check: PassMIT
Suede Clip to GuideJasonColapietro/suede-creator-skills127—~4.1kAutomated safety check: PassMIT
Community MarketingNexus-JPF/note-companion8704 repos~2.2kAutomated safety check: PassMIT
Happycapy Social Publisherhappycapy-ai/Happycapy-skills137—~3.6kAutomated safety check: NotesMIT
Suede Community MarketingJasonColapietro/suede-creator-skills127—~3kAutomated safety check: PassMIT

Similar skills

  • 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

  • Suede Clip to Guide

    JasonColapietro/suede-creator-skills

    Turns a video clip, interview moment or transcript into a package that bridges viewers to a long-form guide, with rights, claim and approval gates along the way.

    127 GitHub stars~4.1k tokensUpdated yesterday
    Marketing & SEOAuto-check passed

  • Community Marketing

    Nexus-JPF/note-companion

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

    870 GitHub starsUsed in 4 repos~2.2k tokens
    Marketing & SEOAuto-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

  • 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

  • Delta Engage

    aiskillstore/marketplace

    Finds high-fit posts to engage with across Reddit and LinkedIn based on the user's positioning and ICP, then drafts platform-appropriate engagement angles.

    433 GitHub stars~4.3k tokensUpdated yesterday
    Marketing & SEOAuto-check passed

More from minhnv0807/ai-business-skills

All 142 skills in this repo

  • Design Master

    minhnv0807/ai-business-skills

    Handles eight kinds of marketing visual requests, from logos and campaign key visuals to infographics and quote graphics, by generating images or writing paste-ready prompts.

    609 GitHub stars~4.6k tokensUpdated 29 days ago
    Auto-check passed

  • Offer Design

    minhnv0807/ai-business-skills

    Designs or repairs what a business sells, covering the promise, value stack, bonuses, guarantee, honest scarcity and a tiered ladder, rather than price or copy.

    609 GitHub stars~1.1k tokensUpdated 29 days ago
    Auto-check passed

  • Global SEO Growth

    minhnv0807/ai-business-skills

    Covers six SEO layers for a website: crawl and index audit, local SEO, search-intent content, AI search visibility, schema markup and backlink or directory distribution.

    609 GitHub stars~5k tokensUpdated 29 days ago
    Auto-check passed

  • B2B Lead Generation

    minhnv0807/ai-business-skills

    Plans B2B pipeline work from ICP definition and prospecting through lead scoring, outbound sequences, sales assets and MQL to SQL handoff, aiming at qualified pipeline.

    609 GitHub stars~1.2k tokensUpdated 29 days ago
    Auto-check passed

  • Ad Conversion Tracking Setup

    minhnv0807/ai-business-skills

    Sets up and verifies conversion tracking before ad spend: Meta Pixel and CAPI, Google Ads, GA4, TikTok, server-side GTM, consent mode, UTMs and a pre-launch checklist.

    609 GitHub stars~3.7k tokensUpdated 29 days ago
    Auto-check passed

  • Global Marketing Plan

    minhnv0807/ai-business-skills

    Builds a full marketing plan for a period, from objectives and segments to channel mix, budget, timeline, KPIs and risks, adapted to the US, EU, SEA or LATAM.

    609 GitHub stars~4.4k tokensUpdated 29 days ago
    Auto-check passed

Works with

Categories

Questions about Community Seeding Plan

What does Community Seeding Plan do?

Plans honest participation in outside communities such as Reddit, Discord and Facebook Groups, with a rules-based community list, roster, posts, replies and calendar. The skill treats community marketing as participation rather than placement. It first reads the product marketing context and customer insight files, then asks up to four questions about what is being marketed, the objective, who on the team will participate under their real name and any history of removals or bans.

When should I use Community Seeding Plan?

Community Seeding Plan fits situations like: planning how a team joins relevant subreddits, groups and forums without spamming; writing replies and post types that follow a community's self-promotion rules; recovering after a brand was removed or banned from a group.

How do I install Community Seeding Plan in Claude Code?

Run `npx skills add minhnv0807/ai-business-skills --skill 38-community-seeding-global -a claude-code`. Or copy the skill folder (skills/en/38-community-seeding-global in minhnv0807/ai-business-skills) into .claude/skills/38-community-seeding-global in your project. Claude Code loads it when a task matches its description.

How do I install Community Seeding Plan in Codex?

Run `npx skills add minhnv0807/ai-business-skills --skill 38-community-seeding-global -a codex`. Or copy the skill folder (skills/en/38-community-seeding-global in minhnv0807/ai-business-skills) into .agents/skills/38-community-seeding-global in your project. Codex loads it when a task matches its description.

Can I use Community Seeding Plan 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 minhnv0807/ai-business-skills --skill 38-community-seeding-global -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/38-community-seeding-global, .gemini/skills/38-community-seeding-global, .github/skills/38-community-seeding-global and .opencode/skills/38-community-seeding-global in your project.

What does Community Seeding Plan need to run?

SKILL.md names no scripts, command-line tools or credentials: Community Seeding Plan is instructions for the agent only. Our summary lists: A product marketing context file such as `.agents/product-marketing-context-global.md`.

Does Community Seeding Plan 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 Seeding Plan 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 Seeding Plan use?

Community Seeding Plan 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 Seeding Plan use?

About 3.2k tokens (SKILL.md is roughly 13k 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 2.1k tokens, read only when the agent opens those files.

What are the alternatives to Community Seeding Plan?

Skills that share tags, products or a category with Community Seeding Plan: Community Moderation Policy (mohitagw15856/pm-claude-skills, 1.4k stars), Suede Clip to Guide (JasonColapietro/suede-creator-skills, 127 stars), Community Marketing (Nexus-JPF/note-companion, 870 stars) and Happycapy Social Publisher (happycapy-ai/Happycapy-skills, 137 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Community Seeding Plan?

minhnv0807 (a GitHub user) maintains it in minhnv0807/ai-business-skills, which has 609 GitHub stars. The repository holds 142 skills in this directory. The repository was last updated on September 12, 2026.

Source: minhnv0807/ai-business-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.