Individual skill
community-ops
Use to orchestrate workflows, tooling, and automation for community programs.
plugins/community-orchestration/skills/community-ops/SKILL.md
Source commit 78e0419f4440bcb43bc80127e174ecf5adef1753
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- 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)
- 438
- Repository last updated
- Apr 3, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering 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 · 1,278 bytes
Read excerpt
# 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.
