sre-practices
SLIs/SLOs/SLAs, error budgets, incident response, postmortems, and reliability patterns
Profile →npx skills add cosmicstack-labs/mercury-agent-skills --skill sre-practices --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# SRE Practices Apply Site Reliability Engineering principles. ## Service Level Concepts | Term | Definition | Example | |------|------------|---------| | SLI | Measured metric | Request latency p95 < 500ms | | SLO | Target threshold for SLI | 99.9% of requests < 500ms | | SLA | Contractual commitment (usually looser than SLO) | 99.5% uptime | ### Choosing SLOs - Pick metrics users actually care about - Start with availability + latency + durability - Tighten SLOs over time as reliability improves - Don't over-constrain (cost/effort vs. benefit) ## Error Budgets ``` Error Budget = 100% - SLO Example: 99.9% SLO → 0.1% error budget = ~8.7 hours/month ``` ### How Error Budgets Work - If error budget remaining → can deploy new features - If error budget exhausted → freeze deployments, focus on reliability - Error budget burn rate alerts trigger incident response - Balance innovation velocity with system stability ## Incident Response ### Severity Levels | Level | Definition | Response | |-------|-----------|----------| | SEV1 | System down, affecting many users | Immediate, all hands | | SEV2 | Degraded but operational | 30min response | | SEV3 | Minor issue, workaround exists | Next b
- Service Level Concepts
- Choosing SLOs
- Error Budgets
- How Error Budgets Work
- Incident Response
- Severity Levels
- Incident Command System
- Postmortem Culture
- Reliability Patterns
What does the sre-practices skill do?
SLIs/SLOs/SLAs, error budgets, incident response, postmortems, and reliability patterns
How do I install it?
Run `npx skills add cosmicstack-labs/mercury-agent-skills --skill sre-practices --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From cosmicstack-labs/mercury-agent-skills, a repository with 364 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.