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.
60
68%
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
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
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill serves as a reasonable reference catalog for iii observability primitives and patterns, with good cross-referencing to other skills and external files. However, it lacks a clear step-by-step workflow for setting up observability, has no validation checkpoints, and relies on external reference files for executable examples rather than including at least a minimal working example inline. The content is moderately concise but could be tightened by removing boilerplate sections and consolidating multi-language variants.
Suggestions
Add a 'Quick Start' workflow section with numbered steps: 1) install iii-observability, 2) configure otel in registerWorker, 3) verify traces are exported (with a specific validation command or check), 4) add custom spans as needed.
Include at least one complete, executable code example inline (e.g., a minimal Node.js worker with otel enabled and a custom span) rather than deferring all examples to reference files.
Add a validation/verification step — e.g., 'Confirm traces are arriving: check Jaeger UI at localhost:16686 or curl the Prometheus endpoint at localhost:9464/metrics'.
Remove or consolidate the generic 'When to Use' and 'Boundaries' boilerplate sections which don't add skill-specific value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some redundancy — the 'When to Use' and 'Boundaries' sections at the bottom repeat generic boilerplate that doesn't add value. The 'Common Patterns' section lists multi-language variants that could be more concise. The 'Key Concepts' bullet list mixes architectural explanation with actionable guidance, adding some bloat. | 2 / 3 |
Actionability | The skill provides concrete API calls and configuration snippets in the 'Common Patterns' section, but they are inline code fragments rather than complete, executable examples. The actual executable code is deferred to reference files (observability.js/py/rs) which are not provided in the bundle, so the skill body itself lacks copy-paste-ready working examples. | 2 / 3 |
Workflow Clarity | There is no clear multi-step workflow or sequenced process for setting up observability. The content reads as a reference catalog of primitives and patterns rather than a guided sequence. There are no validation checkpoints or feedback loops for verifying that telemetry is correctly configured and exporting data. | 1 / 3 |
Progressive Disclosure | The skill references external files (observability.js/py/rs, iii-config.yaml) and cross-references other skills (iii-engine-config, iii-functions-and-triggers, iii-error-handling), which is good structure. However, no bundle files were provided to verify these references exist, and the main body still contains substantial inline content that could benefit from better separation between quick-start and detailed reference material. | 2 / 3 |
Total | 7 / 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
a7ebbbb
- 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.