community-builder
Expert community-led growth and community management guidance. Use when building developer communities, Discord/Slack communities, online communities, managing community platforms, designing member onboarding, creating engagement programs, running ambassador programs, measuring community health, setting up moderation systems, or implementing DevRel strategies. Use for community-led growth, member activation, user-generated content programs, and community governance.
What this skill does
# Community Builder Expert guidance for building, growing, and nurturing thriving online communities — from platform selection to engagement programs to community-led growth strategies. ## Philosophy Great communities are built on three pillars: 1. **Shared purpose** — Members need a reason bigger than the product 2. **Genuine connection** — People stay for people, not features 3. **Member empowerment** — The best communities run themselves ## How This Skill Works When invoked, apply the guidelines in `rules/` organized by: - `strategy-*` — Community-led growth, positioning, and strategic planning - `platform-*` — Discord, Slack, Circle, and platform selection - `onboarding-*` — Member welcome flows and activation - `engagement-*` — Programs, rituals, and recurring activities - `content-*` — User-generated content and content programs - `programs-*` — Ambassador, champion, and super-user programs - `metrics-*` — Community health and analytics - `moderation-*` — Governance, moderation, and conflict resolution - `devrel-*` — Developer relations and technical community building ## Core Frameworks ### The Community Flywheel ``` ┌─────────────────────────────────────────────────────────────┐ │ │ │ ┌──────────┐ ┌──────────┐ ┌──────────┐ │ │ │ ATTRACT │───▶│ ACTIVATE │───▶│ ENGAGE │ │ │ │ (Reach) │ │ (Value) │ │ (Habit) │ │ │ └──────────┘ └──────────┘ └──────────┘ │ │ ▲ │ │ │ │ ┌──────────┐ │ │ │ │ │ ADVOCATE │ │ │ │ └──────────│ (Amplify)│◀─────────┘ │ │ └──────────┘ │ │ │ └─────────────────────────────────────────────────────────────┘ ``` ### Community Maturity Model | Stage | Characteristics | Focus | |-------|-----------------|-------| | **Nascent** | Founder-led, <100 members | 1:1 conversations, manual everything | | **Growing** | Early champions emerge, 100-1,000 | Systems, rituals, first programs | | **Scaling** | Self-sustaining activity, 1,000-10,000 | Governance, moderation, delegation | | **Mature** | Community-led initiatives, 10,000+ | Platform, sub-communities, ecosystem | ### Member Journey Stages | Stage | Goal | Key Metric | |-------|------|------------| | **Lurker** | First interaction | Post/reply count | | **Newcomer** | Find value, connect | Retention D7 | | **Regular** | Form habits, contribute | Weekly active | | **Champion** | Lead initiatives | Content created | | **Ambassador** | Represent externally | Referrals, reach | ### The 1-9-90 Rule In most communities: - **1%** create content (Creators) - **9%** engage with content (Contributors) - **90%** consume content (Lurkers) Goal: Move people up the engagement ladder, not force everyone to create. ### Community vs Audience | Dimension | Audience | Community | |-----------|----------|-----------| | **Direction** | One to many | Many to many | | **Value** | From creator | From each other | | **Ownership** | Creator owns | Members co-own | | **Content** | Creator produces | Members produce | | **Retention** | Content-dependent | Relationship-dependent | | **Scalability** | Linear | Network effects | ## Platform Comparison at a Glance | Platform | Best For | Key Strength | Key Weakness | |----------|----------|--------------|--------------| | **Discord** | Gaming, dev, real-time | Rich features, free | Overwhelming UX | | **Slack** | Professional, B2B | Familiar, searchable | Expensive at scale | | **Circle** | Courses, creators | Clean UX, courses | Less real-time | | **Discourse** | Long-form, async | SEO, knowledge base | Old-school feel | | **GitHub Discussions** | Open source, devs | Code integration | Limited features | | **Reddit** | Public discovery | SEO, scale | Less control | ## Key Metrics Overview | Category | Metrics | |----------|---------| | **Growth** | New members, referral rate, churn rate | | **Engagement** | DAU/MAU, posts per member, response time | | **Health** | Sentiment, helpful answers, retention | | **Value** | NPS, support deflection, product influence | ## Community-Led Growth (CLG) Quick Reference | Motion | Description | Best For | |--------|-------------|----------| | **Community-Assisted** | Community supports product users | Support deflection | | **Community-Qualified** | Leads emerge from community | B2B, enterprise | | **Community-Distributed** | Growth through member networks | Viral products | | **Community-Created** | Members build on platform | Platforms, APIs | ## Engagement Program Types | Program | Frequency | Goal | |---------|-----------|------| | **Office Hours** | Weekly | Direct access, Q&A | | **Show & Tell** | Weekly/Monthly | Member showcases | | **AMAs** | Monthly | Expert access | | **Challenges** | Monthly/Quarterly | Activation, content | | **Conferences** | Annual | Milestone, celebration | ## Anti-Patterns - **Build it and they will come** — Communities require constant nurturing, especially early - **Metrics over meaning** — Vanity metrics don't equal healthy community - **Over-engineering early** — Start simple, add complexity as needed - **Ignoring lurkers** — 90% of your community provides value by consuming - **Founder absence** — Early communities need visible leadership - **Feature obsession** — People join for people, not features - **Forced engagement** — Authentic connection beats gamification - **One-size-fits-all** — Different member types need different experiences - **Scaling too fast** — Growth without engagement destroys community - **Neglecting moderation** — One bad actor can poison the well
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".