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.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/observability-monitoring/skills/slo-implementation/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable PromQL/YAML, but it repeats the same queries across sections, lacks explicit validation checkpoints, and contains two dangling references to missing files alongside a working pointer to details.md.

Suggestions

Fix the dangling references: either create references/slo-definitions.md and references/error-budget.md or remove the "Reference:" lines pointing to them.

De-duplicate the availability/latency PromQL that recurs in the SLI, recording-rule, and dashboard sections — define each query once and reference it.

Add explicit validation checkpoints to the implementation workflow, e.g. verify each recording rule returns a value with a test query before layering alerts on top.

Dimension	Reasoning	Score
Conciseness	The body is mostly technical reference with little concept-padding, but the same availability/latency PromQL is repeated across SLI definitions, recording rules, and dashboard queries, and the opening line restates the description, which is more than minor tightening.	3 / 5
Actionability	Concrete, copy-paste-ready PromQL and YAML for SLI definitions, recording rules, multi-window burn-rate alerts, and error-budget formulas with worked numbers cover the common SLO implementation cases.	5 / 5
Workflow Clarity	Sections imply a sequence (SLIs → SLO targets → error budget → recording rules → alerting → dashboard) but there are no explicit validation checkpoints such as verifying a recording rule returns a value before adding alerts.	3 / 5
Progressive Disclosure	A real one-level-deep reference (references/details.md) is clearly signaled at the end, but two body references (references/slo-definitions.md and references/error-budget.md) point to non-existent files, and recording/alerting YAML is inlined where it overlaps details.md.	3 / 5
	Total	14 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and distinct, clearly stating both capabilities and use-when triggers in third person. Trigger-term coverage is strong but could add a few more natural synonyms in the when-clause.

Dimension	Reasoning	Score
Specificity	"Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting" names the domain plus multiple concrete actions (define SLIs, implement SLOs, error budgets, alerting), matching the comprehensive-coverage anchor.	5 / 5
Completeness	It explicitly answers both what ("Define and implement SLIs/SLOs with error budgets and alerting") and when ("Use when establishing reliability targets, implementing SRE practices, or measuring service performance") with concrete trigger phrases.	5 / 5
Trigger Term Quality	"Use when establishing reliability targets, implementing SRE practices, or measuring service performance" provides good natural trigger phrases, but common synonyms (SLI/SLO/error budget as triggers) appear only in the what-clause rather than the when-clause, leaving a few natural terms missing.	4 / 5
Distinctiveness Conflict Risk	The SLO/error-budget/SRE framing carves a clear niche distinct from generic monitoring skills, with minimal trigger overlap.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: wshobson/agents
Path: plugins/observability-monitoring/skills/slo-implementation/SKILL.md
Commit: d6837ae

Reviewed: about 11 hours ago

Table of Contents

Discovery Implementation Validation

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.