本文へ移動
cccskills
無料GitHub で公開

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).

インストール方法を見る

含まれるファイル(1)

  • SKILL.md4.4 KB

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 specific. The core rules stated positively where possible, each with a one-line example of what crosses the line so it's not ambiguous. Cover the usual: harassment, hate speech, spam/self-promo, off-topic, NSFW, illegal content — scoped to this community.

Enforcement ladder

Consequence matched to behavior and repetition:

LevelTriggerActionWho can apply
1first minor / borderlinefriendly warning, edit/removeany mod
2repeat / clear violationformal warning, temp muteany mod
3serious or repeatedtemp ban (e.g. 7 days)senior mod
4severe / incorrigiblepermanent banadmin
Zero-tolerancethreats, doxxing, CSAM, targeted harassmentimmediate ban + reportadmin, no warning

Appeals process

How a member contests an action: where to appeal, who reviews (not the acting mod), the timeline, and what can/can't be overturned. Appeals are what make the ladder feel legitimate.

Moderator guidelines (internal)

  • Consistency — decide by the rule, not the person; document every Level 2+ action.
  • Conflicts — don't moderate a thread you're personally in; hand off.
  • Edge cases — borderline calls, sarcasm/context, brigading and coordinated behavior, when to lock vs remove.
  • Transparency — what's communicated to the member vs. handled quietly; a mod log.
  • Mod wellbeing — rotation for heavy content, escalation for threats to mods.

Quality Checks

  • Every rule is concrete enough to predict a call, with an example of the line
  • The ladder ties specific triggers to specific actions and who may apply them
  • Severe cases (threats, doxxing, CSAM) are zero-tolerance and route to reporting
  • An appeals path exists and is reviewed by someone other than the acting mod
  • Mod guidelines cover consistency, conflicts of interest, and documentation
  • Tone and severity fit this community; it aligns with the platform ToS

Anti-Patterns

  • Vague rules ("don't be a jerk") with no examples — unenforceable and arbitrary-feeling
  • A single "ban" hammer with no graduated steps for minor issues
  • Inconsistent enforcement by mood or by who the member is
  • No appeals process (every action feels final and unjust)
  • Unwritten rules enforced as if everyone knew them
  • Warning-laddering genuine threats or doxxing instead of acting immediately

Example Trigger Phrases

  • "Write moderation rules for our Discord."
  • "Write a code of conduct for our forum."
  • "Overhaul moderation for our subreddit."
  • "Set up an enforcement ladder for our community."

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

mohitagw15856 のスキルをすべて見る

このスキルの問題を報告する