Name: testland/opentelemetry-trace-assertions
Rating: 74.4 (1 reviews)
Author: testland

testland/opentelemetry-trace-assertions

Author trace-shape assertions in tests using OpenTelemetry SDK in-memory exporter - capture spans during test execution, assert on span name + attributes + status + parent-child structure + duration. Cross-language patterns (Python `InMemorySpanExporter` + `SimpleSpanProcessor`, JS `getRecordedSpans()`, Java `OpenTelemetryExtension`); CI integration. Use when a service is instrumented with the OpenTelemetry SDK and downstream alerts, SLOs, or dashboards depend on specific span names or attributes that a refactor could silently drop.

Quality

93%

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

85%

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

A highly actionable, well-structured skill with executable multi-language examples and clear sequencing. Its only weakness is a lightly padded conceptual opening that re-explains OpenTelemetry basics Claude already knows.

Suggestions

Trim the opening concept paragraph that re-defines traces/spans/DAGs — Claude already knows this; lead directly with 'When to use' or the install step.

Reduce repeated 'Per the [docs]' citation preambles; cite once or rely on the References section to cut tokens without losing attribution.

The description promises 'duration' assertions but the body never demonstrates asserting on span duration; either add a duration-assertion snippet or drop 'duration' from the description to avoid an over-claim.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with lean code blocks, but the opening re-explains trace/span DAG concepts Claude already knows ('a trace is the path of a request... a span is a unit of work') and repeats 'Per the [docs]' citations; not 3 because it could be tightened by trimming the conceptual primer, not 1 because the operational guidance is concrete rather than padded.	2 / 3
Actionability	Provides fully executable Python, JS/TS, and Java code plus exact install commands and copy-paste-ready snippets, matching the 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	Steps 1–8 are clearly sequenced (install → exporter setup → shape assertions → structure → semantic conventions → language patterns → CI), and the anti-patterns table plus the deprecation note ('failures during SDK upgrade are the signal that instrumentation needs migrating') supply guardrail and error-recovery feedback.	3 / 3
Progressive Disclosure	No bundle files exist; the single self-contained SKILL.md is well-organized into clear sections with one-level external doc links in the References section, satisfying the well-organized-sections bar for skills needing no external references.	3 / 3
	Total	11 / 12 Passed

Description

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.

A highly specific, complete description with explicit trigger guidance and a clear niche. It uses third-person imperative voice throughout and avoids vague fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'capture spans during test execution, assert on span name + attributes + status + parent-child structure + duration' plus cross-language patterns and CI integration — matching the 'lists multiple specific concrete actions' anchor; not below because it is far more than naming a domain with some actions.	3 / 3
Completeness	Explicitly answers both what ('Author trace-shape assertions... capture spans... assert on...') and when ('Use when a service is instrumented with the OpenTelemetry SDK and downstream alerts, SLOs, or dashboards depend on specific span names or attributes...'), matching the both-what-and-when anchor.	3 / 3
Trigger Term Quality	Uses natural terms the target audience would say — 'OpenTelemetry SDK in-memory exporter', 'spans', 'trace-shape assertions', 'alerts, SLOs, dashboards' — giving good coverage rather than only some relevant keywords.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (OTel in-memory exporter span assertions in tests) with distinct triggers tied to downstream observability dependencies, making conflict with other skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Reviewed

8 days ago

Table of Contents

Discovery Implementation Validation