Individual skill

community

Use when building or running a persistent two-way community space — Discord, Telegram, Circle: platform choice, structure, onboarding, native→bot→human moderation, rituals, growth loops, health metrics. NOT churn of paying product customers (that is `retention`), NOT broadcast email (that is `newsletter`), NOT one live event (that is `webinar`).

skills/community/SKILL.md

Read pinned source

Source commit d9d6bb338f66cc1e23998585e580a0ea45bbcb82

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Local scripts
Last checked: Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 574
Repository last updated: Nov 9, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
agentic-ai Repository topic
ai-agents Repository topic
ai-coding Repository topic
claude-code Repository topic
cli Repository topic
cline Repository topic
codex Repository topic
coding-assistant Repository topic
cursor Repository topic
community Declared skill tag
discord Declared skill tag
telegram Declared skill tag
moderation Declared skill tag
growth Declared skill tag
rituals Declared skill tag
marketing Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 13,887 bytes
evals/README.mddoc · 995 bytes
evals/cases.yamlasset · 2,843 bytes
references/metrics-and-rituals.mddoc · 3,627 bytes
references/platform-playbooks.mddoc · 4,910 bytes
scripts/verify.shruns · 2,904 bytes

Read excerpt


# community

Run the community like a **product with a job**, not a vanity chat room. The space — a Discord server, a Telegram group+channel, a Circle — is the product. **Onboarding is activation, rituals are the feature, moderation is reliability, and one north-star metric tied to your purpose is the only number that matters.** A room with 5,000 silent members is a failed product, not a big one. Design the system around the conversation, not the conversation itself.

## When NOT to use — route instead

| The ask | Route to |
|---|---|
| Stop *paying customers of a product/SaaS* from churning (win-back, lifecycle, NPS) | `retention` |
| Write the one-to-many broadcast email that nurtures the list | `../newsletter/SKILL.md` |
| Schedule / cross-post public posts across X, LinkedIn, Instagram | `../social-publisher/SKILL.md` |
| Run a single timed live event end-to-end (registration, speakers, replay) | `webinar` |
| Build an automated support desk / ticket triage | `customer-support` |
| Actually code or host the Discord/Telegram bot (gateway, slash handlers) | `whatsapp-telegram`, `automation-flows` |