observability-sre

Skill de observabilidade e confiabilidade operacional. Use quando precisar definir logs, metricas, tracing, alertas, health checks, readiness, error budgets, rollback e operacao segura de servicos. Trigger em: "observabilidade", "observability", "SRE", "logs estruturados", "metricas", "tracing distribuido", "health check", "readiness probe", "error budget", "SLO", "alertas", "rollback seguro", "runbook operacional".

Quality

81%

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

Quality

Content

62%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 body offers well-sequenced workflows with real validation checkpoints and concrete tool guidance, but is diluted by meta/changelog content and presents workflows as prose rather than executable code. Bundle files are absent and inline detail dominates the structure.

Suggestions

Remove the non-executional meta content ("Inspiração" attribution, "O gap fechado" narrative, and "Roadmap derivado") or move it to a separate CHANGELOG/docs file to tighten the token budget.

Convert the SLO-pull workflow into executable, copy-paste-ready command examples (e.g., a real `aws cloudwatch get-metric-statistics` invocation with required flags) instead of instructional prose.

Extract the three full workflows into clearly signaled one-level-deep reference files so SKILL.md reads as an overview with explicit navigation.

Dimension	Reasoning	Score
Conciseness	Mostly actionable but padded with meta content that does not aid execution — the "Inspiração" attribution, the "O gap fechado" version narrative, the "Roadmap derivado" future-planning list, and Quando Usar/Entradas/Saidas sections that duplicate the description.	2 / 3
Actionability	Workflows name concrete tools (Datadog API with DD_API_KEY, "aws cloudwatch get-metric-statistics", Grafana HTTP API) and give specific sampling ratios, but guidance reads as instructional prose with non-copy-paste commands rather than fully executable code blocks.	2 / 3
Workflow Clarity	The SLO-driven workflow is clearly sequenced (steps 1-5) with an explicit validation checkpoint comparing current P95 against the budget ("VIOLATED budget, rollback considerado") and a re-pull feedback loop at 5min/30min/2h.	3 / 3
Progressive Disclosure	No bundle files exist and references are mostly one-level-deep, but they are scattered as inline parenthetical mentions while three full workflows and the roadmap remain inline rather than being split into clearly signaled separate files.	2 / 3
	Total	9 / 12 Passed

Description

100%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 is strong: concrete actions, an explicit bilingual trigger list, and a clear SRE/observability niche that answers both what and when. No missing trigger guidance or voice issues.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "definir logs, metricas, tracing, alertas, health checks, readiness, error budgets, rollback e operacao segura de servicos" — matching the anchor for naming several specific actions.	3 / 3
Completeness	Explicitly answers both what (definir logs, metricas, etc.) and when via "Use quando precisar..." plus the explicit "Trigger em:" list.	3 / 3
Trigger Term Quality	The "Trigger em:" list gives good coverage of natural PT/EN terms users would say ("observability", "SRE", "SLO", "error budget", "health check", "rollback seguro", "runbook operacional").	3 / 3
Distinctiveness Conflict Risk	The SRE/observability niche is anchored by distinctive triggers (SLO, error budget, readiness probe, runbook operacional) making conflicts with other skills unlikely; broad terms like "metricas" are offset by the specialized set.	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: 1 missing	Warning

	Total	15 / 16 Passed

Repository: felvieira/claude-skills-fv
Path: skills/20-observability-sre/SKILL.md
Commit: 030ef22

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