Skip to main content

afrexai-community-growth-engine

Complete community building, engagement, and monetization system. From zero to thriving community — launch strategy, member engagement loops, content programming, moderation frameworks, growth tactics, monetization models, and health metrics. Works for Discord, Slack, Telegram, Circle, forums, or any platform.

Source facts

Repository
modbender/skill-library-mcp
Last source activity
March 6, 2026 at 18:33
Detected SKILL.md language
English
Stars
12
Forks
3

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
afrexai-community-growth-engine
description
Complete community building, engagement, and monetization system. From zero to thriving community — launch strategy, member engagement loops, content programming, moderation frameworks, growth tactics, monetization models, and health metrics. Works for Discord, Slack, Telegram, Circle, forums, or any platform.
metadata
{"clawdbot":{"emoji":"🏘️","os":["linux","darwin","win32"]}}
# Community Growth Engine 🏘️ Complete 12-phase system for building, growing, and monetizing communities. From launch strategy through engagement loops, moderation, growth tactics, and revenue — everything you need to run a thriving community. **Important:** Community advice, not legal counsel. Verify platform ToS, privacy laws (GDPR/CCPA), and local regulations for your jurisdiction. --- ## Phase 1: Community Strategy & Foundation ### Community Brief ```yaml community_brief: name: "" mission: "" # One sentence: who + what value tagline: "" # 8 words max type: "" # interest | practice | product | action | place target_member: who: "" # Specific person, not "everyone" pain_points: [] # 3-5 problems they have desired_outcome: "" # What transformation do they want? where_now: [] # Where do they currently hang out? willingness_to_pay: "" # free-only | low ($5-20) | mid ($20-100) | high ($100+) anti_members: # Who is NOT welcome (be specific) - "" value_proposition: "" # "The only community where [specific group] can [specific outcome]" differentiator: "" # Why this vs Reddit/Facebook/existing communities? business_model: "" # free | freemium | paid | hybrid revenue_target: "" # Monthly target platform: "" # discord | slack | telegram | circle | forum | other platform_rationale: "" # Why this platform specifically? ``` ### Platform Selection Guide | Platform | Best For | Pros | Cons | Cost | |----------|----------|------|------|------| | Discord | Gaming, tech, creator, large | Free, rich features, bots | Noisy, learning curve | Free | | Slack | Professional, B2B, small-mid | Familiar, threaded | Expensive at scale, history limits (free) | $7.25/user/mo | | Telegram | Crypto, international, quick | Fast, global, bots | Limited structure, spam-prone | Free | | Circle | Course creators, premium | Clean, integrations, paywall | Monthly cost, less sticky | $49+/mo | | Mighty Networks | Coaches, courses + community | All-in-one | Expensive, lock-in | $41+/mo | | Reddit (subreddit) | Discovery, SEO, niche | Massive reach, free | No ownership, algorithm changes | Free | | Geneva | Gen Z, social, casual | Mobile-first, clean | Smaller user base | Free | | Discourse | Long-form, knowledge base | SEO, ownership, self-host | Technical setup, less real-time | Free (self-host) | **Decision tree:** 1. Budget = $0 + tech audience → **Discord** 2. Budget = $0 + professional audience → **Slack** (free tier) or **LinkedIn Group** 3. Need paywall + courses → **Circle** or **Mighty Networks** 4. International/mobile-first → **Telegram** 5. Want SEO + discovery → **Reddit** (owned subreddit) or **Discourse** 6. Want full ownership → **Discourse** (self-hosted) ### Community Type Framework | Type | Definition | Examples | Key Metric | |------|-----------|----------|------------| | Interest | Shared passion | Photography clubs, book clubs | Engagement rate | | Practice | Shared profession | DevOps community, founders group | Knowledge sharing | | Product | Around a product | OpenClaw Discord, Figma community | Support deflection + advocacy | | Action | Shared cause | Climate groups, open source | Contribution rate | | Place | Geographic | City tech scenes, local groups | Event attendance | --- ## Phase 2: Community Architecture ### Channel/Space Structure **Discord example (adapt for your platform):** ``` 📌 START HERE #welcome — Auto-message, rules, role select #introduce-yourself — Template: name, role, what you're working on #rules — Community guidelines (link, not wall of text) 💬 GENERAL #general — Main conversation #off-topic — Non-community-topic chat #wins — Celebrate achievements (positive reinforcement loop) 🎓 KNOWLEDGE #resources — Curated links, tools, guides #ask-anything — Q&A (encourage answers from members, not just staff) #tutorials — Member-created guides #[topic-1] — Specific topic channel #[topic-2] — Specific topic channel 🔨 BUILD #show-your-work — Share projects for feedback #accountability — Public goals and check-ins #collabs — Find collaborators 📢 ANNOUNCEMENTS #announcements — Official updates (admin-only post) #events — Upcoming events, AMAs, workshops 🔒 PREMIUM (if applicable) #premium-general — Paid members only #premium-resources — Exclusive content #office-hours — Direct access to experts ``` **Channel rules:** - Start with 5-8 channels max — add more only when existing ones are consistently active - Archive channels with <5 messages/week for 3 consecutive weeks - Every channel needs a clear purpose in its description - Pin the "what this channel is for" message ### Role System ```yaml roles: - name: "New Member" auto_assign: true permissions: "read + post in general channels" visual: "🆕" - name: "Member" earn_criteria: "7 days + 10 messages + intro posted" permissions: "full access to public channels" visual: "✅" - name: "Active Member" earn_criteria: "30 days + 50 messages + helped 3 people" permissions: "member + create threads" visual: "⭐" - name: "Champion" earn_criteria: "90 days + consistent value + nominated by staff" permissions: "active member + moderate threads + beta access" visual: "🏆" - name: "Moderator" earn_criteria: "Champion + invitation" permissions: "full moderation powers" visual: "🛡️" - name: "Admin" earn_criteria: "Core team only" permissions: "everything" visual: "👑" ``` ### Onboarding Flow **0-24 hours (critical window — 70% of members who don't engage in 24h never will):** 1. **Immediate** (auto): Welcome DM with 3 specific actions ``` Welcome to [Community]! 🎉 Here's how to get started: 1. Introduce yourself in #introduce-yourself (use the template pinned there) 2. Check out #resources for our top guides 3. Jump into #general and say hi Pro tip: [one specific valuable thing they can do right now] Questions? Drop them in #ask-anything — someone usually responds within [X] hours. ``` 2. **Within 1 hour** (auto or manual): React to their intro with relevant emoji 3. **Within 4 hours**: A human (mod or champion) replies to their intro with a genuine, specific comment 4. **Day 2-3**: Tag them in a conversation relevant to their interests (from intro) 5. **Day 7**: Check-in DM: "How's it going? Finding what you need?" **Onboarding completion checklist:** - [ ] Posted introduction - [ ] Made first comment in a topic channel - [ ] Reacted to someone else's post - [ ] Received a reply from another member (not staff) - [ ] Accessed one resource --- ## Phase 3: Content Programming & Engagement Loops ### Weekly Content Calendar ```yaml weekly_calendar: monday: name: "Monday Momentum" type: "prompt" description: "Share your #1 goal for the week" channel: "#accountability" engagement_type: "participation" tuesday: name: "Tutorial Tuesday" type: "educational" description: "Member or staff shares a how-to" channel: "#tutorials" engagement_type: "learning" wednesday: name: "Wins Wednesday" type: "celebration" description: "Share something you're proud of this week" channel: "#wins" engagement_type: "positive reinforcement" thursday: name: "AMA / Expert Hour" type: "event" description: "Rotating guest or community expert" channel: "#events" engagement_type: "access" frequency: "bi-weekly" friday: name: "Feedback Friday" type: "peer_review" description: "Share work for constructive feedback" channel: "#show-your-work" engagement_type: "collaboration" weekend: name: "Weekend Reading" type: "curated" description: "Top 3 links from the week" channel: "#resources" engagement_type: "value delivery" ``` ### Engagement Loop Design **The CORE Loop (drives daily engagement):** ``` Trigger → Action → Variable Reward → Investment ``` 1. **Notification trigger**: New question in your area of expertise 2. **Action**: Answer the question 3. **Variable reward**: Social recognition (thanks, reactions, role upgrade) 4. **Investment**: Profile/reputation grows, making future rewards more valuable **7 Engagement Mechanics:** | Mechanic | Description | Example | Frequency | |----------|-------------|---------|-----------| | Prompts | Open-ended questions that invite sharing | "What's your biggest challenge this week?" | Daily | | Challenges | Time-bound goals with public accountability | "30-day shipping challenge" | Monthly | | Showcases | Members share work for feedback | "Show Your Work Friday" | Weekly | | AMAs | Expert access creates FOMO | "AMA with [expert] Thursday 2pm" | Bi-weekly | | Debates | Friendly disagreement drives engagement | "Hot take: [controversial opinion]" | Weekly | | Collaborations | Members work together | "Find a collab partner for [project]" | Monthly | | Celebrations | Public wins reinforce participation | "🎉 [member] just hit [milestone]!" | As earned | ### Conversation Starters That Actually Work **High-response templates:** - "What's one thing you learned this week that surprised you?" - "Hot take: [mild controversy in your niche]. Agree or disagree?" - "If you could only use ONE tool for [topic], what would it be and why?" - "[Before/after] — Share your transformation" - "What's your unpopular opinion about [topic]?" - "Rate your week 1-10 and explain in one sentence" - "Roast my [project/idea/setup] — I want honest feedback" **Low-response patterns to avoid:** - Yes/no questions - "What do you think about [thing]?" (too vague) - Questions requiring expertise most members don't have - Posts that are really announcements disguised as questions --- ## Phase 4: Moderation & Community Health ### Community Guidelines Template ```markdown # [Community Name] Guidelines **Our vibe:** [2-3 words describing the culture — e.g., "helpful, honest, humble"] ## The Basics 1. **Be kind, be specific.** Disagree with ideas, not people. Add context, not just opinions. 2. **No spam, no self-promo** (unless in designated channels). Sharing your work when relevant = cool. Drive-by links = not cool. 3. **Search before asking.** Someone probably answered it. When they didn't, ask away. 4. **Give more than you take.** Answer questions. Share resources. Celebrate others. 5. **Keep it on-topic.** #off-topic exists for a reason. 6. **No hate speech, harassment, or discrimination.** Zero tolerance. One strike. 7. **Protect privacy.** Don't share others' information without consent. ## Enforcement - **Gentle reminder** → **Warning** → **24h mute** → **Permanent ban** - Exception: Hate speech, doxxing, illegal content = immediate ban - Appeals: DM a moderator within 7 days ## Report Issues React with 🚩 or DM a moderator. All reports are confidential. ``` ### Moderation Decision Matrix | Behavior | Severity | First Offense | Second | Third | |----------|----------|---------------|--------|-------| | Off-topic post | Low | Redirect to correct channel | Gentle reminder | Mute 1h | | Self-promotion spam | Medium | Delete + DM warning | 24h mute | 7-day ban | | Heated argument | Medium | Cool-down reminder (public) | Thread lock + DM both | 24h mute | | Misinformation | Medium | Correct publicly (kindly) | Warning DM | 7-day ban | | Harassment | High | Immediate mute + investigate | Permanent ban | — | | Hate speech/slurs | Critical | Immediate ban | — | — | | Doxxing | Critical | Immediate ban + delete content | — | — | | Illegal content | Critical | Immediate ban + report to platform | — | — | ### Moderator Playbook **When someone is being difficult (but not rule-breaking):** 1. Assume good intent first — they might be having a bad day 2. Redirect publicly: "Hey, let's keep this constructive. What specifically would help?" 3. If continuing: DM privately — "I noticed some tension. What's going on?" 4. If still escalating: "Taking a quick break on this thread. Let's revisit in 24h." **When two members are fighting:** 1. Don't take sides publicly 2. Acknowledge both perspectives: "You both make valid points" 3. Lock the thread if it's derailing 4. DM both separately to de-escalate 5. If recurring: mediated conversation or separate them **Moderator burnout prevention:** - Rotate on-call moderators (never one person 24/7) - Maximum 2-hour active moderation shifts - Monthly moderator check-in: "How are you doing?" - Clear escalation path — mods shouldn't handle everything alone - Celebrate moderator contributions publicly --- ## Phase 5: Growth Engine ### The Growth Flywheel ``` Content creates value → Value attracts members → Members create content → Repeat ``` ### 12 Growth Tactics (Ranked by Effort/Impact) | Tactic | Effort | Impact | Best For | |--------|--------|--------|----------| | 1. SEO content → community | Medium | High | Long-term discovery | | 2. Cross-promotion with adjacent communities | Low | High | Quick growth | | 3. Guest AMAs | Low | Medium | Authority + reach | | 4. Member referral program | Medium | High | Quality growth | | 5. Social proof posts | Low | Medium | Conversion | | 6. Free resources with community CTA | Medium | High | Lead gen | | 7. Twitter/LinkedIn threads → community | Low | Medium | Audience funnel | | 8. Podcast/YouTube → community | High | High | Authority + funnel | | 9. Challenges (public + invite friends) | Medium | Medium | Viral loops |
View on GitHub
This SKILL.md is very large, so SkillsMP previews the first section here. View on GitHub