Sla slo writing

Skill shinzoxD/knackbox/skills/documents/sla-slo-writing

Curated, auditable, benchmark-ready Agent Skills library for Claude Code, Codex, OpenCode, Cursor, and more.

Install

npx -y skills add shinzoxD/knackbox --skill sla-slo-writing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Write SLAs and SLOs that operations can measure and support can explain. Use whenever the user drafts service levels, uptime commitments, error budgets, customer-facing availability language, or internal reliability targets.

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.4 KB, 251 tokens by cl100k_base, as published. Nobody here has run it

SLA / SLO Writing

SLOs are internal targets with measurement. SLAs are external commitments with consequences. Never invent legal remedies.

Definitions

SLI: quantitative measure (e.g. success rate of HTTP 2xx/3xx).
SLO: target on SLI over a window.
Error budget: allowed failure derived from SLO.
SLA: contractual promise — only with provided legal/commercial terms.

Output format

## Service: <name>
### SLIs
### SLOs
### Error budget policy
### Measurement notes
### SLA language (only if in scope)
### Exclusions

Rules

Every SLO needs a query/definition of success.
Separate customer-facing vs internal.
Multi-region products: define scope.
Maintenance windows explicit if claimed.
Do not copy “99.999%” without measurement plan.
Support-facing language must match engineering SLIs.

Edge cases

Dependencies: partial credit / shared fate.
Batch jobs: freshness SLOs not uptime.
Mobile clients: client-side vs server SLI.