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'.
95
95%
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 clearly communicates its purpose, scope, and trigger conditions. It excels at trigger term coverage and distinctiveness due to the project-specific context and comprehensive keyword list. The main weakness is that the specific actions could be more concrete—listing discrete operations rather than broad verbs like 'implement' and 'enforce'.
Suggestions
Replace broad verbs like 'implement and verify' and 'enforces' with more concrete actions, e.g., 'Adds OTEL spans and attributes, configures trace exporters, validates metric emission, checks storage path conventions.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | 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', etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (implement/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, covering both abbreviations and full phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive—targets a specific project ('joelclaw'), a specific concern (observability/telemetry), and specific infrastructure components (Inngest functions, gateway channels, webhook providers). Very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that is concise, highly actionable, and well-structured. It provides project-specific rules, executable code patterns, CLI commands for verification, and a clear triage workflow—all without wasting tokens on concepts Claude already knows. The Definition of Done section and smoke test script provide strong validation gates.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It avoids explaining what OTEL is or how observability works conceptually—it jumps straight into project-specific rules, contracts, and patterns. Every section earns its place with actionable, project-specific information. | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples for both worker and gateway patterns, specific CLI commands for verification and triage, concrete file paths, and a runnable smoke test script. The guidance is copy-paste ready and specific to the codebase. | 3 / 3 |
Workflow Clarity | The Implementation Workflow section provides a clear 5-step sequence. The Definition of Done section serves as an explicit validation checklist. The Inngest Replay triage section has a well-sequenced diagnostic workflow with verification commands. Feedback loops are implicit but present (smoke probe, otel list/stats verification gates). | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-organized sections, references `references/implementation-checklist.md` for full checklists, and lists key files for navigation. Content is appropriately split between quick patterns inline and detailed checklists in a separate file—one level deep. | 3 / 3 |
Total | 12 / 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
ce9ca8e
- 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.