trace-spec-author SKILL.md skillA
trace-spec-author from testland/qa is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add testland/qa/trace-spec-author@v1.1.8Pins v1.1.8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- testland/qa
- Path
plugins/qa-distributed-tracing/skills/trace-spec-author/SKILL.md- Versions recorded
- 5
- Latest version
- v1.1.8, committed Oct 11, 2026
- First version recorded
- Jul 18, 2026
- Size
- 8,189 bytes
- Repository stars
- 11
- License
- MIT
Build a trace specification document per feature - defines the trace shape (root span + child spans + key attributes per OpenTelemetry semantic conventions) that production code MUST emit. The spec drives both implementation reviews AND trace-assertion tests, so a single declarative document is the source of truth for what observability "looks like" for a feature. Use before instrumenting a new feature, when existing spans have grown organically with no agreed shape, or after an incident where…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# trace-spec-author Builds a per-feature trace specification document. The spec is canonical input for: (a) implementation review during code review, (b) trace-shape regression tests via `opentelemetry-trace-assertions` and `jaeger-trace-tests`, (c) onboarding for new team members. ## When to use - Starting observability for a new feature. - Auditing existing instrumentation that grew organically. - Pre-incident-review prep (spec gaps explain why a debugging session was painful). ## Step 1 - Spec template Save under `docs/observability/<feature>.md`: ```markdown # Trace Spec: <Feature> **Owner:** team-checkout **Status:** active | draft | deprecated **Last reviewed:** YYYY-MM-DD **Implementations:** orders-svc 1.4+, payments-svc 2.1+ ## Root span | Field | Value | |---|---| | name | `order.create` | | kind | `INTERNAL` | | status semantics | OK on 2xx, ERROR on 4xx + 5xx | ### Required attributes | Attribute | Type | Source | Notes | |---|---|---|---| | `order.id` | string | UUID v4 | | | `order.item_count` | int | int.between(1, 1000) | | | `customer.id` | string | low-cardinality hash, never PII | | ## Child spans ### `db.query` (when persisting order) …
Read the whole file at its exact version.
How to install
mdr add testland/qa/trace-spec-author@sha256:21c2f56871141a8bThe line at the top of this page pins the label v1.1.8, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_3bk6svcgja24lmgc)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 18, 2026 and Oct 11, 2026, about one every 21 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1.8 latest | 2026-10-11 | a1bd3f7 | 8,189 B | A | view · diff |
| git:20260724.d4db756 | 2026-07-24 | d4db756 | 8,170 B | A | view · diff |
| git:20260719.53f73b7 | 2026-07-19 | 53f73b7 | 8,306 B | A | view · diff |
| git:20260719.6226ac1 | 2026-07-19 | 6226ac1 | 8,118 B | A | view · diff |
| git:20260718.ab29907 | 2026-07-18 | ab29907 | 8,132 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8189 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
testland/qa · 11 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3bk6svcgja24lmgc GET https://markdownregistry.com/api/v1/resolve?ref=testland/qa/trace-spec-author GET https://markdownregistry.com/api/v1/blob/21c2f56871141a8ba86e7d8648adf2448d6aee3eb20848c6d2e286c3cd8c6028
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.