cs-incident-communication SKILL.md skillA
cs-incident-communication from polar-bear-org/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add polar-bear-org/claude-skills/cs-incident-communication@git:20261026.a2f0899Pins git:20261026.a2f0899 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- polar-bear-org/claude-skills
- Path
packs/ai-for-customer-service-pack/skills/cs-incident-communication/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261026.a2f0899, committed Oct 26, 2026
- First version recorded
- Sep 27, 2026
- Size
- 5,100 bytes
- Repository stars
- 51
- License
- a license file GitHub does not identify
Writes an incident communication plan for an outage, with a first notice, an update cadence that always gives the next-update time, no-ETA wording, an all-clear, a blameless closing note and an agent brief. Use for "run cs-incident-communication", "incident communication plan", "outage update to customers", "status page update", "what to tell customers with no ETA", "agent brief during an outage", "incident closing note", part of the AI for Customer Service Pack by 90n.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Incident Communication Plan ## When To Use An outage with no ETA and every customer wants an answer now. The queue fills in minutes, agents improvise different answers, and someone promises "fixed within the hour" that nobody can keep. Use this to answer: what do we say, where, how often, and who approves it, from the first notice to the closing note. ## When Not To Use If one customer hits one defect, use Bug Report Template; incident communication is for many customers at once. If the change was planned and nothing has failed yet, use Release Readiness Brief. ## Inputs - What is known: symptoms, who is affected, when it started, what is being done - Your channels (status page, email, in-app, social) and which one is primary - Who approves public wording during an incident If you have none of this, I start from a one-line description of the outage and mark every message as a first draft. ## Approach …
Read the whole file at its exact version.
How to install
mdr add polar-bear-org/claude-skills/cs-incident-communication@sha256:c4ba73d358f93a70The line at the top of this page pins the label git:20261026.a2f0899, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_adovbbkcsmwxnbmf)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 27, 2026 and Oct 26, 2026, about one every 29 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261026.a2f0899 latest | 2026-10-26 | a2f0899 | 5,100 B | A | view · diff |
| git:20260927.63d5f36 | 2026-09-27 | 63d5f36 | 5,052 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5100 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
polar-bear-org/claude-skills · 51 stars · license a license file GitHub does not identify · pushed 2026-10-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_adovbbkcsmwxnbmf GET https://markdownregistry.com/api/v1/resolve?ref=polar-bear-org/claude-skills/cs-incident-communication GET https://markdownregistry.com/api/v1/blob/c4ba73d358f93a70db840ef0525a17ee9b678644c48a4e83d3cd499ed62a5424
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.