otel-telemetry-emissions SKILL.md skillA
otel-telemetry-emissions from ollygarden/opentelemetry-agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ollygarden/opentelemetry-agent-skills/otel-telemetry-emissions@git:20261016.9671795Pins git:20261016.9671795 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ollygarden/opentelemetry-agent-skills
- Path
skills/otel-telemetry-emissions/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261016.9671795, committed Oct 16, 2026
- First version recorded
- Aug 7, 2026
- Size
- 2,344 bytes
- Repository stars
- 125
- License
- Apache-2.0
Version-pinned inventory of the telemetry (spans, metrics, logs, attributes) emitted by OpenTelemetry collector components and SDK instrumentation packages. Use when working with a covered component — what it emits at a given version, or how emission changed across versions — and when upgrading a component or SDK version, to see the telemetry after the change.
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
# Telemetry Emissions A registry of what telemetry OpenTelemetry components actually emit, pinned to upstream versions. > **Note:** The telemetry emissions in these files were detected by LLM > analysis of the upstream source and may contain errors. Verify against the > component's source or docs before relying on a row for critical decisions. ## Layout ``` <repo basename>/<path in repo>/v<version>.md ``` Example: `opentelemetry-collector-contrib/receiver/kafkareceiver/v0.158.0.md` One file per scanned version. The files in a component directory are its telemetry history; `index.md` lists every file — start there to see what is covered. ## Looking up a component at a version 1. Find the component's directory (or its row in `index.md`). 2. Pick the file matching the target version exactly. 3. If there is no exact match, use the file with the highest version below the target and say the exact version is unverified. 4. If the component or version is not covered at all, say so — do not infer telemetry from semantic conventions. ## What a data file contains Frontmatter (`repo`, `path`, `version`, `scope_name`, `commit_sha`, `last_verified`), then per-signal tables: …
Read the whole file at its exact version.
How to install
mdr add ollygarden/opentelemetry-agent-skills/otel-telemetry-emissions@sha256:7cd51cbee7656fd3The line at the top of this page pins the label git:20261016.9671795, 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_rcsul3ecleyrkgpn)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 7, 2026 and Oct 16, 2026, about one every 35 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261016.9671795 latest | 2026-10-16 | 9671795 | 2,344 B | A | view · diff |
| git:20260815.474f624 | 2026-08-15 | 474f624 | 2,098 B | A | view · diff |
| git:20260807.8ed1478 | 2026-08-07 | 8ed1478 | 2,101 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 (2344 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
ollygarden/opentelemetry-agent-skills · 125 stars · license Apache-2.0 · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rcsul3ecleyrkgpn GET https://markdownregistry.com/api/v1/resolve?ref=ollygarden/opentelemetry-agent-skills/otel-telemetry-emissions GET https://markdownregistry.com/api/v1/blob/7cd51cbee7656fd3235b76d9bfd4f8d58254c486e8aa5f704a3209b8a7ad9308
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.