otel-telemetrygen

Build safe, version-pinned telemetrygen commands for synthetic OTLP traces, metrics, and logs. Use for “send sample traces to this collector,” “load-test an OTLP endpoint,” “generate traffic to verify a processor, OTTL transform, or tail sampling,” and “produce test data for dashboards.” Also use when choosing telemetrygen transport, TLS, attributes, counts, duration, or rate. Not for application SDK instrumentation or production collection that does not use telemetrygen.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, executable skill body with strong command examples, explicit validation for a load-generating tool, and clean one-level-deep reference split. The only weak spot is mild over-explanation in the environment-variable and rate-limiting prose.

Suggestions

Tighten the 'Make environment behavior explicit' paragraph: lead with the actionable flag-vs-env rule and condense the inherited-values rationale.

Compress the per-worker rate formula explanation into a one-line equation with a brief caveat rather than a multi-clause paragraph.

Consider moving the 'Before finalizing a response, check that' checklist into the collector-verification reference so the main body stays a concise overview.

Dimension	Reasoning	Score
Conciseness	Mostly lean and information-dense with executable shapes and flag-level detail, but the 'Make environment behavior explicit' and rate-limiter explanation paragraphs contain prose that could be trimmed without losing actionability.	4 / 5
Actionability	Provides copy-paste-ready executable commands for all three signals, a docker run example, and pinned install/image references; defers only exhaustive flag lookup to a real reference file, which is appropriate.	5 / 5
Workflow Clarity	Sequences a 6-step command-construction process and a Collector-verification recipe with explicit validation controls (finite bounds, refuse --rate 0/--duration inf, known input + positive control, inspect only after flush) plus a finalizing checklist; the batch/load nature is covered by real checkpoints so no cap applies.	5 / 5
Progressive Disclosure	Body is a clear overview with two well-signaled, one-level-deep references ([references/flags.md], [references/collector-verification.md]) that exist as real files; detail is appropriately split out rather than inlined.	5 / 5
	Total	19 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that concretely states capabilities, surfaces natural trigger phrases, and explicitly bounds scope with a negative-trigger clause. It satisfies what/when and distinctiveness without padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Build safe, version-pinned telemetrygen commands for synthetic OTLP traces, metrics, and logs') plus choosing transport, TLS, attributes, counts, duration, and rate — comprehensive coverage of the tool's capability surface.	5 / 5
Completeness	Explicitly answers both what (build telemetrygen commands for synthetic OTLP traces/metrics/logs) and when ('Use for…', 'Also use when…'), with an explicit 'Not for…' negative boundary; clear concrete trigger phrases throughout.	5 / 5
Trigger Term Quality	Embeds natural user phrases quoted verbatim — 'send sample traces to this collector,' 'load-test an OTLP endpoint,' 'generate traffic to verify a processor, OTTL transform, or tail sampling,' 'produce test data for dashboards' — covering the real ways users request this.	5 / 5
Distinctiveness Conflict Risk	Niche is tightly scoped to the telemetrygen tool and the 'Not for application SDK instrumentation or production collection that does not use telemetrygen' clause removes the main overlap risk; minimal conflict with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ollygarden/opentelemetry-agent-skills
Path: skills/otel-telemetrygen/SKILL.md
Commit: c5d2edc

Reviewed: about 3 hours ago

Table of Contents

Discovery Implementation Validation

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.