AgentStack
SKILL verified MIT Self-run

Community Moderation Brief

skill-jeremylongworth-source-agentskills-community-moderation-brief · by jeremylongworth-source

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.

No reviews yet
0 installs
6 views
0.0% view→install

Install

$ agentstack add skill-jeremylongworth-source-agentskills-community-moderation-brief

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Community Moderation Brief? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Community Moderation Brief

Core Workflow

  1. Identify the item, channel, policy or rule context, audience impact,

visibility, prior action, decision owner, and deadline.

  1. Summarize the issue without overstating intent, motive, identity, or rule

violation.

  1. Classify the moderation question: reply, hold, hide, remove, escalate,

document, educate, or no action.

  1. Draft options with rationale, likely tradeoffs, missing context, and required

approvals.

  1. Route legal, safety, sponsor, customer support, platform policy, privacy,

child safety, harassment, doxxing, and crisis items to a human reviewer.

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

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.