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

91%

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

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

Excellent body content: lean, highly actionable, with explicit verification gates, a Definition of Done checklist, and a well-organized bundle (a substantive checklist reference and a working smoke-test script). The only structural nit is that the niche Inngest replay/hang triage procedure is inlined rather than split into a reference.

Dimension	Reasoning	Score
Conciseness	The body is lean and imperative throughout — rules, conventions, and copy-paste snippets with no explanation of concepts Claude already knows. Every section carries operational weight, matching the 'every token earns its place' anchor; not 4 because there is no padding to trim.	5 / 5
Actionability	Fully executable, copy-paste-ready TypeScript examples for worker and gateway emission, a concrete CLI command with the exact flag ('--metadata', and the note that '--attributes' does not exist), the smoke-probe invocation, and a Key Files list of real paths. Coverage spans the common cases, matching the level-5 anchor.	5 / 5
Workflow Clarity	The Implementation Workflow is a clear 5-step sequence with an explicit validation gate ('Run verification gates before finishing'), backed by a Definition of Done checklist with the smoke-probe command, and the Replay + Hang Triage section provides an explicit inspect-diagnose-recover feedback loop. Not 4 because validation checkpoints are explicit, not merely implied.	5 / 5
Progressive Disclosure	Good structure: an overview body with quick patterns, one clearly signaled one-level-deep reference ('For full checklists and command recipes, read references/implementation-checklist.md' — verified to exist and be substantive) and a real helper script. Not 5 because the specialized 'Inngest Replay + Hang Triage' troubleshooting section is inlined in SKILL.md where it arguably belongs in a separate reference file, keeping the core body tighter.	4 / 5
	Total	19 / 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.

A strong description that explicitly states what the skill does, when to use it, and a concrete trigger list, all in third person. Minor gaps: a few common trigger synonyms are absent and 'logging' is broad enough to risk overlap with generic logging skills.

Suggestions

Add natural trigger synonyms such as 'tracing', 'monitoring', or 'metrics' to the Triggers-on list.

Enumerate one or two more concrete capabilities (e.g., 'emit structured OTEL events and verify delivery via smoke probe') to sharpen the what.

Dimension	Reasoning	Score
Specificity	Names concrete actions — 'Implement and verify joelclaw observability', 'Enforces canonical OTEL contract, storage path, and verification gates' — with only minor gaps. Not 5 because the actions are summarized rather than enumerated comprehensively (e.g., emit events, run smoke probe, query by source/component); not 3 because it lists several specific actions beyond just naming the domain.	4 / 5
Completeness	Explicitly answers both: what ('Implement and verify joelclaw observability... Enforces canonical OTEL contract, storage path, and verification gates') and when ('Use when adding/updating Inngest functions, gateway channels, webhook providers, APIs, workers, or any pipeline step' plus concrete trigger phrases), matching the level-5 anchor exactly.	5 / 5
Trigger Term Quality	The explicit trigger list ('o11y', 'observability', 'logging', 'otel', 'instrument this', 'silent failure', 'add telemetry', 'log this function') covers natural phrasings well. Not 5 because common synonyms like 'tracing', 'monitoring', 'metrics', or 'alerts' are missing; not 3 because coverage goes well beyond a couple of generic keywords and includes natural user phrasings.	4 / 5
Distinctiveness Conflict Risk	The joelclaw/Inngest/gateway niche is distinct with dedicated triggers, but the broad 'logging' trigger term could overlap with a generic logging skill. Mostly distinct with minor overlap risk, so 4 rather than 5; clearly more specific than the level-3 anchor.	4 / 5
	Total	17 / 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: aa0116c

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