smithery.ai

community-ops

Use to orchestrate workflows, tooling, and automation for community programs.

First seen Apr 19, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,278 B
  • docs SUMMARY.md 98 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

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.