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.
61
52%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/20-observability-sre/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a reasonably well-constructed skill description that covers the observability and reliability domain with explicit trigger guidance. Its main strengths are the comprehensive list of trigger terms and the explicit 'Use quando' clause. Its weaknesses are that the capabilities are listed more as topics than concrete actions, and some terms could overlap with adjacent DevOps/infrastructure skills.
Suggestions
Replace the generic verb 'definir' with multiple specific actions like 'configure distributed tracing, set up metric dashboards, define SLO-based alerts, implement health check endpoints' to improve specificity.
Add distinguishing context to reduce overlap with DevOps skills, e.g., 'Use this skill specifically for production observability design and SRE practices, not for CI/CD pipelines or infrastructure provisioning.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (observability and operational reliability) and lists several relevant concepts (logs, metrics, tracing, alerts, health checks, readiness, error budgets, rollback), but these are more like topic keywords than concrete actions. It says 'definir' (define) but doesn't describe multiple distinct actions like 'configure alerts, set up dashboards, implement tracing'. | 2 / 3 |
Completeness | The description clearly answers both 'what' (observability and operational reliability skill covering logs, metrics, tracing, alerts, health checks, etc.) and 'when' with an explicit 'Use quando precisar...' clause listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms a user would mention: logs, metricas, tracing, alertas, health checks, readiness, error budgets, rollback, operacao segura. These are terms practitioners naturally use when discussing observability and reliability topics. | 3 / 3 |
Distinctiveness Conflict Risk | While the observability/reliability niche is fairly specific, terms like 'logs', 'alertas', and 'rollback' could overlap with DevOps, CI/CD, or infrastructure skills. The combination of all these terms together helps, but individual triggers could cause conflicts with related operational skills. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads as a role description and checklist rather than actionable operational guidance. It lacks concrete examples (log formats, metric definitions, health check code, alerting rules, rollback commands) that would make it useful for Claude to execute observability and SRE tasks. The content would benefit significantly from executable examples, a clear workflow sequence, and specific implementation patterns.
Suggestions
Add concrete, executable examples for key tasks: structured log format (JSON schema), health check endpoint code, example alerting rules, and a sample rollback procedure with specific commands.
Define a clear sequenced workflow with validation checkpoints, e.g.: 1. Audit existing signals → 2. Define missing metrics/logs → 3. Validate coverage against checklist → 4. Implement health checks → 5. Configure alerts → 6. Document runbooks → 7. Handoff.
Replace the generic 'Responsabilidades' section with specific implementation patterns or decision trees (e.g., 'When to use readiness vs liveness probes', 'How to structure correlation IDs across services').
Consolidate the external references into a single 'References' section at the bottom with brief descriptions of what each linked file provides.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably structured but includes some sections that are somewhat generic and could be tightened (e.g., 'Responsabilidades' largely restates the checklist, 'Quando Usar/Nao Usar' is somewhat obvious). It avoids explaining basic concepts to Claude, but there's redundancy between sections. | 2 / 3 |
Actionability | The skill provides no concrete code, commands, configuration examples, or executable guidance. It reads as a high-level checklist of responsibilities and outputs rather than actionable instructions Claude can follow. There are no specific log format examples, metric definitions, alerting rule templates, health check implementations, or rollback procedures. | 1 / 3 |
Workflow Clarity | There is no clear sequenced workflow for multi-step processes. The content lists responsibilities and checklists but doesn't define an order of operations, validation checkpoints, or feedback loops for tasks like setting up observability, responding to incidents, or performing rollbacks. | 1 / 3 |
Progressive Disclosure | The skill references external files (docs/skill-guides/observability-sre.md, various policies and templates) which shows some progressive disclosure structure. However, the references are scattered throughout and not clearly organized in a navigation section, and it's unclear what content those files contain. | 2 / 3 |
Total | 6 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- felvieira/claude-skills-fv
- Commit
e9f6648
- 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.