iii-observability
Integrates OpenTelemetry tracing, metrics, and logging into iii workers. Use when setting up distributed tracing, Prometheus metrics, custom spans, or connecting to observability backends.
83
78%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/iii-observability/SKILL.mdQuality
Discovery
100%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 identifies its domain (OpenTelemetry observability for iii workers), lists specific capabilities, and includes an explicit 'Use when' clause with natural trigger terms. The only minor weakness is that 'iii workers' is somewhat opaque to someone unfamiliar with the platform, but this doesn't detract from its effectiveness as a skill selector.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'tracing, metrics, and logging', 'distributed tracing', 'Prometheus metrics', 'custom spans', 'connecting to observability backends'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (integrates OpenTelemetry tracing, metrics, and logging into iii workers) and 'when' (explicit 'Use when' clause covering distributed tracing, Prometheus metrics, custom spans, or observability backends). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'OpenTelemetry', 'tracing', 'metrics', 'logging', 'distributed tracing', 'Prometheus', 'custom spans', 'observability'. These cover the main terms a developer would use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: OpenTelemetry + iii workers is a very specific combination. Terms like 'Prometheus metrics', 'custom spans', and 'observability backends' are unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured with good progressive disclosure and clear references to implementation files and related skills. However, it lacks a concrete step-by-step setup workflow with validation checkpoints, and the inline code snippets are fragments rather than executable examples. Some sections contain boilerplate and redundant framing that could be trimmed.
Suggestions
Add a 'Quick Start' section with a complete, executable minimal example showing worker registration with otel enabled, a custom span, and expected output/verification (e.g., 'you should see traces at http://localhost:16686').
Replace the 'Adapting This Pattern' list with a numbered workflow: 1. Enable OtelModule in engine config, 2. Register worker with otel, 3. Verify traces appear in collector, 4. Add custom spans/metrics as needed.
Remove the generic 'When to Use' and 'Boundaries' boilerplate sections — these repeat standard skill metadata that doesn't provide actionable guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy — the 'When to Use' and 'Boundaries' sections at the bottom repeat generic boilerplate that doesn't add value. The 'Architecture' section explains concepts Claude could infer. The 'Comparable to' line and some framing sentences ('Use the concepts below when they fit the task') are unnecessary padding. | 2 / 3 |
Actionability | The 'Common Patterns' section provides concrete code snippets showing API usage, but they are inline fragments rather than complete executable examples. The actual working code is deferred to reference files. There's no copy-paste-ready block that shows a full minimal setup from import to running worker. | 2 / 3 |
Workflow Clarity | There is no explicit step-by-step workflow for setting up observability (e.g., 1. configure engine, 2. register worker with otel, 3. verify traces appear). The 'Adapting This Pattern' section lists actions but without sequencing or validation checkpoints. For a multi-component setup (engine config + worker SDK + collector), the lack of a clear ordered workflow with verification steps is a gap. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled one-level-deep references to implementation files (observability.js, observability.py, observability.rs, iii-config.yaml). Content is appropriately split between the overview skill and reference files, and cross-references to related skills (iii-engine-config, iii-functions-and-triggers) are clearly signaled. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- iii-hq/iii
- Commit
8921efa
- 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.