CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

otel-python

OpenTelemetry in Python — SDK setup, declarative config, zero-code instrumentation (opentelemetry-instrument, opentelemetry-distro), contrib auto-instrumentation, manual API, performance tuning, breaking changes. Use when configuring or troubleshooting OpenTelemetry in a Python service. Triggers on "setup otel in python", "python telemetry", "python tracing", "opentelemetry-instrument", "opentelemetry-distro", "TracerProvider python", "MeterProvider python", "FastAPI/Flask/Django otel", "python logging bridge".

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

The body is an exemplary progressive-disclosure hub: lean, unpadded, with a well-signaled reference table, concrete source-of-truth fetch commands, and lateral-only cross-links. It falls short of top marks on actionability and workflow clarity because it is pure indirection — no substantive guidance is inlinable without opening a reference — and the pinned version numbers and verification date will age.

Suggestions

Move the pinned version numbers and the 'verified 2026-10-25' date out of the Sources of Truth table into the relevant references (or a clearly dated verification note) so the hub body stays evergreen.

Add one line stating how to handle a task that spans multiple references (e.g., zero-code instrumentation plus performance tuning), or which reference takes precedence when several 'Use when' rows match.

Inline one or two immediately usable commands for the most common case (e.g., an opentelemetry-instrument quick start) so the hub can answer the simplest tasks without requiring a reference load.

DimensionReasoningScore

Conciseness

Quotes: "Entry point for OpenTelemetry mechanics in Python services. Load a reference below based on the task; each reference is self-contained." — a lean hub page with zero padding or explanation of concepts Claude already knows. Not 5: time-sensitive pins like "released 1.45.1 overview; verified 2026-10-25" and "Contrib CHANGELOG through 0.66b1" will go stale and are not placed in a deprecated/old-patterns section, which the guidelines penalize even though the pinned URLs are functional.

4 / 5

Actionability

Quotes: "WebFetch https://pypi.org/pypi/opentelemetry-sdk/json" (`.info.version`)" and a References table with a concrete "Use when" column — copy-paste-ready fetch commands and unambiguous routing. Not 5: all substantive how-to guidance is delegated to the references, so the body alone answers no task end-to-end; not 3: the commands and routing present are fully executable, not pseudocode or high-level hints.

4 / 5

Workflow Clarity

Quotes: "Load a reference below based on the task; each reference is self-contained" plus the use-when table and "For YAML schema details, fetch the upstream sources listed in the otel-declarative-config skill" — the routing sequence is clear and no validation is needed (no destructive/batch operations). Not 5: there is minor routing ambiguity — a task spanning multiple references (e.g., zero-code instrumentation plus performance tuning) has no stated precedence, and guidance is split across two tables and three cross-referenced skills.

4 / 5

Progressive Disclosure

Quotes: the References table mapping each of five real files (all verified present in references/) to a use case, and "each reference is self-contained" — a clear overview with well-signaled, one-level-deep references. References cross-link only to siblings in the same directory (e.g., "see [api.md](api.md#attributes)"), never nesting 2+ levels, so navigation is easy and content is appropriately split.

5 / 5

Total

17

/

20

Passed

Description

96%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 description: it names concrete capabilities with specific tool names, gives an explicit 'Use when' clause plus a comprehensive trigger-phrase list, and scopes itself clearly to Python. The only residual risk is overlap with closely related sibling OTel skills (declarative config schema, version selection), which the description does not explicitly fence off.

DimensionReasoningScore

Specificity

Quotes: "SDK setup, declarative config, zero-code instrumentation (opentelemetry-instrument, opentelemetry-distro), contrib auto-instrumentation, manual API, performance tuning, breaking changes" — multiple specific concrete capabilities with named tools, comprehensively covering the domain. Not 4: coverage is comprehensive rather than having minor gaps.

5 / 5

Completeness

Quotes: what — the full capability list ("SDK setup, declarative config, zero-code instrumentation..."); when — "Use when configuring or troubleshooting OpenTelemetry in a Python service" plus an explicit "Triggers on..." clause with concrete phrases. Both questions are answered explicitly; matches the anchor-5 good example structure. Not 4: the 'when' is fully explicit, not merely present.

5 / 5

Trigger Term Quality

Quotes: "setup otel in python", "python telemetry", "python tracing", "opentelemetry-instrument", "opentelemetry-distro", "TracerProvider python", "MeterProvider python", "FastAPI/Flask/Django otel", "python logging bridge" — comprehensive natural phrasings users would actually say, spanning task-level, tool-level, and framework-level variants. Not 4: few natural terms are missing.

5 / 5

Distinctiveness Conflict Risk

Quotes: "OpenTelemetry in Python" and "in a Python service" — a clear language-specific niche. Not 5: sibling OTel skills exist (the body references otel-declarative-config, otel-sdk-versions, otel-semantic-conventions), and declarative-config or version-selection questions could route to those siblings since the description draws no boundary; this is the anchor-4 'minor overlap risk with closely related skills'. Not 3: the Python scoping is far stronger than 'somewhat specific'.

4 / 5

Total

19

/

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-python/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.