# Community Moderation Brief

> Prepare review-only moderation and escalation briefs for creator communities. Use when Codex is asked to review comments, DMs, member posts, Discord or community issues, potential rule violations, harassment, spam, inflammatory threads, removal questions, response options, reviewer notes, or moderation boundary decisions for a creator, influencer, manager, or community team.

- Skill: `gabrielmoreira/community-moderation-brief` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add gabrielmoreira/community-moderation-brief`
- Raw SKILL.md: https://api.skillmd.com/api/skills/gabrielmoreira/community-moderation-brief/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: gabrielmoreira (https://skillmd.com/u/gabrielmoreira)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/gabrielmoreira/community-moderation-brief

---


# Community Moderation Brief

## Core Workflow

1. Identify the item, channel, policy or rule context, audience impact,
   visibility, prior action, decision owner, and deadline.
2. Summarize the issue without overstating intent, motive, identity, or rule
   violation.
3. Classify the moderation question: reply, hold, hide, remove, escalate,
   document, educate, or no action.
4. Draft options with rationale, likely tradeoffs, missing context, and required
   approvals.
5. Route legal, safety, sponsor, customer support, platform policy, privacy,
   child safety, harassment, doxxing, and crisis items to a human reviewer.
6. Keep moderation and community systems read-only unless the user approves a
   specific action.

## Decision Guidance

- Use "hold for review" when facts, policy, consent, or severity are unclear.
- Use "reply draft" when a calm, public or private response can resolve the
  issue without implying a policy decision.
- Use "remove or restrict for review" only as a recommendation, not an action.
- Use "escalate" when the item involves safety, legal, platform, sponsor,
  privacy, payments, minors, threats, harassment, or reputational risk.
- Use "document" when a recurring pattern may require a future policy or FAQ.

## Safety Rules

- This is review support, not legal, crisis, platform enforcement, or trust and
  safety advice.
- Do not send replies, remove content, ban users, mute users, approve members,
  change roles, report accounts, or update rules without explicit approval.
- Do not invent policy terms, violations, user intent, private facts, platform
  requirements, screenshots, prior warnings, or relationship history.
- Separate public response drafts, private/internal notes, moderation rationale,
  missing context, and approval owner.

## Deliverable Shape

For a moderation brief, provide:

- Issue summary
- Evidence provided
- Policy or rule context
- Risk classification
- Options and rationale
- Recommended next step
- Missing context
- Review owner
- Approval status

## References

- Read `references/community-moderation-brief-checklist.md` when drafting
  moderation, escalation, or boundary review packets.