cs-sla-ola SKILL.md skillA
cs-sla-ola 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-sla-ola@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-sla-ola/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261026.a2f0899, committed Oct 26, 2026
- First version recorded
- Sep 27, 2026
- Size
- 5,200 bytes
- Repository stars
- 51
- License
- a license file GitHub does not identify
Drafts an SLA and OLA agreement for a support desk, with customer targets by priority and channel, internal OLAs with engineering, product and billing, breach rules and a named clock owner at every stage. Use for "run cs-sla-ola", "SLA template", "OLA template", "operational level agreement", "SLA for customer support", "breaches blamed on support", "response time targets", "agreement with engineering on response times", 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
# SLA and OLA Template ## When To Use SLA breaches caused by another team get reported against support. The customer was promised an answer in a set time, the ticket sat with engineering or billing for most of it, and the dashboard shows support missing its target. Use this to answer: what has each team agreed to, and who holds the clock when time runs out. ## When Not To Use If the targets already exist and the problem is how they are reported, use Support Metrics Scorecard. If nobody yet knows where a ticket should go, build the Escalation Matrix first; times without routes have nothing to attach to. ## Inputs - Your escalation matrix or current routing, and the priority levels you use - Any current SLA wording given to customers, and your channels - The teams support depends on (engineering, product, billing, outside suppliers) If you have none of this, I start from a priority list and the teams you name, 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-sla-ola@sha256:c7fcc8590adb70eeThe 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_d6wgl2jkahwbqgvr)
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,200 B | A | view · diff |
| git:20260927.63d5f36 | 2026-09-27 | 63d5f36 | 5,152 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 (5200 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_d6wgl2jkahwbqgvr GET https://markdownregistry.com/api/v1/resolve?ref=polar-bear-org/claude-skills/cs-sla-ola GET https://markdownregistry.com/api/v1/blob/c7fcc8590adb70eea1e33cd433b3fc37fd00a9129dfdb588cf0d127433ed802a
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.