Site Reliability

Use when defining SLOs and error budgets, reducing toil, planning capacity, improving on-call, running postmortems, or designing safe progressive delivery; connect reliability targets to user journeys and explicit evidence.

9 stars 3 forksFinance & Crypto

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sandbaseai/workbuddy-skill --skill site-reliability
Manual install
git clone --depth 1 https://github.com/sandbaseai/workbuddy-skill.git /tmp/workbuddy-skill
mkdir -p ~/.claude/skills
cp -r /tmp/workbuddy-skill/skills/site-reliability ~/.claude/skills/site-reliability

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Site Reliability Engineering

Use this skill to make reliability a measurable engineering practice rather than an aspiration. Start with user journeys and business impact, then define signals, targets, ownership, response, and learning. Reliability is a trade-off with cost, speed, features, security, and recovery—not a promise of 100% uptime.

Do not set arbitrary “number of nines” targets, page on symptoms without an SLO, freeze all delivery without an explicit budget policy, or run load/chaos experiments against production without authorization, abort thresholds, and recovery evidence.

## Define the reliability contract

For each important journey document:

- user action, criticality, dependency graph, eligible population, and exclusions;
- SLI formula, event source, sampling, aggregation, freshness, and data-quality checks;
- SLO target and rolling window, external SLA relationship, owner, review date, and error budget;
- alert thresholds, page/ticket policy, escalation, dashboard, runbook, and authorized response;
- cost, latency, correctness, durability, privacy, and availability trade-offs.

Choose SLIs that represent user outcomes, not only infrastructure health. Typical signals include availability, latency, freshness, correctness, durability, and successful completion. Make denominators explicit and handle retries, cancellations, client errors, maintenance, dependency failures, and partial outages consistently.
Read the full skill on GitHub

Details

Skill name
site-reliability
Path
skills/site-reliability/SKILL.md
License
MIT
Repo updated
8 September 2026

FAQ

What does the Site Reliability skill do?

Use when defining SLOs and error budgets, reducing toil, planning capacity, improving on-call, running postmortems, or designing safe progressive delivery; connect reliability targets to user journeys and explicit evidence.

How do I install the Site Reliability skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add sandbaseai/workbuddy-skill --skill site-reliability. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Site Reliability popular?

It lives in sandbaseai/workbuddy-skill, which has 9 GitHub stars and 3 forks.

Related skills

Browse the most popular Claude skills, all finance & crypto skills, or write your own with the skills generator.