Today's Agent Skill: Business Crisis Communication Statement Drafter
What It Does
When something goes wrong with your business — a service outage, a product recall, a data issue, a public complaint that goes viral, or a local news story — how quickly and professionally you communicate in the first hour determines whether you contain the situation or let it spiral. Most small business owners freeze or say too much in the wrong places, making a manageable situation worse.
How It Works
The agent takes a description of what happened, who is affected, and what you're doing about it, then drafts a crisis communication statement calibrated for the specific situation and audience. It produces a version for email to affected customers, a version for your website or Google Business profile, and brief social media language — all consistent in message but appropriate for each channel's tone and character limits.
How to Deploy It
Run this skill in Claude Code, Gemini CLI, Cursor, or Windsurf as soon as a crisis situation becomes clear — ideally within 30 minutes of the triggering event. Communication speed matters in a crisis; a statement published two hours after the event is far more effective than a polished one published two days later. After posting, monitor replies and comments for 24 hours and respond to individual concerns directly.
SKILL.md — Ready to Deploy
## Description
Drafts a multi-channel crisis communication statement for a small business — including an email to affected customers, website/Google Business profile language, and brief social media text — that acknowledges the situation, explains what is being done, and preserves customer trust without over-admitting liability.
## Trigger
Invoke when the user says "help me write a statement about what happened," "I need to communicate a problem to my customers," "we had a service outage and need to say something," "a bad review is going viral and I need to respond publicly," or describes any situation where customers need to be informed of a problem or disruption.
## Input
- What happened: a plain-language description of the issue (service outage, incorrect charge, product defect, data problem, delay, etc.)
- Who is affected: all customers, a specific group, customers in a date range, or customers who purchased a specific product
- What you are doing about it: the concrete steps being taken to resolve it
- What affected customers can expect: refund, replacement, discount, timeline for fix
- Current status: still happening, resolved, partially resolved, or under investigation
- BCopy the full SKILL.md and drop it into your agent's skills directory to activate this skill.