CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 strong, safety-conscious skill body: concrete executable examples for all three signals, a gated multi-step construction procedure with validation checkpoints and a final checklist, and a clean two-file reference split. Its only weakness is wordiness in the environment-variable reproducibility section and the deferral of error-recovery loops to the reference file.

Suggestions

Tighten the 'Make environment behavior explicit' section: replace the convoluted 'Documented retention means recording the exact intended values...' sentence with a short direct instruction (e.g., 'Record intended header/compression values; never print inherited values, which may contain credentials'), and state the flags-vs-env-var split once instead of restating it across multiple sentences.

Add a brief inline error-recovery loop for the verification workflow (e.g., 'If a command fails or output is empty, preserve the failure output, fix the command or config, and re-run the known-positive control before concluding') so workflow clarity does not depend on opening references/collector-verification.md.

Consider trimming the pre-response checklist to concrete checkable items or moving it to the end of the verification reference, since its current phrasing partially repeats guidance already given in the safety gate and construction sections.

DimensionReasoningScore

Conciseness

The body is dense with tool-specific facts Claude would not know (rate semantics, parent/child span counting, exporter env-var behavior, version pinning) and avoids general-concept padding, but the "Make environment behavior explicit" section is convoluted and repetitive (e.g., "Documented retention means recording the exact intended values without printing inherited values, which may contain credentials") and could be tightened. Fits anchor 4 (efficient, minor instances that could be trimmed) better than anchor 5.

4 / 5

Actionability

Fully executable, copy-paste-ready commands cover the common cases: three bounded example shapes for traces, metrics, and logs with realistic values; go install and docker pull pins; and a complete docker run example. Numbered construction steps reference exact flags, deferring only exhaustive flag lookup to references/flags.md. Matches anchor 5.

5 / 5

Workflow Clarity

A clear gated sequence exists: authorization/budget gate, a numbered 6-step command construction procedure, verification checkpoints (fresh output directory, wait for Collector readiness, known-positive control, preserve failures, inspect only after flush), and an explicit pre-response checklist. However, error-recovery feedback loops (what to do when a check or command fails) are deferred to references/collector-verification.md rather than stated inline, which is a minor validation gap characteristic of anchor 4 rather than anchor 5's explicit "if errors: fix and re-validate" loop.

4 / 5

Progressive Disclosure

SKILL.md is a well-organized overview holding core command construction, while the full flag reference and the Collector verification workflow live in two real, one-level-deep, well-signaled files (references/flags.md, references/collector-verification.md), each referenced from the body with context about what it contains. Verified both files exist and contain no further nested .md references. Matches anchor 5.

5 / 5

Total

18

/

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.

An exemplary description: it states a concrete, version-pinned capability, gives four natural-language trigger phrases users would actually say, covers parameter-level triggers (transport, TLS, attributes, counts, duration, rate), and closes with an explicit negative boundary. Voice is imperative/consistent with no fluff or over-claims.

DimensionReasoningScore

Specificity

Concrete capability statement ("Build safe, version-pinned telemetrygen commands for synthetic OTLP traces, metrics, and logs") plus comprehensive parameter coverage ("transport, TLS, attributes, counts, duration, or rate") names multiple specific actions with no coverage gaps. Anchor 4 would require minor gaps in coverage, which are absent.

5 / 5

Completeness

Explicitly answers both questions: "what" via the opening capability sentence and "when" via four concrete "Use for..." trigger phrases plus "Also use when choosing...". It even adds a negative boundary ("Not for application SDK instrumentation or production collection that does not use telemetrygen"), matching the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

Quoted trigger phrases are exactly what users would naturally say: "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." This comprehensively covers natural terms across load-testing, verification, and dashboard-data use cases.

5 / 5

Distinctiveness Conflict Risk

A clear niche (the telemetrygen tool specifically) with distinct triggers and an explicit exclusion clause separating it from adjacent OTel skills (SDK instrumentation, production collection). Minimal conflict risk; anchor 4's "minor overlap risk with closely related skills" does not apply given the explicit boundary.

5 / 5

Total

20

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

ollygarden/opentelemetry-agent-skills

Path

skills/otel-telemetrygen/SKILL.md

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.