mcpField
C
community-ops

community-ops

github.com/gtmagentsMarketing & growth42872 installsUpdated 30w ago
Repository

About community-ops

community-ops is a skill for organizing community channels, operations, and moderation processes. It offers a playbook for teams setting up workflows, managing access and schedules, and reviewing operational consistency and compliance.

Key features

  1. 01Channel naming, permissions, integrations, and backup owners
  2. 02Welcome, tagging, escalation, and reporting workflows
  3. 03Moderator rosters and resource management
  4. 04Access, retention, legal, and crisis procedures
  5. 05Launch checklists, shift planners, and automation registry

Use cases

  1. 01Launching a community channel and its operating processes
  2. 02Coordinating moderator coverage and onboarding
  3. 03Reviewing community operations for consistency or compliance

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill community-ops

After installing, type/community-opsin Claude Code to confirm it loaded.

Details

From the project README

Community Operations Playbook Skill

When to Use

  • Standing up new community channels, automation, or tooling.
  • Coordinating moderator schedules, onboarding flows, and partner access.
  • Auditing operations for consistency, compliance, or scale.

Framework

  1. Channel Setup – naming conventions, permissions, integrations, and backup owners.
  2. Workflow Automation – welcome flows, tagging, escalation triggers, and reporting pipelines.
  3. Resource Management – moderator rosters, ambassador kits, and knowledge base updates.
  4. Compliance & Security – access reviews, data retention, legal approvals, and crisis playbooks.
  5. Continuous Improvement – retros, tooling evaluations, and experiment backlog.

Templates

  • Channel launch checklist (config, automation, QA, analytics hooks).
  • Moderator shift planner with coverage heatmap.
  • Automation registry (flow, trigger, owner, status, notes).

Tips

  • Keep SOPs in a shared workspace with version history.
  • Pair with escalation skill to ensure automation ties into incident paths.
  • Review automation logs weekly to catch failures before members notice.

Comments

Markdown supported