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.
Install with Tessl CLI
npx tessl i github:Dicklesworthstone/pi_agent_rust --skill slo-implementation89
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%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 well-crafted skill description that excels across all dimensions. It uses proper third-person voice, lists specific SRE capabilities, includes natural trigger terms that users would actually say, and has an explicit 'Use when...' clause with clear trigger scenarios. The domain-specific terminology makes it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting.' These are distinct, actionable capabilities in the SRE domain. | 3 / 3 |
Completeness | Clearly answers both what ('Define and implement SLIs and SLOs with error budgets and alerting') and when ('Use when establishing reliability targets, implementing SRE practices, or measuring service performance') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'SLIs', 'SLOs', 'error budgets', 'alerting', 'reliability targets', 'SRE practices', 'service performance'. Good coverage of both acronyms and full terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to SRE/reliability engineering domain with distinct terminology (SLIs, SLOs, error budgets). Unlikely to conflict with general monitoring or alerting skills due to the specific reliability engineering focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent concrete examples including executable PromQL queries and complete YAML configurations. The main weaknesses are some verbosity in explanatory sections and a lack of explicit implementation workflow with validation checkpoints. The progressive disclosure and reference structure are well done.
Suggestions
Add an explicit implementation workflow section with numbered steps and validation checkpoints (e.g., 'Verify SLI queries return expected values before creating recording rules')
Trim the 'Choose Appropriate SLOs' considerations list and SLI/SLO/SLA hierarchy explanation - Claude understands these concepts
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary explanation (e.g., the SLI/SLO/SLA hierarchy diagram explains concepts Claude already knows). The tables and formulas are useful, but some sections like 'Choose Appropriate SLOs' considerations are somewhat verbose. | 2 / 3 |
Actionability | Provides fully executable PromQL queries, complete YAML configurations for recording rules and alerting rules, and specific examples with concrete values. The code is copy-paste ready for Prometheus/Grafana implementations. | 3 / 3 |
Workflow Clarity | The review process sections outline steps but lack explicit validation checkpoints. The implementation flow (define SLIs → set SLOs → implement recording rules → create alerts) is implicit rather than explicitly sequenced with verification steps between stages. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from concepts to implementation. References to external files (slo-definitions.md, error-budget.md, slo-template.md) are clearly signaled and one level deep. Related skills are appropriately linked. | 3 / 3 |
Total | 10 / 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.
- 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.