o11y-logging

Implement and verify joelclaw observability on every change so failures cannot stay silent. Use when adding/updating Inngest functions, gateway channels, webhook providers, APIs, workers, or any pipeline step. Enforces canonical OTEL contract, storage path, and verification gates. Triggers on: 'o11y', 'observability', 'logging', 'otel', 'instrument this', 'silent failure', 'add telemetry', 'log this function'.

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

83%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 well-organized, highly actionable body with executable examples and a real one-level reference file. Conciseness and workflow clarity are strong but not maximal due to the lengthy Inngest triage section and verification steps delegated rather than spelled out inline.

Suggestions

Move the Inngest Replay + Hang Triage section into references/ and keep only a one-line pointer in SKILL.md to tighten conciseness, since it is a specialized troubleshooting path rather than core usage.

Inline the single key verification command (e.g. scripts/otel-smoke.sh) directly in the Implementation Workflow's 'Run verification gates' step so the checkpoint is explicit rather than deferred to the reference.

Trim the duplicated Key Files list at the bottom — the canonical paths already appear under Non-Negotiable Rules — to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	Mostly lean — rules, conventions, and code examples each earn their place without explaining concepts Claude already knows — though the Inngest Replay triage section adds length that is borderline domain-specific rather than strictly necessary, keeping it just below a clean 5.	4 / 5
Actionability	Provides copy-paste-ready TypeScript for worker/gateway emission, an executable CLI emission command, and a concrete smoke script invocation, fully covering common cases as in the score-5 anchor.	5 / 5
Workflow Clarity	The Implementation Workflow is a clear numbered sequence with a 'Run verification gates before finishing' checkpoint and a Definition of Done list, but the verification step is named rather than spelled out inline (delegated to the reference), a minor checkpoint gap versus the score-5 anchor.	4 / 5
Progressive Disclosure	Good structure with one-level-deep references ('For full checklists and command recipes, read references/implementation-checklist.md', confirmed to exist) and well-organized sections, but inline code patterns plus the reference overlap somewhat, a minor organization gap below a clean 5.	4 / 5
	Total	17 / 20 Passed

Description

96%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, specific description that explicitly covers what, when, and trigger terms with concrete subsystem examples. Minor overlap risk on generic terms like 'logging' keeps distinctiveness just below maximal.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Implement and verify joelclaw observability', 'Enforces canonical OTEL contract, storage path, and verification gates' — with comprehensive coverage of the capability surface, matching the score-5 anchor for multiple specific concrete actions.	5 / 5
Completeness	Clearly answers 'what' (implement/verify observability, enforce OTEL contract and gates) and 'when' ('Use when adding/updating Inngest functions, gateway channels, webhook providers, APIs, workers, or any pipeline step') with concrete trigger phrases, matching the score-5 anchor.	5 / 5
Trigger Term Quality	Explicit 'Triggers on:' list covers natural user phrases and synonyms — 'o11y', 'observability', 'logging', 'otel', 'instrument this', 'silent failure', 'add telemetry', 'log this function' — matching comprehensive natural-term coverage at score 5.	5 / 5
Distinctiveness Conflict Risk	The joelclaw/OTEL niche and specific subsystem triggers (Inngest, gateway channels, webhook providers) make it clearly distinct, but 'logging'/'add telemetry' are broad enough to risk minor overlap with general logging skills, placing it just below a clean 5.	4 / 5
	Total	19 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: joelhooks/joelclaw
Path: skills/o11y-logging/SKILL.md
Commit: 7094ced

Reviewed: 3 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.