cs-complaint-handling-procedure SKILL.md skillA
cs-complaint-handling-procedure 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-complaint-handling-procedure@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-complaint-handling-procedure/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261026.a2f0899, committed Oct 26, 2026
- First version recorded
- Sep 27, 2026
- Size
- 5,652 bytes
- Repository stars
- 51
- License
- a license file GitHub does not identify
Writes a complaint handling procedure with receive, acknowledge, investigate, answer, close and learn steps, acknowledgement and outcome letters and a complaint log. Use for "run cs-complaint-handling-procedure", "complaint handling procedure", "how to handle customer complaints", "complaints process", "formal complaint response letter", "complaint log template", "ISO 10002 complaints", "who handles a formal complaint", 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
# Complaint Handling Procedure ## When To Use A formal complaint arrives and the answer depends on who picks it up: one agent replies in an hour, another leaves it for a week, a third forwards it to nobody. Use it to set one procedure every complaint follows, with letters and a log. The question it answers: who owns this complaint, what happens at each step, and how fast? ## When Not To Use For a single mistake we already own and can fix today, Service Recovery Plan is lighter. For routing any hard ticket (not a complaint about us) to the right decider, run Escalation Matrix instead. ## Inputs - How complaints reach you today (channels, forms, addresses) and who handles them. - Two or three recent complaints and how they ended, names removed. - Any time targets you already promise, and any regulator or ombudsman route that applies to you. If you have none of this, I start from the ISO 10002 steps with blank time targets, 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-complaint-handling-procedure@sha256:d1b66e433ff1bae6The 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_slwsth2hwuh3qspv)
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,652 B | A | view · diff |
| git:20260927.63d5f36 | 2026-09-27 | 63d5f36 | 5,604 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 (5652 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_slwsth2hwuh3qspv GET https://markdownregistry.com/api/v1/resolve?ref=polar-bear-org/claude-skills/cs-complaint-handling-procedure GET https://markdownregistry.com/api/v1/blob/d1b66e433ff1bae69e9fa85eb951e9863f8a859b2c940d0ce29f28264ebe3e44
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.