CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

Quality

Content

61%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.

A technically solid reference body with real, executable Prometheus rules and useful numeric tables, but it reads as a domain reference rather than a guided workflow: there is no explicit step sequence or validation feedback loop, and some filler (generic considerations list, ASCII dashboard) dilutes token efficiency. The reference file is genuine and well signaled, though duplication between body and details.md could be trimmed.

Suggestions

State an explicit implementation workflow (define SLIs → set SLO targets → add recording rules → add alerts → verify) and include a validation step such as `promtool check rules slo_rules.yaml` before deployment.

Define the missing burn_rate_1h, burn_rate_6h, and burn_rate_30m recording rules that the alerting rules reference, so the configuration is complete and executable end-to-end.

Move the Grafana dashboard mockup and the generic 'Consider' bullet list into references/details.md, and reference the multi-window alert pattern there instead of duplicating it in the body.

DimensionReasoningScore

Conciseness

Mostly efficient — the bulk is concrete promql/YAML rather than prose — but the generic "Consider: user expectations, business requirements, current performance..." bullet list, the ASCII Grafana dashboard mockup, and the SLA/SLO/SLI concept hierarchy explain things Claude already knows or add little actionable value. Fits 'mostly efficient but includes some unnecessary explanation or could be tightened'; the genuinely useful content (downtime table, rules) doesn't lift it to 4.

3 / 5

Actionability

The recording rules, SLO YAML, and alerting rules are largely copy-paste-ready Prometheus configuration. Not 5 because the alert rules depend on recording metrics (burn_rate_1h, burn_rate_6h, burn_rate_30m) that are never defined in the recording-rules section, and the 'days until exhausted' query is dubious, leaving minor execution gaps.

4 / 5

Workflow Clarity

The section order (SLI → SLO targets → error budget → recording rules → alerts → dashboard) implies a sequence but no explicit step ordering is stated, and there are no validation checkpoints (e.g., promtool check rules, verifying rules loaded). Fits 'steps listed but validation gaps; sequence present but checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

The body is well-sectioned and points to references/details.md, which exists and is one level deep, clearly signaled at the end ("Read that file for the full pattern library"). Not 5 because the pointer appears only at the very end, and content that belongs in the reference (dashboard mockup, multi-window alert variants that duplicate details.md) is inlined in SKILL.md.

4 / 5

Total

14

/

20

Passed

Description

88%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.

A strong description: it pairs concrete, domain-specific capabilities with an explicit 'Use when...' trigger clause and uses third person throughout. The only gaps are a few missing natural synonyms (availability, uptime, SLA) and slight overlap risk with generic monitoring skills on the broadest trigger phrases.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting" — covering definition, implementation, error budgets, and alerting comprehensively. Not 4 because no meaningful capability within the SLO domain is left uncovered.

5 / 5

Completeness

Explicitly answers both: the what ("Define and implement... SLIs and SLOs with error budgets and alerting") and the when ("Use when establishing reliability targets, implementing SRE practices, or measuring service performance"). Both halves are concrete, mirroring the top anchor.

5 / 5

Trigger Term Quality

Good coverage of natural terms users would say: "SLIs", "SLOs", "error budgets", "reliability targets", "SRE practices". Not 5 because common variations users naturally say — "availability", "uptime", "SLA", "burn rate" — are absent, matching the 'a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

The SLI/SLO/error-budget/SRE vocabulary carves a clear niche, but the trigger phrases "alerting" and "measuring service performance" overlap with general monitoring/observability skills. Fits 'mostly distinct; minor overlap risk with closely related skills' rather than the minimal-conflict top anchor.

4 / 5

Total

18

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

wshobson/agents

Path

plugins/observability-monitoring/skills/slo-implementation/SKILL.md

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.