Incident Status Comms

    1

    Draft honest customer-facing incident updates.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    About this skill

    When your service is broken, your customers need honest, timely, plain-language communication — not internal war-room chatter. This skill is a playbook for writing customer-facing incident notices: the initial alert, mid-incident updates, and the resolution message. It does not decide what to do about the incident; it tells you exactly what to say about it.

    Turn verified facts about an outage, degradation, or bug into clear customer-facing status updates that reduce support load, preserve trust, and avoid the two classic failure modes of incident comms: going silent, or speculating about things you don't know yet. This skill covers COMMUNICATION ONLY. Incident triage, root-cause analysis, and response decisions belong to your incident response workflow (for example, a sev-decision playbook handles decision-making; this skill handles what customers hear).

    • Your service, product, or feature is degraded or down and customers may notice.

    • You need to write a status-page post, in-app banner, or email notice about an incident.

    • Stakeholders keep asking "what do we tell customers?" during an active incident.

    • You need to draft the public resolution message after service is restored.

    • You want to announce a postmortem or follow-up action publicly without admitting liability.

    • For internal war-room decisions: severity calls, escalation, root-cause analysis, rollback vs. hotfix tradeoffs. This skill assumes those decisions are already being made elsewhere.

    • As an incident detector. This skill drafts messages; it cannot tell you an incident is happening, monitor uptime, or verify system state. Only use facts verified by your monitoring or engineering team.

    • For legal or regulatory breach-notification obligations (e.g., data-breach disclosure). Those have legal requirements this playbook does not cover; involve legal counsel.

    • For marketing the postmortem. The postmortem teaser here is a trust-building follow-up, not content marketing.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Permissions

    No special permissions declared or detected

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    Draft honest customer-facing incident updates.

    This skill uses the open SKILL.md standard. Use it through an MCP-compatible agent connected to Agensi, and check the compatibility information on this page for confirmed agents and required capabilities.

    Connect your AI agent to Agensi through MCP, then ask it to use incident-status-comms on your task. Your agent loads the latest approved version each time. Paid skills require a purchase or active subscription. Skill files are not available for download; your licence does not allow you to save, copy or export any part of a skill.

    New in DevOps & Cloud