本文へ移動
cccskills
無料GitHub で公開

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.

インストール方法を見る

含まれるファイル(12)

  • SKILL.md6.9 KB
  • rules/_sections.md1.5 KB
  • rules/content-ugc-programs.md8.2 KB
  • rules/devrel-basics.md10.2 KB
  • rules/engagement-programs-rituals.md8.0 KB
  • rules/metrics-community-health.md12.2 KB
  • rules/moderation-governance.md10.8 KB
  • rules/onboarding-member-activation.md8.3 KB
  • rules/platform-discord-slack-setup.md9.6 KB
  • rules/platform-selection.md8.3 KB
  • rules/programs-ambassador-champion.md9.5 KB
  • rules/strategy-community-led-growth.md9.5 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

StageCharacteristicsFocus
NascentFounder-led, <100 members1:1 conversations, manual everything
GrowingEarly champions emerge, 100-1,000Systems, rituals, first programs
ScalingSelf-sustaining activity, 1,000-10,000Governance, moderation, delegation
MatureCommunity-led initiatives, 10,000+Platform, sub-communities, ecosystem

Member Journey Stages

StageGoalKey Metric
LurkerFirst interactionPost/reply count
NewcomerFind value, connectRetention D7
RegularForm habits, contributeWeekly active
ChampionLead initiativesContent created
AmbassadorRepresent externallyReferrals, 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

DimensionAudienceCommunity
DirectionOne to manyMany to many
ValueFrom creatorFrom each other
OwnershipCreator ownsMembers co-own
ContentCreator producesMembers produce
RetentionContent-dependentRelationship-dependent
ScalabilityLinearNetwork effects

Platform Comparison at a Glance

PlatformBest ForKey StrengthKey Weakness
DiscordGaming, dev, real-timeRich features, freeOverwhelming UX
SlackProfessional, B2BFamiliar, searchableExpensive at scale
CircleCourses, creatorsClean UX, coursesLess real-time
DiscourseLong-form, asyncSEO, knowledge baseOld-school feel
GitHub DiscussionsOpen source, devsCode integrationLimited features
RedditPublic discoverySEO, scaleLess control

Key Metrics Overview

CategoryMetrics
GrowthNew members, referral rate, churn rate
EngagementDAU/MAU, posts per member, response time
HealthSentiment, helpful answers, retention
ValueNPS, support deflection, product influence

Community-Led Growth (CLG) Quick Reference

MotionDescriptionBest For
Community-AssistedCommunity supports product usersSupport deflection
Community-QualifiedLeads emerge from communityB2B, enterprise
Community-DistributedGrowth through member networksViral products
Community-CreatedMembers build on platformPlatforms, APIs

Engagement Program Types

ProgramFrequencyGoal
Office HoursWeeklyDirect access, Q&A
Show & TellWeekly/MonthlyMember showcases
AMAsMonthlyExpert access
ChallengesMonthly/QuarterlyActivation, content
ConferencesAnnualMilestone, 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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Expert full-cycle enterprise sales strategist for B2B SaaS. Use when planning sales strategy, pipeline management, deal progression, account planning, competitive displacement, or territory optimization. Covers multi-threading, executive engagement, champion development, buying committee navigation, and complex deal orchestration. Use for enterprise selling, account expansion, land-and-expand, and quota attainment.

日本語の概要は準備中です。原文の説明を表示しています。

ncklrs/startup-os-skills522026年2月27日 更新

adr

無料

Expert Architecture Decision Record (ADR) creation and lifecycle management based on Olaf Zimmermann's methodology. Use when creating ADRs, reviewing architectural decisions, evaluating decision readiness, writing MADR templates, assessing decision quality, or managing ADR logs. Covers the full lifecycle from readiness (START criteria) through creation, MADR formatting, completion (ECADR criteria), and ongoing maintenance.

日本語の概要は準備中です。原文の説明を表示しています。

ncklrs/startup-os-skills522026年2月27日 更新

Hand off code review to OpenAI Codex CLI. Use when asked to "review code with codex", "codex review", "get a second opinion on code", "review my changes", "review this PR", or when you want AI-powered code review from a different model perspective.

日本語の概要は準備中です。原文の説明を表示しています。

ncklrs/startup-os-skills522026年2月27日 更新

Expert competitive intelligence and strategy guidance for B2B/SaaS companies. Use when conducting competitive research, creating battlecards, analyzing win/loss data, building market landscape maps, positioning against alternatives, handling competitive objections, writing comparison pages, or developing sales enablement for competitive situations. Use for competitive monitoring, feature comparisons, and market intelligence gathering.

日本語の概要は準備中です。原文の説明を表示しています。

ncklrs/startup-os-skills522026年2月27日 更新

Master orchestrator that chains all Remotion video creation skills together in a single automated pipeline. Takes a creative brief and produces a complete, production-ready Remotion video project. Use when starting a new video from scratch, when asked to "create a video", "make a video", "build a complete video", or "video from idea to code".

日本語の概要は準備中です。原文の説明を表示しています。

ncklrs/startup-os-skills522026年2月27日 更新

Strategic Customer Success leadership guidance for CS org design, customer segmentation and tiering (tech touch, low touch, high touch), success metrics and KPIs (NRR, GRR, NPS, CSAT, CES), playbook development, executive stakeholder management, CS technology stack strategy, value realization frameworks, and customer journey mapping. Use when building CS teams, defining customer segments, designing playbooks, measuring success outcomes, or implementing CS platforms.

日本語の概要は準備中です。原文の説明を表示しています。

ncklrs/startup-os-skills522026年2月27日 更新

ncklrs のスキルをすべて見る

このスキルの問題を報告する