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

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

An exemplary index/entry-point skill body: lean, well-structured, with a clear routing table, real one-level-deep references, and concrete source-fetch commands. The only gap is that inline code examples are intentionally deferred to the references, which costs one point on actionability.

Suggestions

Consider adding a 3-5 line minimal SDK setup snippet inline in the body so the most common case is actionable without opening a reference file.

The Sources of Truth table could note when to re-fetch (e.g., 're-fetch before recommending a version') so the routing workflow has an explicit refresh checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is a lean index — 'Entry point for OpenTelemetry mechanics in Python services. Load a reference below based on the task' — with no re-explanation of what OpenTelemetry is; the Sources of Truth table is dense (fact + WebFetch command per row) with every token earning its place, matching the score-5 anchor.	5 / 5
Actionability	It gives concrete, copy-paste-ready WebFetch commands ('WebFetch https://pypi.org/pypi/opentelemetry-sdk/json') and an explicit task-to-reference routing table, but the common-case code examples live in the referenced files rather than inline, so it sits at the 'mostly executable, minor gaps' anchor rather than 5.	4 / 5
Workflow Clarity	The single routing action is unambiguous — a 'Use when' column maps each task to one self-contained reference ('each reference is self-contained'), and the skill is read-only so the destructive/batch validation cap does not apply; the simple-skill exception supports the top anchor.	5 / 5
Progressive Disclosure	A concise overview points to five one-level-deep references in a clearly signaled table, all of which exist on disk (declarative-setup.md, api.md, instrumentation-libraries.md, performance.md, breaking-changes.md), with content appropriately split and easy to navigate, matching the score-5 anchor.	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, well-structured description that concretely enumerates capabilities, provides explicit 'Use when' and 'Triggers on' guidance, and stays tightly scoped to OpenTelemetry in Python. It hits the top anchor on all four dimensions with no fluff.

Dimension	Reasoning	Score
Specificity	The description lists seven concrete action areas — 'SDK setup, declarative config, zero-code instrumentation (opentelemetry-instrument, opentelemetry-distro), contrib auto-instrumentation, manual API, performance tuning, breaking changes' — giving comprehensive coverage of the OpenTelemetry-in-Python surface, matching the score-5 anchor rather than the minor-gaps anchor at 4.	5 / 5
Completeness	It explicitly answers both 'what' (the dash-listed capabilities) and 'when' ('Use when configuring or troubleshooting OpenTelemetry in a Python service' plus 'Triggers on ...'), with concrete trigger phrases as the score-5 anchor requires.	5 / 5
Trigger Term Quality	Triggers cover natural user phrasings and synonyms — 'setup otel in python', 'python telemetry', 'python tracing', 'opentelemetry-instrument', 'TracerProvider python', 'MeterProvider python', 'FastAPI/Flask/Django otel', 'python logging bridge' — comprehensive coverage including framework variants, matching the score-5 anchor.	5 / 5
Distinctiveness Conflict Risk	It carves a clear Python-specific niche with distinct, Python-scoped triggers; the only adjacent skill (otel-declarative-config) is language-agnostic per the cross-references, so conflict risk is minimal and the score-5 anchor fits better than 4.	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-python/SKILL.md
Commit: 8e6ed41

Reviewed: 15 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.