observability-and-instrumentation

Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.

Quality

90%

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

88%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.

A highly actionable, well-sequenced skill with copy-paste code and explicit validation steps; the main weaknesses are mild motivational padding and a monolithic body that relies on a single lightly-signaled external reference.

Suggestions

Trim the Overview paragraph and the "Common Rationalizations" table, or move the rationalizations into a reference file, to reduce motivational padding.

Surface the checklist reference in a dedicated "References" section with a clear heading rather than appending it to the end of the Verification checklist, and confirm ../../references/observability-checklist.md resolves within the broader skill suite.

Dimension	Reasoning	Score
Conciseness	Most content earns its place via concrete tables and copy-paste code, but the motivational Overview paragraph and the seven-row "Common Rationalizations" table are over-explanation that could be trimmed without losing actionable value.	4 / 5
Actionability	Provides fully executable, copy-paste-ready TypeScript for structured logging, correlation-ID middleware, a Prometheus histogram, and OpenTelemetry SDK setup, plus concrete tables and verification procedures covering the common instrumentation cases.	5 / 5
Workflow Clarity	A clearly sequenced 7-step Process ending in an explicit validation step ("Verify the telemetry itself": force an error, send test traffic, follow a request, fire each alert) plus a final verification checklist gives explicit checkpoints and feedback loops.	5 / 5
Progressive Disclosure	Well-organized with clear section headers and a single one-level reference (../../references/observability-checklist.md), but the body is fairly monolithic and that reference is appended after the Verification checklist rather than clearly signaled in a dedicated navigation section; no bundle files exist to verify the path.	4 / 5
	Total	18 / 20 Passed

Description

92%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 description that concretely names the capability and supplies three explicit, natural trigger scenarios. The only gap is a few common synonyms (monitoring, telemetry) that would round out trigger coverage.

Suggestions

Consider adding "monitoring" or "telemetry" to the trigger list to catch users who phrase the need with those common synonyms.

The phrase "observability" itself does not appear in the description; including it would align the description with the skill name and the term practitioners search for.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Instruments code so production behavior is visible and diagnosable" plus "logging, metrics, tracing, or alerting" — giving comprehensive coverage of the domain's distinct capabilities.	5 / 5
Completeness	Clearly states what ("Instruments code so production behavior is visible and diagnosable") and provides three explicit "Use when..." trigger clauses with concrete scenarios, satisfying both what and when.	5 / 5
Trigger Term Quality	Good natural-keyword coverage ("logging, metrics, tracing, alerting", "production issues", "evidence it works"), but common synonyms like "monitoring", "telemetry", "observability", and "dashboards" are absent, leaving a few natural terms missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (production instrumentation via logging/metrics/tracing/alerting) with distinct triggers, so the risk of firing for an unrelated skill is minimal.	5 / 5
	Total	19 / 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: addyosmani/agent-skills
Path: skills/observability-and-instrumentation/SKILL.md
Commit: df1edb2

Reviewed: about 18 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.