Agent skill · Design & Presentation

slo-designer

Design Service Level Objectives (SLOs) with SLIs, targets, alerting thresholds, and error budget calculations following Google SRE best practices. Use when defining reliability targets, designing SLOs, calculating error budgets, or establishing service level indicators.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill slo-designer-rjmurillo-ai-agents-2 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 10 KB
Bundled scripts: none
Version: 1.0.0
Path: skills/analysis/slo-designer-rjmurillo-ai-agents-2/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# SLO Designer When this skill activates, you guide users through designing production-ready Service Level Objectives. Your role is to help identify critical user journeys, define measurable SLIs, set appropriate targets, and calculate error budgets. ## Triggers Activate when the user: - `Design SLOs for my service` - `Define reliability targets` - `Calculate error budget` - `Define SLIs for this system` - `What should my availability target be?` ## When to Use Use this skill when: - Defining reliability targets for a new or existing service - Calculating error budgets for capacity planning - Establishing SLIs and alerting thresholds - Stakeholders ask "what should our availability target be?" Use [chaos-experiment](../chaos-experiment/SKILL.md) instead when: - Testing whether the system meets its SLOs through failure injection - Validating resilience mechanisms work as designed Use [threat-modeling](../threat-modeling/SKILL.md) instead when: - Analyzing security threats, not reliability targets ## Core Concepts | Term | Definition | Example | |------|------------|---------| | **SLI** | Service Level Indicator. Metric measuring service quality. | p99 latency, availability % | | **S

What's inside
Steps it walks through
  1. Triggers
  2. When to Use
  3. Core Concepts
  4. Common SLI Categories
  5. Availability
  6. Latency
  7. Throughput
  8. Error Rate
  9. Correctness
  10. Process
  11. Scripts
  12. calculateerrorbudget.py
  13. generateslodocument.py
  14. Question Framework
Ships with 1 file
  • metadata.json
Commands it runs
python3 .claude/skills/slo-designer/scripts/calculate_error_budget.py \
python3 .claude/skills/slo-designer/scripts/generate_slo_document.py \
More from claude-skill-registry
All skills →
About this skill
What does the slo-designer skill do?

Design Service Level Objectives (SLOs) with SLIs, targets, alerting thresholds, and error budget calculations following Google SRE best practices. Use when defining reliability targets, designing SLOs, calculating error budgets, or establishing service level indicators.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill slo-designer-rjmurillo-ai-agents-2 --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 majiayu000/claude-skill-registry, a repository with 534 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.

Keep going