mcpField
C
community-governance-review

community-governance-review

github.com/sylphxaiOther141 installsUpdated today
Repository

About community-governance-review

A skill for turning community-governance questions into practical plans and decision artifacts. It helps teams define community roles, norms, moderation, safety, feedback routing, events, and sustainability.

Key features

  1. 01Classify community types and stakeholders
  2. 02Define roles, norms, and moderation steps
  3. 03Plan transparency, events, and incentives
  4. 04Route feedback and set safety practices
  5. 05Create governance and escalation artifacts

Use cases

  1. 01Design governance for a support or open-source community
  2. 02Set moderation roles and escalation paths
  3. 03Plan events and incentives with safety boundaries
  4. 04Create a community health checklist and succession plan

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill community-governance-review

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

Bundled filesagents/openai.yamlreferences/community-governance-patterns.md

Details

From the project README

Community Governance Review

Use this skill to convert a community governance, norms, roles, moderation, escalation, transparency, incentives, events, and sustainability question into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

  1. Identify community purpose, member segments, channels, roles, norms, risks, moderation owner, escalation path, and product feedback boundary.
  2. Read references/community-governance-patterns.md.
  3. Classify community type: support community, creator ecosystem, open-source community, game community, ambassador group, customer council, or marketplace community.
  4. Define governance model, roles, norms, moderation ladder, transparency, event cadence, incentives, feedback routing, safety practices, and succession plan.
  5. Produce governance plan, state machine, decision table, event schema, health checklist, and escalation policy.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not turn unpaid community leaders into hidden support staff without boundaries, recognition, and safety controls.
  • Do not let community feedback become product policy without evidence, representation, and decision ownership.
  • Do not ignore harassment, faction capture, spam, or misinformation because engagement metrics look high.
  • Do not use incentives that reward low-quality posting, brigading, or fake advocacy.

Output format

Community context:
Purpose / roles / channels / health risk:

Community governance plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |

Norms, roles, and incentives:
- <item> -> <policy, metric, edge case, support note>

Escalation and sustainability policy:
- <trigger> -> <action, communication, owner>

Comments

Markdown supported