observability

Add agent-first observability to code — structured logs, health endpoints, failure-state persistence, and explicit failure modes — so the next agent hitting a problem at 3am has the signals it needs to diagnose. Use when asked to "add logging", "add observability", "add metrics", "debug later", "make this observable", or when building/refactoring a subsystem that will run unattended (auto-mode engine, background jobs, servers, watchers). Operationalizes VISION.md's "agent-first observability" principle.

Quality

92%

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

85%

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 and well-structured with executable examples and a verification step, but leans slightly verbose in its context framing. No bundle files exist, so progressive disclosure is judged on organization alone.

Suggestions

Trim the <context> section's verbatim quotes of the system prompt and VISION.md to the essential points, keeping only what motivates the skill.

Tighten transitional prose like 'This skill is the thinking process for adding it. Not "add logs everywhere"...' into more direct guidance to push conciseness toward score 3.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's competence, but the context section quotes the system prompt and VISION.md at length and a few prose sentences could be tightened, matching the score-2 anchor over the lean-every-token-earns-its-place score-3.	2 / 3
Actionability	Provides executable TypeScript examples (log.info, writeAtomically, the try/catch refactor), specific file paths, and concrete do/don't lists, matching the score-3 anchor for fully executable guidance.	3 / 3
Workflow Clarity	Clear 7-step sequence with an explicit validation checkpoint in Step 7 (simulate a failure and confirm signals reach a fresh reader) plus a success-criteria checklist, matching the score-3 anchor with feedback loops.	3 / 3
Progressive Disclosure	Single-file skill with no bundle directories, organized into clearly labeled sections and no nested references, so well-organized sections justify the score-3 anchor.	3 / 3
	Total	11 / 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.

The description is strong: it names concrete capabilities, provides natural trigger phrases, answers both what and when, and occupies a distinct niche. It uses third-person voice throughout, so no voice penalty applies.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'structured logs, health endpoints, failure-state persistence, and explicit failure modes' — matching the score-3 anchor for multiple specific concrete actions rather than the score-2 'some actions' level.	3 / 3
Completeness	Explicitly answers both what (the four instrumentation additions) and when via a 'Use when...' clause with explicit triggers, matching the score-3 anchor.	3 / 3
Trigger Term Quality	Includes natural phrases users would say — "add logging", "add observability", "add metrics", "debug later", "make this observable" — giving good coverage rather than only some keywords.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (agent-first observability for unattended subsystems) with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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: gsd-build/gsd-2
Path: src/resources/skills/observability/SKILL.md
Commit: 33c00aa

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