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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

A code-rich, highly actionable SLO reference whose main weaknesses are unnecessary conceptual filler and two broken reference-file pointers in the bundle.

Suggestions

Create the missing references/slo-definitions.md and references/error-budget.md files (or remove/fix the inline 'See ...' pointers) so all referenced paths resolve.

Cut the SLI/SLO/SLA hierarchy diagram, the generic 'Consider' bullet list, and the ASCII dashboard mockup — Claude already knows these concepts and the space is better spent on patterns.

Add an explicit numbered implementation workflow with validation checkpoints (e.g., verify recording rules return data before adding alerts) to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The bulk is lean executable code, but the SLI/SLO/SLA hierarchy diagram, the generic 'Consider: User expectations, Business requirements...' list, and the ASCII dashboard mockup explain concepts or pad content Claude does not need.	2 / 3
Actionability	Provides fully executable, copy-paste-ready PromQL queries, Prometheus recording rules, alerting rules, and YAML SLO configs with concrete thresholds and burn-rate values.	3 / 3
Workflow Clarity	Sections loosely follow an implementation order (SLIs → SLO targets → error budget → recording rules → alerting → dashboard) but there are no explicit validation checkpoints or feedback loops tying the steps together.	2 / 3
Progressive Disclosure	Content is organized into clear sections and details.md is correctly one level deep, but two referenced files — references/slo-definitions.md and references/error-budget.md — do not exist in the bundle, leaving broken pointers.	2 / 3
	Total	9 / 12 Passed

Description

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.

A strong description that pairs concrete, domain-specific capabilities with an explicit 'Use when' trigger clause in third-person voice, closely matching the good examples.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting' — naming specific domain artifacts rather than vague verbs.	3 / 3
Completeness	Explicitly answers both what ('Define and implement ... with error budgets and alerting') and when ('Use when establishing reliability targets, implementing SRE practices, or measuring service performance').	3 / 3
Trigger Term Quality	Covers natural terms a user would say — 'reliability targets', 'SRE practices', 'measuring service performance' — alongside the domain terms SLIs/SLOs/error budgets.	3 / 3
Distinctiveness Conflict Risk	SLO/SLI implementation with error budgets is a distinct niche with specific triggers unlikely to collide with other skills.	3 / 3
	Total	12 / 12 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
Commit: d7cf7dc

Reviewed: about 23 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.