cs-service-recovery-plan SKILL.md skillA
cs-service-recovery-plan 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-service-recovery-plan@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-service-recovery-plan/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261026.a2f0899, committed Oct 26, 2026
- First version recorded
- Sep 27, 2026
- Size
- 5,578 bytes
- Repository stars
- 51
- License
- a license file GitHub does not identify
Drafts a service recovery plan with an owned-mistake reply, a fix and follow-up plan on two tracks, a gesture within agreed limits and an apology letter. Use for "run cs-service-recovery-plan", "service recovery", "how to apologise to a customer for our mistake", "we promised the wrong delivery date", "apology letter to customer", "make it right with the customer", "goodwill gesture", "we messed up, what do we say", 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
# Service Recovery Plan ## When To Use We made a wrong promise, a late delivery or a billing error, and we must admit it honestly without grovelling or hiding. Use it when one mistake we own needs a reply, a fix with a date, and a follow-up that proves the fix held. The question it answers: what do we say, what do we fix for this customer, and what do we fix so it does not happen to the next one? ## When Not To Use If the customer has filed a formal complaint, run Complaint Handling Procedure so it follows one process. If the customer is still shouting on the line, start with De-escalation Playbook; recovery comes once the contact is calm. ## Inputs - What we promised and what actually happened, with dates. - What the customer has said so far (paste the thread, personal details removed). - Your gesture limits and who approves above them: the decision-rights table from Refund and Exception Policy if you have run it, or whatever limits the team works to today. If you have none of this, I start from the mistake in one sentence, leave the gesture blank for a person to fill, and mark the output as a first draft. ## Approach …
Read the whole file at its exact version.
How to install
mdr add polar-bear-org/claude-skills/cs-service-recovery-plan@sha256:ffed3c3d5ae611f5The 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_2ag4hu6kvtdhqx7w)
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,578 B | A | view · diff |
| git:20260927.63d5f36 | 2026-09-27 | 63d5f36 | 5,530 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 (5578 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_2ag4hu6kvtdhqx7w GET https://markdownregistry.com/api/v1/resolve?ref=polar-bear-org/claude-skills/cs-service-recovery-plan GET https://markdownregistry.com/api/v1/blob/ffed3c3d5ae611f54ace17124361641646a4860e8ef44cef0015fa596f30872c
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.