observability-monitoring-slo-implement

You are an SLO (Service Level Objective) expert specializing in implementing reliability standards and error budget-based practices. Design SLO frameworks, define SLIs, and build monitoring that balances reliability with delivery velocity.

Quality

51%

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 ./skills/observability-monitoring-slo-implement/SKILL.md

Quality

Content

42%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 body is well-structured and reasonably concise but offers only generic, non-executable guidance with no concrete SLO patterns, and its sole detailed reference points to a file that does not exist. Validation is mentioned but never made into a real checkpoint.

Suggestions

Replace the generic Instructions with concrete, actionable SLO steps such as example SLI query templates, error-budget calculation formulas, and alert threshold examples.

Either create the referenced 'resources/implementation-playbook.md' or remove the dangling reference so progressive-disclosure navigation actually resolves.

Add an explicit validation checkpoint with a concrete action (e.g., 'Verify the SLO's SLI queries return data before publishing the dashboard') to lift workflow clarity above 3.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but the Context section restates the description's purpose and the Instructions are generic boilerplate, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the lean 4.	3 / 5
Actionability	Instructions are abstract ('Apply relevant best practices and validate outcomes') with no concrete SLI queries, error-budget formulas, alert thresholds, or examples, and the only detailed resource does not exist, matching 'minimal concrete guidance; missing the specific steps'.	2 / 5
Workflow Clarity	A recognizable sequence is listed (clarify, apply, validate, open playbook) but checkpoints are only nominally mentioned ('validate outcomes') with no concrete validation step, fitting 'steps listed but validation gaps; checkpoints missing or implicit'.	3 / 5
Progressive Disclosure	Sections are well-organized and a one-level-deep reference is signaled, but the referenced 'resources/implementation-playbook.md' does not exist, so navigation is non-functional, matching 'references present but not clearly signaled / could be better organized'.	3 / 5
	Total	11 / 20 Passed

Description

61%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 clearly defines a specific SLO/SLI/error-budget niche with several concrete actions, but it omits any explicit 'Use when' trigger guidance, which caps completeness. Trigger terms are strong but miss common synonyms.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when defining SLIs/SLOs, setting error budgets, or building reliability dashboards') to raise completeness above 3.

Include natural synonyms users actually say, such as 'uptime', 'availability targets', and 'service reliability', to improve trigger-term coverage.

Sharpen distinctiveness from generic monitoring skills by mentioning error-budget consumption alerts or SLO reporting specifically.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions ('Design SLO frameworks, define SLIs, and build monitoring that balances reliability with delivery velocity'), matching the 'several specific actions; minor gaps' anchor rather than the comprehensive 5 or the 1-2-action 3.	4 / 5
Completeness	The description clearly states what the skill does but has no 'Use when...' trigger clause, and the rubric caps completeness at 3 when explicit trigger guidance is missing.	3 / 5
Trigger Term Quality	Covers natural domain terms (SLO, SLIs, error budget, monitoring, reliability) but omits common synonyms like 'uptime' and 'availability targets', fitting 'good keyword coverage; a few natural terms missing' rather than comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	The SLO/SLI/error-budget niche is mostly distinct but overlaps with general monitoring/observability skills and lacks explicit trigger phrases to sharpen routing, matching 'mostly distinct; minor overlap risk'.	4 / 5
	Total	15 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/observability-monitoring-slo-implement/SKILL.md
Commit: 3eff4af

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