About content-policy-appeals-review
Content Policy Appeals Review is a skill for turning content moderation and appeals questions into an operational plan. It structures policy, evidence, enforcement, review, and recovery decisions into artifacts with owners, gates, and metrics.
Key features
- 01Map policy and enforcement stages
- 02Define severity and evidence requirements
- 03Set appeal SLAs and reviewer independence
- 04Plan QA, abuse controls, and restoration
- 05Produce decision tables and event schemas
Use cases
- 01Design an appeals process for a platform
- 02Review moderation notices and evidence handling
- 03Set human review and restoration rules
- 04Create moderation QA and reporting plans
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ sylphxai/ skills --skill content-policy-appeals-reviewAfter installing, type/content-policy-appeals-reviewin Claude Code to confirm it loaded.
Bundled filesagents/openai.yamlreferences/content-policy-appeals-patterns.md
Details
From the project READMEContent Policy Appeals Review
Use this skill to convert a content policy, enforcement, appeals, evidence, transparency, moderation QA, and creator/user trust question into a concrete artifact with owners, gates, metrics, and recovery paths.
Workflow
- Identify content surface, policy domain, user/creator stakes, harm model, jurisdiction/platform constraints, enforcement tools, and appeal promise.
- Read
references/content-policy-appeals-patterns.md. - Separate policy definition, detection, review, enforcement, notification, appeal, reversal, repeat-offender, and transparency reporting.
- Define severity ladder, evidence package, notice copy, appeal SLA, reviewer independence, QA sampling, abuse controls, and restoration path.
- Produce policy operations plan, state machine, decision table, event schema, appeal checklist, and edge-case review cadence.
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 enforce vague policy without examples, severity ladder, notice, and appeal path.
- Do not expose reporters, private evidence, or sensitive enforcement signals unnecessarily.
- Do not let automation permanently remove high-stakes content without human review or appeal where appropriate.
- Do not restore content without considering downstream notifications, ranking, monetization, and trust state.
Output format
Policy context:
Surface / harm / stakes / appeal promise:
Policy and appeals plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |
Rules and enforcement ladder:
- <item> -> <policy, metric, edge case, support note>
Appeal and restoration path:
- <trigger> -> <action, communication, owner>
Comments
Markdown supported