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.
76
70%
Does it follow best practices?
Impact
—
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
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 solid skill description with an explicit 'Use when' clause and good trigger term coverage across the observability domain. Its main weakness is that the 'what' portion could be more specific about concrete actions (e.g., configuring exporters, instrumenting routes, setting up dashboards). The niche focus on OpenTelemetry for iii workers makes it highly distinctive.
Suggestions
Expand the capability list with more concrete actions, e.g., 'configure trace exporters, instrument HTTP handlers, define custom metrics, set up Prometheus scrape endpoints'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (OpenTelemetry, observability) and some actions (tracing, metrics, logging), but doesn't list multiple concrete actions like 'create custom spans, configure exporters, set up Prometheus endpoints, instrument middleware'. | 2 / 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, and observability backends). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'OpenTelemetry', 'tracing', 'metrics', 'logging', 'distributed tracing', 'Prometheus', 'custom spans', 'observability backends' — these are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped to OpenTelemetry integration specifically for 'iii workers', with domain-specific triggers like Prometheus, distributed tracing, and observability backends that are unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a reasonable overview of iii observability primitives with useful inline code snippets and references to external implementations. However, it lacks a complete executable example in the body, has no explicit step-by-step workflow with validation checkpoints, and includes some redundant/boilerplate sections that consume tokens without adding value. The content would benefit from a concrete quick-start workflow and trimming overlapping sections.
Suggestions
Add a concise, complete quick-start example (5-10 lines) showing registerWorker with otel config and a custom span, rather than relying entirely on external reference files.
Replace the separate 'Common Patterns' and 'Adapting This Pattern' sections with a single unified section to eliminate overlap and save tokens.
Add an explicit step-by-step setup workflow with validation (e.g., 1. Enable otel → 2. Start collector → 3. Verify traces appear → 4. Add custom spans).
Remove the generic 'When to Use' and 'Boundaries' boilerplate sections — these are meta-instructions that don't add actionable guidance for the task.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary sections like 'When to Use' and 'Boundaries' that are boilerplate/meta rather than instructive. The 'Architecture' paragraph explains concepts Claude could infer. The 'Adapting This Pattern' section partially overlaps with 'Common Patterns'. | 2 / 3 |
Actionability | The 'Common Patterns' section provides concrete code snippets inline, but they are one-liners rather than complete executable examples. The actual full implementation is deferred to reference files. There's no copy-paste-ready complete example in the skill body itself — just fragments. | 2 / 3 |
Workflow Clarity | There is no explicit multi-step workflow with sequencing or validation checkpoints. The skill describes what primitives to use and common patterns but doesn't walk through a setup process step-by-step (e.g., 1. enable otel config, 2. verify traces appear, 3. add custom spans). For an integration task involving configuration + code + verification, this lacks validation steps. | 2 / 3 |
Progressive Disclosure | References to external files (observability.js, observability.py, observability.rs, iii-config.yaml) are present and one-level deep, which is good. However, no bundle files were provided to verify these exist, the reference sentence is awkwardly split across lines ('connected to an OTel collector' appears after the Python/Rust references), and the inline content could be better organized with a clearer quick-start section. | 2 / 3 |
Total | 8 / 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
d51a06d
- 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.