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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable skill body with executable code, a sequenced process, and a verification feedback loop. Its main weaknesses are some conceptual framing in the Overview and a progressive-disclosure reference to a checklist file that is not present in the bundle.

Suggestions

Tighten the Overview: drop the textbook definition of observability and lead directly with the instrumentation-first thesis and when-to-use signal.

Add the missing references/observability-checklist.md (or remove the pointer) so the one external reference resolves; a dead link is worse than no link for progressive disclosure.

Consider moving the Common Rationalizations and Red Flags tables into a reference file to slim the SKILL.md body and give the at-a-glance checklist a real home.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete code and tables, but the Overview defines observability in conceptual terms Claude already knows ("Observability is the ability to answer 'what is the system doing and why?'") and could be tightened; not a 3 because of this framing padding, not a 1 because the bulk is lean operational guidance rather than filler.	2 / 3
Actionability	Provides copy-paste-ready TypeScript for structured logging, Express correlation-ID middleware, OpenTelemetry setup, and a Prometheus Histogram, plus concrete label/cardinality examples; not a 2 because the examples are complete and executable rather than pseudocode.	3 / 3
Workflow Clarity	A clear 7-step sequence culminating in step 7 "Verify the telemetry itself" with a final verification checklist and feedback loops (force an error in staging, test-fire alerts); not a 2 because validation checkpoints are explicit, not merely listed.	3 / 3
Progressive Disclosure	Sections are well-organized, but the only external pointer — "see references/observability-checklist.md" — targets a file that does not exist in the bundle, so navigation breaks; not a 1 because the body is structured (headers, tables, code) rather than a monolithic wall of text, and not a 3 because the single one-level reference is dead.	2 / 3
	Total	10 / 12 Passed

Description

100%

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, third-person description that states concrete capabilities and provides multiple explicit "Use when" triggers covering feature shipping, signal addition, and incident diagnosis. It is distinctive and unlikely to conflict with adjacent skills.

Dimension	Reasoning	Score
Specificity	Names concrete actions — "adding logging, metrics, tracing, or alerting" — alongside the domain, matching the anchor for listing multiple specific concrete actions; not a 2 because it goes beyond naming a domain plus a few actions.	3 / 3
Completeness	Answers both what ("Instruments code so production behavior is visible and diagnosable") and when via three explicit "Use when..." clauses; not a 2 because the trigger guidance is explicit, not implied.	3 / 3
Trigger Term Quality	Uses natural terms an on-call engineer would say — "logging, metrics, tracing, alerting", "production issues" — with good coverage; not a 2 because common variations are all present rather than partially missing.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear observability niche with triggers (logging/metrics/tracing/alerting) unlikely to fire for debugging, performance, or security skills; not a 2 because it is sharply scoped rather than merely somewhat specific.	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: addyosmani/agent-skills
Commit: 8c65303

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.