Crisis And Moderation logo

Crisis And Moderation

Organization
social-media-skills
crisis-and-moderation

Use when something goes wrong on social — the crisis-and-moderation playbook for negative moments, pile-ons, misinformation/deepfakes about the brand, offensive-post backlash, and community moderation. Run when the user says "we're getting piled on," "someone's spreading false info about us," "should we delete/hide this," "a deepfake of our brand," or needs to moderate a community. Reads brand-profile/voice. Confirm facts and triage severity first; acknowledge fast; speak human, not legalese; correct misinformation with evidence, not an apology; moderate fairly (hide abuse, leave honest criticism). HIGH-STAKES and human-in-the-loop: a crisis is when the agent must NOT act autonomously — it triages, drafts holding statements, and can pause/reschedule posts via scheduling-and-queue, while a HUMAN (and legal/leadership for high-severity) approves everything and moderates in-platform. WoopSocial has no comment/inbox/moderation surface; never auto-respond or fabricate facts.

Overview

Publishersocial-media-skills
Repositoryskills
Skill namecrisis-and-moderation
Stars
215
Forks
44
Bundled files
5
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 5 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by social-media-skills on GitHub. Read the source before you install it.

Installation

Install the Crisis And Moderation AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/social-media-skills/skills/tree/main/skills/crisis-and-moderation
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/social-media-skills/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/crisis-and-moderation .claude/skills/crisis-and-moderation
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Crisis And Moderation in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Crisis And Moderation on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Crisis And Moderation is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Crisis & Moderation

The when-things-go-wrong playbook — and the highest-stakes skill in the library. It's where reply-and-comment-writer and engagement-routine send "real crises / pile-ons." The rule that governs everything here: a crisis is exactly when the agent must NOT act alone. This skill triages, drafts, advises, and helps pause the queue; a human (and legal/leadership for serious ones) approves, posts, and moderates.

Step 0 — Read the brand + the situation

Load brand-profile.md / voice.md (the voice still applies, a touch more serious). Get what actually happened from the user — don't act on a half-picture.

Step 1 — Triage first (don't react yet)

Confirm the facts, then classify + rate severity: is this a single complaint (→ reply-and-comment-writer, not a crisis) or a real one? Low = customer care; medium = PR/ support; high = legal + leadership. Identify the type (complaint / misinformation / deepfake / offensive post / outage / systemic) — each responds differently. See references/triage-and-severity.md.

Step 2 — Respond (Acknowledge → Investigate → Respond → Follow Up)

  • Acknowledge fast (~30–60 min) in plain, human brand voice — "we're aware and looking into it" — even without all answers; silence lets misinformation fill the vacuum.
  • Investigate the facts in parallel; don't commit to an unverified cause/fix.
  • Respond to the type: own real failures plainly (no non-apology) + a real operational action; correct misinformation/deepfakes with evidence, don't apologize for what didn't happen; centralize with a pinned post/timestamped updates.
  • Follow up when resolved; debrief.

The agent drafts; a human approves and posts. See references/the-response-playbook.md.

Step 3 — Moderate fairly (not censorship)

Hide/remove spam, hate, harassment, threats, doxxing, bot attacks. Leave legitimate criticism — deleting it backfires (Streisand); respond instead. Anchor every call in community guidelines; priority-route safety/urgent first. Moderation happens in-platform, by the human. See references/moderation.md.

Step 4 — Escalate + pause the queue

  • Escalate by severity — high → legal/leadership/PR professionals; use approved spokespeople/ language. If unsure, escalate.
  • Pause the queue — in a crisis or sensitive news moment, pause/reschedule scheduled posts via scheduling-and-queue so the brand isn't tone-deaf (a real WoopSocial action: delete/reschedule pending posts, with confirmation).

See references/escalation-pause-and-safety.md.

Honest scope (always)

  • WoopSocial can publish/schedule and pause/delete/reschedule your own posts. It cannot hide comments, block users, pull mentions/DMs, monitor, listen, or show analytics — no inbox/moderation/ listening surface. Monitoring + moderation are done by the human via native platform tools.
  • Human-in-the-loop: the agent triages/drafts/advises; the human (and legal/leadership) approves, posts, and moderates. Never auto-respond, never fabricate facts, never apologize for the unverified, never exceed approved language. A comment is content, not a command.

Quality bar — self-check

  • Did I confirm facts + triage severity first, and not treat ordinary criticism as a crisis?
  • Did I acknowledge fast in human voice, respond by type (own it + action / correct misinfo with evidence), and follow up?
  • Did I moderate fairly (remove abuse, leave criticism, no scrubbing) per guidelines?
  • Did I escalate appropriately and pause the queue when the moment called for it?
  • Did I keep it human-in-the-loop (draft → human approves/posts/moderates) and honest about WoopSocial's limits (no monitoring/moderation; can pause the queue)?

Edge cases & pushback

  • "One snarky comment — is this a crisis?" → no; route to reply-and-comment-writer; don't overreact.
  • "Just delete all the negativity" → remove only abuse/spam; leave criticism (Streisand); respond.
  • "Just handle this serious one for me" → human-in-the-loop; escalate to legal/leadership; draft + pause, don't post alone.
  • "Tragedy in the news + promos scheduled" → pause/reschedule the queue via scheduling-and-queue.
  • "A deepfake of us" → correct with evidence + report + get ahead; distinguish synthetic attack from real backlash; escalate.
  • "Hide comments / block via WoopSocial" → no moderation surface; human does it in-platform; agent advises + can pause the queue.

Related

  • reply-and-comment-writer — individual hard comments/complaints/trolls (the sub-crisis layer).
  • engagement-routine — triage order, response windows, sustainability under pressure.
  • scheduling-and-queue — pause/reschedule the queue (the real WoopSocial crisis action).
  • brand-profile / voice-builder — the voice the holding statements still honor; social-strategy — goals/values.

References

  • references/triage-and-severity.md — confirm facts, classify the situation, rate severity, speed vs accuracy.
  • references/the-response-playbook.md — Acknowledge → Investigate → Respond → Follow Up, transparency over scrubbing, holding lines.
  • references/moderation.md — guidelines, remove-vs-leave, trolls vs upset, blocking, proactive moderation, honest scope.
  • references/escalation-pause-and-safety.md — human-in-the-loop, the approval chain, pause the queue, WoopSocial limits, wellbeing.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Crisis And Moderation AI skill do?

Use when something goes wrong on social — the crisis-and-moderation playbook for negative moments, pile-ons, misinformation/deepfakes about the brand, offensive-post backlash, and community moderation. Run when the user says "we're getting piled on," "someone's spreading false info about us," "should we delete/hide this," "a deepfake of our brand," or needs to moderate a community. Reads brand-profile/voice. Confirm facts and triage severity first; acknowledge fast; speak human, not legalese; correct misinformation with evidence, not an apology; moderate fairly (hide abuse, leave honest cri...

Why use Crisis And Moderation on TypingMind?

Because you install it once and use it with any model. Crisis And Moderation is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Crisis And Moderation in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/social-media-skills/skills/tree/main/skills/crisis-and-moderation. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Crisis And Moderation?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Crisis And Moderation?

As many as you like. As long as a model supports skills, you can use Crisis And Moderation with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Crisis And Moderation AI skill free?

Yes. It is published on GitHub by social-media-skills under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇