The body is lean and code-forward — runnable docker/Python blocks, a port table, and an anti-patterns table — and avoids explaining concepts Claude already knows; the brief prose (e.g. why force_flush is mandatory) directly supports actionability rather than padding, matching the 'every token earns its place' anchor.

Provides copy-paste-ready, executable guidance — a complete `docker run` command, full OpenTelemetry SDK wiring, and a worked test with concrete query params and span/tag assertions — matching the 'fully executable code/commands' anchor.

A clearly sequenced five-step 'How to use' flow with an explicit validation checkpoint (force_flush + brief sleep, labelled 'mandatory') and verification assertions in the worked example; checkpoints are explicit rather than implicit, so it sits above the 'validation gaps' level below.

Overview and worked example stay inline while advanced material (parent-child/duration assertions, full port map, GitHub Actions service, isolation/retention) is split into the verified-existing, one-level-deep references/query-api-and-ci-wiring.md, clearly signaled multiple times — matching the 'clear overview with well-signaled one-level-deep references' anchor.

Lists multiple concrete actions — 'Author integration tests that query Jaeger', '/api/traces?service=X&operation=Y query patterns', and 'span set + parent-child + duration assertions' — plus specific ingest/query ports, matching the 'lists multiple specific concrete actions' anchor.

Explicitly answers both: what ('Author integration tests that query Jaeger for cross-service trace verification...') and when ('Use when verifying that a request produces the expected spans across service boundaries in a running Jaeger backend.'), satisfying the explicit-trigger anchor; not capped at 2 because the 'Use when...' clause is present.

Natural user-facing terms are well covered — 'Jaeger', 'distributed-tracing', 'integration-testing', 'opentelemetry', 'trace-query' (also in metadata keywords) — matching the 'good coverage of natural terms' anchor rather than the 'some keywords but missing variations' level below.

Occupies a clear Jaeger-specific niche (cross-service trace verification against a running Jaeger backend) with distinct triggers unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.