slo-implementation
Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting. Use when establishing reliability targets, implementing SRE practices, or measuring service performance.
84
77%
Does it follow best practices?
Impact
92%
1.55xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/observability-monitoring/skills/slo-implementation/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description that clearly identifies its niche in SRE reliability engineering with explicit trigger guidance. Its main weakness is that the 'what' portion could be more specific about concrete actions beyond 'define and implement'—for example, mentioning dashboard creation, burn-rate alerting configuration, or SLO document generation would strengthen specificity.
Suggestions
Expand the capability list with more concrete actions, e.g., 'create SLO dashboards, configure burn-rate alerts, calculate error budget consumption, generate SLO documents' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (SLIs, SLOs, error budgets, alerting) and some actions ('define and implement'), but doesn't list multiple concrete actions in detail—e.g., it doesn't specify what 'implement' entails (dashboards, monitoring configs, burn-rate alerts, etc.). | 2 / 3 |
Completeness | Clearly answers both 'what' (define and implement SLIs/SLOs with error budgets and alerting) and 'when' (explicit 'Use when' clause covering reliability targets, SRE practices, and measuring service performance). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'SLIs', 'SLOs', 'error budgets', 'alerting', 'reliability targets', 'SRE practices', 'service performance'. These cover the main terms a user would naturally use when requesting this kind of work. | 3 / 3 |
Distinctiveness Conflict Risk | The SLI/SLO/error budget domain is a clear niche within SRE. The specific terminology (SLIs, SLOs, error budgets) makes it highly unlikely to conflict with general monitoring, alerting, or performance skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides strong, actionable Prometheus/Grafana configurations for SLO implementation with concrete, executable examples. However, it's overly long for a SKILL.md — much of the detailed configuration could be offloaded to reference files — and it includes generic best practices and conceptual explanations that don't add value for Claude. The workflow could benefit from explicit implementation sequencing with validation steps.
Suggestions
Move the detailed Prometheus recording rules, alerting rules, and dashboard queries into separate reference files, keeping only a concise overview and one representative example in SKILL.md
Remove or drastically trim the 'Best Practices' list, 'When to Use' section, 'SLI/SLO/SLA Hierarchy' diagram, and 'Consider' list — these are generic SRE knowledge Claude already has
Add an explicit implementation workflow with validation steps, e.g.: 1. Define SLIs → 2. Create recording rules → 3. Verify metrics are recording (`curl localhost:9090/api/v1/query?query=sli:http_availability:ratio`) → 4. Add alerting rules → 5. Test alerts with `promtool check rules`
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanatory content (e.g., the SLI/SLO/SLA hierarchy diagram, the 'When to Use' list, the 'Consider' list for choosing SLOs, and the 'Best Practices' list of 10 generic items). The core Prometheus recording rules and alerting configs are valuable, but there's significant padding around them that Claude already knows. | 2 / 3 |
Actionability | The skill provides fully executable PromQL queries, complete Prometheus recording rules, and concrete alerting rule YAML configurations that are copy-paste ready. The error budget calculations include specific numerical examples, and the SLO definitions are in deployable YAML format. | 3 / 3 |
Workflow Clarity | While the content covers the components of SLO implementation (define SLIs → set targets → calculate error budgets → implement recording rules → create alerts → build dashboards), there's no explicit step-by-step implementation workflow with validation checkpoints. The review process section lists what to review but not how to validate that the implementation is correct. | 2 / 3 |
Progressive Disclosure | There are references to external files (references/slo-definitions.md, references/error-budget.md) and related skills, which is good. However, the main file is quite long and monolithic — the detailed Prometheus recording rules, alerting rules, and dashboard queries could be split into separate reference files with the SKILL.md serving as a concise overview. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- wshobson/agents
- Commit
91fe43e
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.