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
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 defines its niche (observability for the joelclaw project), provides explicit 'Use when' guidance with specific component types, and includes a comprehensive list of natural trigger terms. The main weakness is that the concrete actions could be more specific—'implement and verify observability' and 'enforces canonical OTEL contract' are somewhat abstract without detailing the exact operations performed.
Suggestions
Make the actions more concrete by specifying what 'implement observability' entails, e.g., 'Adds structured logging, trace spans, and metric exports to functions' rather than the abstract 'implement and verify joelclaw observability'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (observability/telemetry) and mentions some actions like 'implement and verify joelclaw observability' and 'enforces canonical OTEL contract, storage path, and verification gates,' but the actual concrete actions are somewhat vague—'implement observability' is broad, and 'verification gates' lacks detail on what specifically is done. | 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 use when needing this skill. | 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
85%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, well-structured observability skill that provides concrete, actionable guidance with executable code examples and clear verification steps. The workflow is well-sequenced with explicit validation gates, and content is appropriately organized with references to deeper materials. Minor verbosity in a few sections (severity guidance, some explanatory text) prevents a perfect conciseness score, but overall the skill is highly effective.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient and avoids explaining basic concepts, but some sections like the Inngest Replay triage and the event conventions could be tightened. The severity guidance (debug/info/warn/error) is something Claude already knows. Overall mostly lean but not maximally tight. | 2 / 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 throughout. | 3 / 3 |
Workflow Clarity | The implementation workflow is clearly sequenced with 5 steps, the Definition of Done provides explicit validation checkpoints (smoke probe, CLI verification commands), and the Inngest replay triage section has a clear diagnostic sequence with feedback loops. Verification gates are explicitly required before finishing. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-organized sections, references a separate checklist file (`references/implementation-checklist.md`) for detailed checklists, and lists key files for navigation. Content is appropriately split between the overview and referenced materials without deep nesting. | 3 / 3 |
Total | 11 / 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
825972c
- 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.