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'.
88
83%
Does it follow best practices?
Impact
98%
2.80xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that excels in completeness and trigger term coverage, clearly specifying both when to use it and what it does. The main weakness is that the specific capabilities could be more concretely enumerated—terms like 'enforces canonical OTEL contract' are somewhat abstract. The project-specific terminology (joelclaw, Inngest) provides excellent distinctiveness.
Suggestions
Replace abstract phrases like 'enforces canonical OTEL contract, storage path, and verification gates' with more concrete actions such as 'adds OpenTelemetry spans/traces, configures log exporters, validates instrumentation coverage'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (observability/telemetry) and mentions some actions like 'implement and verify joelclaw observability', 'enforces canonical OTEL contract, storage path, and verification gates', but the actual concrete actions are somewhat abstract—'enforces' and 'implement' are broad, and it doesn't list specific discrete operations like 'add span attributes', 'configure exporters', or 'set up dashboards'. | 2 / 3 |
Completeness | Clearly answers both 'what' (implement and verify observability, enforce OTEL contract/storage path/verification gates) and 'when' (adding/updating Inngest functions, gateway channels, webhook providers, APIs, workers, or any pipeline step), with explicit trigger terms listed. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'o11y', 'observability', 'logging', 'otel', 'instrument this', 'silent failure', 'add telemetry', 'log this function'. These are terms users would naturally say when needing this skill, covering both abbreviations and full phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche—observability/telemetry specifically for the 'joelclaw' system with named components (Inngest functions, gateway channels, webhook providers). The specific project context and explicit trigger terms make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with clear executable examples, well-defined conventions, and explicit verification gates. Its main weakness is that it packs too much inline content (particularly the triage section) that would benefit from being split into referenced files, and some sections could be tightened. The non-negotiable rules and definition of done sections are particularly well-crafted for preventing silent failures.
Suggestions
Move the 'Inngest Replay + Hang Triage' section to a separate reference file (e.g., references/inngest-triage.md) and link to it from the main skill to improve progressive disclosure and conciseness.
Verify that `references/implementation-checklist.md` exists in the bundle or provide it, since it's referenced as the source for 'full checklists and command recipes'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient and avoids explaining basic concepts, but some sections like the Inngest Replay + Hang Triage section add significant length that could be a separate reference file. The event conventions section is useful but slightly verbose for inline content. | 2 / 3 |
Actionability | Provides fully executable TypeScript code examples for both worker and gateway patterns, concrete CLI commands for verification and triage, specific file paths, and a clear smoke test script invocation. Copy-paste ready. | 3 / 3 |
Workflow Clarity | The implementation workflow is clearly sequenced (identify boundary → add envelopes → include context → set severity → verify). The Definition of Done section provides explicit validation checkpoints including smoke probe and CLI verification. The triage section has a clear numbered diagnostic sequence with feedback loops. | 3 / 3 |
Progressive Disclosure | References `references/implementation-checklist.md` for detailed checklists, which is good progressive disclosure. However, the Inngest Replay + Hang Triage section is substantial inline content that could be split into a separate reference file. No bundle files were provided to verify the referenced checklist exists, and the key files list is a flat dump without navigation guidance. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- joelhooks/joelclaw
- Commit
03f0a59
- Reviewed
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.