agentleFS
koinodkoinod/skills/community-mod-pack/SKILL.md

community-mod-pack

Skill0 starsChanged 6 months agoMITView on GitHub

Assist community moderation with summaries, spam detection suggestions, and draft replies for Discord or Telegram. Use when a user wants moderation help, rule reminders, or daily summaries without automatic enforcement actions.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when the user needs daily or weekly channel summaries.

    line 12
  2. Distinctive:

    Use when the user wants spam or rule-violation signals.

    line 13
  3. Distinctive:

    Use when the user wants draft moderator replies or rule reminders.

    line 14
  4. Distinctive:

    Avoid when the user asks to auto-ban, kick, or delete messages.

    line 17
  5. Distinctive:

    Avoid when the community rules are missing or unclear.

    line 18
  6. Distinctive:

    Avoid when privacy constraints prohibit analysis.

    line 19
  7. Distinctive:

    Avoid making final enforcement decisions.

    line 44
  8. Distinctive:

    Keep outputs in draft form.

    line 45
  9. Distinctive:

    Avoid sharing personal data beyond the moderator context.

    line 49
  10. Distinctive:

    Use read-only access to logs when possible.

    line 53

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Community Mod Pack

Goal

Summarize community activity and surface moderation signals with draft responses only.

Best fit

  • Use when the user needs daily or weekly channel summaries.
  • Use when the user wants spam or rule-violation signals.
  • Use when the user wants draft moderator replies or rule reminders.

Not fit

  • Avoid when the user asks to auto-ban, kick, or delete messages.
  • Avoid when the community rules are missing or unclear.
  • Avoid when privacy constraints prohibit analysis.

Quick orientation

  • references/overview.md for workflow and quality bar.
  • references/auth.md for access and token handling.
  • references/endpoints.md for optional integrations and templates.
  • references/webhooks.md for async event handling.
  • references/ux.md for intake questions and output formats.
  • references/troubleshooting.md for common issues.
  • references/safety.md for safety and privacy guardrails.

Required inputs

  • Channel logs or message exports within the allowed window.
  • Community rules and enforcement preferences.
  • Languages to moderate.
  • Escalation contacts and severity thresholds.

Expected output

  • Activity summary with key topics and notable threads.
  • Flagged messages with reasons and confidence.
  • Draft responses or rule reminders.
  • Suggested follow-up actions for human moderators.

Operational notes

  • Provide confidence and cite the rule that was triggered.
  • Avoid making final enforcement decisions.
  • Keep outputs in draft form.

Security notes

  • Respect privacy and minimize data retention.
  • Avoid sharing personal data beyond the moderator context.

Safe mode

  • Analyze and draft only; no enforcement actions.
  • Use read-only access to logs when possible.

Sensitive ops

  • Muting, banning, deleting messages, or modifying roles is out of scope.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.