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'.
90
87%
Does it follow best practices?
Impact
98%
2.80xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
100%
81%Document Processing Worker: Add Observability
Inngest worker OTEL instrumentation
emitMeasuredOtelEvent usage
0%
100%
Correct import path
0%
100%
Emit-once inside step.run
41%
100%
Failure sets success false
0%
100%
High-cardinality values in metadata
0%
100%
Stable dotted action name
37%
100%
source is subsystem name
0%
100%
No console.log as primary
0%
100%
No direct DB writes
100%
100%
metadata has operational context
0%
100%
Event-per-hop style
20%
100%
95%
39%Gateway Notification Channel: Add Observability
Gateway OTEL emission
emitGatewayOtel usage
20%
100%
Correct import source
50%
50%
Failure sets success false with error
0%
100%
Severity levels correct
100%
100%
Session/queue in metadata
50%
100%
No direct DB writes
100%
100%
Stable dotted action name
80%
100%
Stable component name
50%
100%
No console.log as primary
60%
100%
Wide event style
100%
100%
100%
68%Webhook Handler Observability Audit
Event schema compliance and anti-pattern removal
Replaces console.log
40%
100%
No direct Typesense writes
100%
100%
Uses canonical emit function
0%
100%
Required fields present
0%
100%
High-cardinality fields moved to metadata
0%
100%
No secrets in payload
100%
100%
success false with error on failure
0%
100%
Correct failure severity
100%
100%
Stable dotted action names
0%
100%
No ad-hoc top-level fields
0%
100%
- Repository
- joelhooks/joelclaw
- Commit
825972c
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
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.