observability-designer

Design production-ready observability strategies combining metrics, logs, and traces. Includes SLI/SLO design, golden-signals monitoring, alert optimization. Use when adding observability to a new service, refactoring alerting that is too noisy, or designing an SLO program before scaling production load.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./engineering/skills/observability-designer/SKILL.md

Quality

Content

56%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's actionable Quick Start and verification loop are excellent, but they are buried under a long, padded taxonomy of well-known observability concepts that should be moved into reference files. Trim the concept enumeration and externalize it to improve both conciseness and progressive disclosure.

Suggestions

Move the Core Competencies, Advanced Patterns, and Best Practices concept taxonomies into a separate reference file (e.g. references/observability_concepts.md) and link to it from a short overview, reducing SKILL.md to the Quick Start, scripts, and integration guidance.

Cut definitional padding that Claude already knows (e.g. what SLI/SLO/SLA mean, RED/USE method expansions, log-level enumerations) and keep only skill-specific decisions like chosen thresholds or routing rules.

Add a one-line boundary note in the description (not just the body) clarifying the split from the sibling SLO skill to reduce distinctiveness/overlap risk.

Dimension	Reasoning	Score
Conciseness	Roughly 150+ lines (Core Competencies, Advanced Patterns, Best Practices) enumerate concepts Claude already knows (SLI/SLO/SLA definitions, RED/USE methods, log levels, golden signals), which is noticeable padding; only the Quick Start and Scripts Overview are lean.	2 / 5
Actionability	The Quick Start provides copy-paste-ready commands with full flags for all three scripts and the Scripts Overview documents inputs/outputs, giving mostly executable guidance with only minor gaps in the bulk taxonomy sections.	4 / 5
Workflow Clarity	A clear sequence is present with an explicit verification loop ('track the report's noise metrics... re-run --analyze-only... iterate' and confirm panels render before closing), and the alert optimizer's analyze-then-review-then-output flow has a checkpoint, leaving only minor validation gaps.	4 / 5
Progressive Disclosure	The three bundled scripts are clearly signaled and verified as real files, but the large inline concept taxonomy that belongs in separate reference documents is kept in SKILL.md with no reference-file split, so organization is only partial.	3 / 5
	Total	13 / 20 Passed

Description

83%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 is strong: it concisely states concrete capabilities and provides explicit, natural trigger phrases for when to use the skill. Minor gaps are the omission of dashboard generation and the lack of an inline boundary note against the sibling SLO skill.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities ('SLI/SLO design', 'golden-signals monitoring', 'alert optimization', combining metrics/logs/traces), but the actions are stated at a fairly high level and dashboard generation (a bundled script) is omitted, leaving minor gaps.	4 / 5
Completeness	It explicitly answers both 'what' (design observability strategies, SLI/SLO, golden-signals, alert optimization) and 'when' with concrete trigger phrases in the 'Use when' clause, matching the top anchor.	5 / 5
Trigger Term Quality	The 'Use when' clause supplies natural phrasings users would actually say ('adding observability to a new service', 'alerting that is too noisy', 'designing an SLO program'), giving good keyword coverage, though a few synonyms and tool-specific terms are missing.	4 / 5
Distinctiveness Conflict Risk	The observability/SLO/alerting niche is mostly distinct, but there is minor overlap risk with a sibling SLO-focused skill (noted in the body as 'slo-architect') since the description itself does not draw that boundary.	4 / 5
	Total	17 / 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: alirezarezvani/claude-skills
Path: engineering/skills/observability-designer/SKILL.md
Commit: 19392f7

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