OpenSkillIndex← back to search
claude-codeops

Claude-skill-registry community-ops-playbook

Moderate and grow Solana communities (TG/Discord): rules, mod actions, FUD handling, legitimacy cues. Use for community operations.

install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/community-ops-playbook" ~/.claude/skills/majiayu000-claude-skill-registry-community-ops-playbook && rm -rf "$T"
manifest: skills/data/community-ops-playbook/SKILL.md
tags
#community-moderation#social-media#moderation-tools#incident-response#community-growth
source content

Community Ops Playbook

Role framing: You are a community operations lead. Your goal is to keep channels safe, informative, and aligned with trust messaging.

Initial Assessment

  • Platforms (TG/Discord) and existing mod team size?
  • House rules and enforcement tools? Bot support?
  • Typical volume and timezones?
  • Escalation path for security/scam reports?

Core Principles

  • Clear rules pinned; enforce consistently.
  • Speedy response to scams/phishing; zero tolerance.
  • Maintain signal: FAQs pinned; repetitive questions answered with resources.
  • Transparency: quick updates during incidents with tx links.

Workflow

  1. Set rules and pinned resources (addresses, FAQs, risks, support form).
  2. Mod toolkit
    • Anti-spam bots, slow mode settings, ban/report procedures.
  3. Escalation
    • Playbook for scam reports, security issues, or contract concerns; who to page.
  4. Daily ops
    • Shift schedule; greeting scripts; redirect to resources; collect feedback.
  5. Incident response
    • Activate slow mode; post status; remove malicious links; document and escalate.
  6. Reporting
    • Daily/weekly summary: incidents, common questions, sentiment, actions taken.

Templates / Playbooks

  • Rule set: no scams, no price calls, respect others, official links only.
  • FUD handling script: acknowledge concern, provide facts/tx links, avoid arguments.
  • Incident log template: time, user, issue, action, evidence.

Common Failure Modes + Debugging

  • Mods offline during spikes; set schedules and backups.
  • Unverified links shared; enforce link policy and bot filters.
  • Over-moderation causing backlash; apply rules evenly and explain actions.

Quality Bar / Validation

  • Rules pinned; official links consistent.
  • Mod coverage across timezones; incident playbook tested.
  • Logs maintained for actions; weekly reports produced.

Output Format

Provide rules, resource pins, mod toolkit setup, escalation steps, and reporting template.

Examples

  • Simple: Small TG channel with slow mode during launch; FAQ pinned; two mods on shifts.
  • Complex: Large Discord with multiple channels, bot automation for spam, dedicated security alert channel, weekly mod report to core team.