service-level-management skillA
service-level-management is agent-read markdown (skill) from cbrock84/headcount: Defines and manages service levels — setting targets that reflect what customers need, measuring honestly, and handling breaches. Use this to write or negotiate an SLA, decide what to measure and at what threshold, respond to a missed service level, or work out why a service that meets its targets still has unhappy customers..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Service level management A service level is a promise with a number attached. The number is the easy part; choosing what to measure is where these go wrong. ## Measure what the customer feels The characteristic failure is a service meeting every target while customers are angry. It happens when the measure is chosen for availability of data rather than relevance: - **Uptime that excludes degraded operation.** Technically up and unusably slow is down. - **Response time instead of resolution time.** An instant acknowledgment that resolves nothing measures the autoresponder. - **Averages instead of percentiles.** A mean hides the tail, and the tail is who complains. Commit at p95 or p99, not the mean. - **Measurement from inside your own perimeter**, which excludes the part of the path the customer actually traverses. ## Set targets you would fund A target is a spending decision. Each added nine costs disproportionately more than the last, so the question is never "what would be good?" but "what is the gap worth to the customer, and does it exceed what closing it costs?" Set the internal objective tighter than the external commitment. The gap between them is your …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/service-level-management@git:20260916.e72e404mdr add cbrock84/headcount/service-level-management@sha256:c760b923a988888bPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_pdr7l26nsmarwowp)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.e72e404 latest | 2026-09-16 | e72e404 | 3,329 B | A | view · diff |
| git:20260829.2464776 | 2026-08-29 | 2464776 | 2,990 B | A | view · diff |
| git:20260829.42b4a27 | 2026-08-29 | 42b4a27 | 2,991 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 (3329 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
cbrock84/headcount · 1,664 stars · license MIT · pushed 2026-09-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pdr7l26nsmarwowp GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/service-level-management GET https://markdownregistry.com/api/v1/blob/c760b923a988888b3e7d30e47963da596e699ee96244401fab3c24573fe0fd38
Your agent 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.