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

80%

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/20-observability-sre/SKILL.md

Quality

Content

63%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 actionable with well-sequenced workflows and a concrete validation/rollback checkpoint, but it is moderately verbose and inlines substantial detailed material (the full Runtime Feedback Sensors section) that would be better placed in a separate reference file rather than in SKILL.md itself.

Suggestions

Move the detailed Runtime Feedback Sensors workflows, anti-patterns, integration table, and version roadmap into a separate reference file (e.g. references/runtime-feedback.md), keeping only a concise overview and pointer in SKILL.md.

Trim the "Inspiração" quote block and the "O gap fechado" prose to a one-line rationale; remove or relocate the time-sensitive version roadmap (v2.7.1/v2.7.2/v2.8.0) to a changelog.

Add explicit validation checkpoints (e.g., confirm sampling configuration is active before relying on it) to the log-anomaly and response-quality workflows to match the SLO workflow's rigor.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but includes padded material — the "Inspiração" quote block, prose about "the gap closed", a future-version roadmap with time-sensitive version numbers, and an integration table — that could be tightened or deferred.	3 / 5
Actionability	Workflows give concrete, mostly executable guidance: named APIs (Datadog DD_API_KEY, Grafana HTTP API, aws cloudwatch get-metric-statistics, NerdGraph, Honeycomb Query API), specific sampling rates (100% errors, 1% info, 10% warnings), and concrete cost figures; minor gaps in exact call syntax keep it from 5.	4 / 5
Workflow Clarity	Workflows are clearly numbered and the SLO-driven flow has an explicit validation/rollback checkpoint (comparing actual P95 against budget, flagging "VIOLATED budget, rollback considerado"); the anomaly and sampling workflows have minor validation gaps.	4 / 5
Progressive Disclosure	No bundle files exist, and external references (policies/, docs/skill-guides/, templates/*) are clearly signaled and one level deep, but the entire Runtime Feedback Sensors deep-dive — workflows, anti-patterns, integration table, and roadmap — is inlined in SKILL.md rather than split into a separate guide file.	3 / 5
	Total	14 / 20 Passed

Description

96%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, specific description that clearly states capabilities and provides rich, natural trigger terms in both languages. Its only weakness is slight overlap with adjacent backend/deploy skills, which keeps distinctiveness just below the top anchor.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "definir logs, metricas, tracing, alertas, health checks, readiness, error budgets, rollback e operacao segura" — giving comprehensive coverage of the observability domain.	5 / 5
Completeness	Explicitly answers both "what" (definir logs, metricas, tracing, alertas...) and "when" ("Use quando precisar definir..." plus a dedicated "Trigger em:" list with concrete trigger phrases).	5 / 5
Trigger Term Quality	The "Trigger em:" line provides comprehensive natural-term coverage including synonyms ("observabilidade"/"observability"), SLO, error budget, health check, readiness probe, and rollback seguro.	5 / 5
Distinctiveness Conflict Risk	Niche triggers like SLO, error budget, readiness probe and runbook operacional are clearly SRE-specific with minimal conflict risk; only minor overlap with generic backend/deploy skills keeps it from a 5.	4 / 5
	Total	19 / 20 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: f3492ef

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