Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when the user wants a plan for showing up in communities — Reddit, Facebook Groups, Discord, Slack, LinkedIn groups, Quora, niche forums — without astroturfing. Trigger on 'community marketing', 'Reddit marketing', 'seeding plan', 'post in groups', 'community strategy', 'forum marketing', or 'Discord and Slack communities'.
.claude/skills/minhnv0807-38-community-seeding-global/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 8% | 0% |
| case-03 | ✗→✓ | ▲ Improved | 12% | 0% |
| case-11 | ✗→✓ | ▲ Improved | 166% | 0% |
| case-15 | ✗→✓ | ▲ Improved | 128% | 0% |
| case-16 | ✗→✓ | ▲ Improved | 94% | 0% |
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.
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:
Selection criteria:
| Criterion | Threshold | |-----------|-----------| | Size | Large enough to matter, small enough to be read — for niche B2B, 3,000 engaged members beats 300,000 dormant ones | | Activity | Daily posts with real comment threads, not a wall of unanswered links | | Rules | Self-promotion permitted in some form (dedicated thread, flair, tenure gate) — record the exact rule text | | Moderation | Active mods. Well-moderated communities are safer to invest in than unmoderated ones | | Audience fit | Members 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.
Each participant needs:
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.
Four post types, each written in full at 150-300 words, in a real person's voice rather than a brand voice:
| Type | Purpose | Brand mention rule | |------|---------|--------------------| | 1. Genuine question / research post | Learn from the community, surface demand language | No brand mention at all | | 2. Expertise share / teardown | Give real, specific value; earn recognition | Affiliation stated up front; product mentioned only if it is genuinely the answer | | 3. Answering an existing thread | Help someone who already asked | Disclose the connection in the same comment, in plain words | | 4. Customer story amplification | Real social proof | Written 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:
| Metric | How to capture | |--------|----------------| | Post reach and engagement | Native post stats per community; screenshot where no export exists | | Inbound DMs and mentions | Ask "how did you hear about us" at first contact; log the community | | Traffic | UTM per community, only where links are allowed by the rules | | Leads and revenue | CRM source field set to the community name | | Removals, warnings, bans | Log every one with the rule cited — this is the risk signal that decides whether to keep investing in that community | | Sentiment | Track how the brand is spoken about unprompted, via 15-social-listening-global |
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 | |------|-----------------|--------------|----------| | | | | |
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.| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→pass | 53,854 | 42,328 | -21% | 1 | 1 | 0% | 8,319 | 9,003 | +8% | 0 | 0 | — |
case-02 | fail→fail | 51,754 | 37,391 | -28% | 1 | 1 | 0% | 8,281 | 8,697 | +5% | 0 | 0 | — |
case-03 | fail→pass | 52,312 | 40,863 | -22% | 1 | 1 | 0% | 8,286 | 9,253 | +12% | 0 | 0 | — |
case-04 | fail→fail | 18,777 | 26,880 | +43% | 1 | 1 | 0% | 3,092 | 6,141 | +99% | 0 | 0 | — |
case-05 | fail→fail | 11,808 | 20,930 | +77% | 1 | 1 | 0% | 2,030 | 6,344 | +213% | 0 | 0 | — |
case-21 | pass→pass | 13,189 | 5,904 | -55% | 1 | 1 | 0% | 2,107 | 3,647 | +73% | 0 | 0 | — |
case-06 | fail→fail | 21,197 | 26,626 | +26% | 1 | 1 | 0% | 3,755 | 7,397 | +97% | 0 | 0 | — |
case-07 | pass→pass | 18,955 | 30,663 | +62% | 1 | 1 | 0% | 3,146 | 7,701 | +145% | 0 | 0 | — |
case-08 | pass→pass | 16,176 | 24,808 | +53% | 1 | 1 | 0% | 2,441 | 6,973 | +186% | 0 | 0 | — |
case-09 | pass→pass | 12,300 | 11,281 | -8% | 1 | 1 | 0% | 1,868 | 4,324 | +131% | 0 | 0 | — |
case-10 | pass→pass | 16,674 | 12,565 | -25% | 1 | 1 | 0% | 2,513 | 4,573 | +82% | 0 | 0 | — |
case-11 | fail→pass | 11,402 | 12,339 | +8% | 1 | 1 | 0% | 1,732 | 4,602 | +166% | 0 | 0 | — |
case-12 | pass→pass | 10,710 | 6,945 | -35% | 1 | 1 | 0% | 1,586 | 3,758 | +137% | 0 | 0 | — |
case-13 | pass→pass | 15,262 | 12,215 | -20% | 1 | 1 | 0% | 2,221 | 4,516 | +103% | 0 | 0 | — |
case-14 | pass→pass | 13,926 | 11,244 | -19% | 1 | 1 | 0% | 2,314 | 4,326 | +87% | 0 | 0 | — |
case-15 | fail→pass | 12,644 | 11,748 | -7% | 1 | 1 | 0% | 1,993 | 4,541 | +128% | 0 | 0 | — |
case-16 | fail→pass | 13,730 | 13,306 | -3% | 1 | 1 | 0% | 2,378 | 4,604 | +94% | 0 | 0 | — |
case-17 | pass→pass | 12,776 | 9,547 | -25% | 1 | 1 | 0% | 1,998 | 4,135 | +107% | 0 | 0 | — |
case-18 | fail→pass | 12,049 | 9,653 | -20% | 1 | 1 | 0% | 1,860 | 4,094 | +120% | 0 | 0 | — |
case-19 | pass→pass | 13,246 | 18,551 | +40% | 1 | 1 | 0% | 2,216 | 5,525 | +149% | 0 | 0 | — |
case-20 | fail→pass | 16,741 | 12,484 | -25% | 1 | 1 | 0% | 2,687 | 4,701 | +75% | 0 | 0 | — |
case-22 | pass→pass | 14,958 | 20,010 | +34% | 1 | 1 | 0% | 2,519 | 5,896 | +134% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +32 percentage points is the difference between those two pass rates over the 22 comparable cases.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.