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

93%

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

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

The body is well-structured, executable, and appropriately offloads detail to a real reference file with verification gates and triage guidance. It is slightly verbose in places but otherwise strong.

Suggestions

Tighten the Event Conventions and severity primers to bullet essentials, removing phrasing that restates what experienced engineers already know.

Make the Implementation Workflow's validation step explicit (e.g., 'Only mark done after smoke probe passes') to push workflow clarity toward a strict validate-then-proceed loop.

Consider moving the Inngest Replay + Hang Triage section into the reference file to keep SKILL.md focused on the core implementation contract.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence (no primer on what OTEL/observability is), but small primers like the severity-level list and 'event-per-hop (wide event style)' elaboration could be trimmed. Fits the 'efficient; minor over-explanation' anchor better than lean-5.	4 / 5
Actionability	Provides fully executable, copy-paste-ready TypeScript and bash blocks (emitMeasuredOtelEvent, emitGatewayOtel, joelclaw otel emit/search/list/stats) plus concrete file paths, covering the common cases.	5 / 5
Workflow Clarity	The Implementation Workflow is a numbered sequence and the Definition of Done plus the verification gates (smoke probe, otel list/stats) provide checkpoints and a fix-retry signal in the replay triage. A couple of validation transitions are implicit rather than strict validate-then-proceed, so it sits at 'clear sequence with most checkpoints' rather than explicit-feedback-loop 5.	4 / 5
Progressive Disclosure	SKILL.md is an overview that signals a single one-level-deep reference ('For full checklists and command recipes, read references/implementation-checklist.md'), and the referenced file plus scripts/otel-smoke.sh and assets exist as real bundle files, making navigation clean.	5 / 5
	Total	18 / 20 Passed

Description

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

The description is concrete, complete, and trigger-rich, answering both what and when with named subsystems and natural trigger phrases. It is a strong, low-conflict description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Implement and verify', 'Enforces canonical OTEL contract, storage path, and verification gates') and concrete targets ('Inngest functions, gateway channels, webhook providers, APIs, workers'), giving comprehensive coverage.	5 / 5
Completeness	Clearly states what ('Implement and verify joelclaw observability... Enforces canonical OTEL contract, storage path, and verification gates') and when ('Use when adding/updating Inngest functions... Triggers on: ...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Explicit trigger list ('o11y', 'observability', 'logging', 'otel', 'instrument this', 'silent failure', 'add telemetry', 'log this function') covers natural terms and synonyms a user would actually say.	5 / 5
Distinctiveness Conflict Risk	Targets a distinct joelclaw/OTEL niche with specific subsystem triggers, making conflict with unrelated skills minimal.	5 / 5
	Total	20 / 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: d952451

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