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

53%

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

35%Weight 40%Scale 1-3

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

The skill is well-organized into clear sections but its core instructions are generic boilerplate lacking executable guidance, and its sole external reference points to a file that is not present in the bundle.

Suggestions

Replace the generic Instructions with concrete, actionable SLO steps (e.g., sample SLI/SLO definitions, error-budget math, alert-rule patterns) to lift actionability.

Either create the referenced 'resources/implementation-playbook.md' or remove the dangling references in the Instructions and Resources sections so progressive disclosure resolves.

Tighten the redundant 'Context' section, which restates information already in the description.

Dimension	Reasoning	Score
Conciseness	Mostly lean, but the 'Context' section restates the description and the 'Instructions' are generic boilerplate that could be tightened, matching the 'mostly efficient but includes some unnecessary explanation' anchor.	2 / 3
Actionability	The Instructions are vague and abstract ('Apply relevant best practices and validate outcomes', 'Provide actionable steps and verification') with no concrete code, commands, or examples, matching the 'describes rather than instructs' anchor.	1 / 3
Workflow Clarity	A step list is present (clarify goals, apply practices, provide steps, verify) but it is generic with no concrete validation checkpoints or error-recovery feedback loops for an inherently multi-step SLO implementation process.	2 / 3
Progressive Disclosure	The body is sectioned clearly and signals a one-level reference to 'resources/implementation-playbook.md', but that file does not exist (no resources/ directory), so the reference is broken and navigation is not actually resolvable.	2 / 3
	Total	7 / 12 Passed

Description

72%Weight 40%Scale 1-3

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 lists concrete SLO-specific capabilities and good natural trigger terms, but is held back by second-person voice (costing specificity) and the absence of an explicit 'Use when' clause (capping completeness).

Suggestions

Rewrite in third person ('Designs SLO frameworks, defines SLIs, and builds monitoring...') to avoid the second-person specificity penalty.

Add an explicit trigger clause such as 'Use when implementing SLOs, SLIs, or error budgets for services' to lift completeness to 3.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions ('Design SLO frameworks, define SLIs, and build monitoring that balances reliability with delivery velocity'), which is anchor-3 caliber, but the second-person voice ('You are an SLO expert') triggers the mandatory specificity penalty of -1.	2 / 3
Completeness	Clearly answers 'what' (design SLO frameworks, define SLIs, build monitoring) but provides no 'Use when...' trigger clause, so completeness is capped at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Good coverage of natural terms users would say: 'SLO (Service Level Objective)', 'SLIs', 'error budget', 'reliability', and 'monitoring'.	3 / 3
Distinctiveness Conflict Risk	The SLO/SLI/error-budget niche has distinct triggers and is unlikely to conflict with unrelated skills, matching the 'clear niche' anchor.	3 / 3
	Total	10 / 12 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: e63f7dd

Reviewed: 13 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.