Agent skill · Content & Marketing

community-moderation-policy

Write a fair, enforceable community moderation policy. Use when standing up or overhauling moderation for a forum, Discord, Slack, subreddit, or any user community. Produces a clear code of conduct with examples, a graduated enforcement ladder tied to specific triggers, an appeals process, moderator guidelines, and the handling for the severe cases (threats, doxxing, brigading) that need immediate action. Governs member conduct in a user community — distinct from [[community-management-playbook]], which manages a brand's own social-media channels (comments, DMs, tone, response templates).

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill community-moderation-policy --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/community-moderation-policy/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Community Moderation Policy Skill A moderation policy fails when it's vague ("be respectful") or applied inconsistently — members can't predict what's allowed, and mods burn out making judgment calls with no backing. This skill writes a policy that is *enforceable*: concrete rules with examples, a ladder that matches consequence to behavior, and the process that makes enforcement feel fair even to the person on the receiving end. ## Working from a brief Given the community (platform, size, purpose, audience), **write the full policy** — tune severity and tone to the space (a professional Slack ≠ a gaming Discord). Keep the public-facing rules short and human; put the operational detail in the moderator guidelines. ## Required Inputs Ask for (if not provided, else infer and label the assumption): - **The community** — platform, rough size, purpose, and audience norms - **The values / what "good" looks like** here, and the behaviors you most want to prevent - **Team** — how many moderators, volunteer or staff, tools available - **Legal/brand constraints** — platform ToS, regulated topics, company brand line ## Output Format ### Code of conduct (public-facing) Short, plain, and spec

What's inside
Steps it walks through
  1. Working from a brief
  2. Required Inputs
  3. Output Format
  4. Code of conduct (public-facing)
  5. Enforcement ladder
  6. Appeals process
  7. Moderator guidelines (internal)
  8. Quality Checks
  9. Anti-Patterns
More from pm-claude-skills
All skills →
About this skill
What does the community-moderation-policy skill do?

Write a fair, enforceable community moderation policy. Use when standing up or overhauling moderation for a forum, Discord, Slack, subreddit, or any user community. Produces a clear code of conduct with examples, a graduated enforcement ladder tied to specific triggers, an appeals process, moderator guidelines, and the handling for the severe cases (threats, doxxing, brigading) that need immediate action. Governs member conduct in a user community — distinct from [[community-management-playbook]], which manages a brand's own social-media channels (comments, DMs, tone, response templates).

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill community-moderation-policy --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going