New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Otel Component Telemetry

by ollygarden in ollygarden/opentelemetry-agent-skills

Scan one OpenTelemetry component at pinned upstream versions and record the telemetry it emits (spans, metrics, logs) as change-point files under skills/otel-telemetry-emissions/.

Apache-2.0Auto-check passedDevOps & Cloud

Install Otel Component Telemetry

skills CLI
$ npx skills add ollygarden/opentelemetry-agent-skills --skill otel-component-telemetry -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ollygarden/opentelemetry-agent-skills otel-component-telemetry --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ollygarden/opentelemetry-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/tools/otel-telemetry-emission-scan .claude/skills/otel-component-telemetry && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
otel-component-telemetry
GitHub stars
106
Token cost
~782 tokens
SKILL.md length
342 words
Files
3 (incl. scripts)
Skills in repo
19
Repo updated
First seen
Licence
Apache-2.0

At a glance

Scan one OpenTelemetry component at pinned upstream versions and record the telemetry it emits (spans, metrics, logs) as change-point files under skills/otel-telemetry-emissions/.

  • Works in 5 steps: Resolve versions. The repo is already… → Get source. Check out each resolved tag… → Ground truth in the code. Analyse the… → …
  • Tasks that involve Observability
  • SKILL.md covers Procedure, Updates and Output
  • Runs Shell scripts from its folder; calls git

What it does

Otel Component Telemetry is an agent skill from ollygarden/opentelemetry-agent-skills. Scan one OpenTelemetry component at pinned upstream versions and record the telemetry it emits (spans, metrics, logs) as change-point files under skills/otel-telemetry-emissions/. Invoked headless by scripts/scan.sh, one agent per component from config.json. Authoring-time only — not shipped.

Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `config.json` and `scripts/scan.sh`).

It sits in DevOps & Cloud, covering Observability. It works with OpenTelemetry. The repository describes itself as: Vendor-neutral OpenTelemetry skills for AI coding agents like Claude Code, Cursor, and Codex, grounded in upstream sources. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Observability

Example prompts

  • “/otel-component-telemetry”

Requirements

  • A Bash shell

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Resolve versions. The repo is already cloned locally at /tmp/otel-component-telemetry/ — do not clone it yourself. Versions to scan is…
  2. Get source. Check out each resolved tag into its own temp directory: git worktree add "$(mktemp -d)" . Never scan a branch — only pinned…
  3. Ground truth in the code. Analyse the instrumentation inside a codebase deeply and identify all emitted instrumentation data points…
  4. Record conditionality. If a signal, metric, or attribute is gated (feature gate, opt-in config, experimental semconv env var), it still…
  5. Apply the skip/force rule, run the self-check, write the file(s).

What it can do on your machine

Read from SKILL.md and the folder at commit 12296db. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Otel Component Telemetry loads about 782 tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 342 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~80
When it runs · the whole SKILL.md, loaded when a task matches
~782

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from ollygarden/opentelemetry-agent-skills at commit 12296db, republished under its Apache-2.0 licence (© ollygarden). 342 words, ~782 tokens.

Download SKILL.mdSave it as .claude/skills/otel-component-telemetry/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
otel-component-telemetry
description
Scan one OpenTelemetry component at pinned upstream versions and record the telemetry it emits (spans, metrics, logs) as change-point files under skills/otel-telemetry-emissions/. Invoked headless by scripts/scan.sh, one agent per component from config.json. Authoring-time only — not shipped.

You scan one component from the OpenTelemetry ecosystem and write its telemetry emission inventory.

Repo: ${Repo} Path: ${Path} Versions to scan: ${Version} Tag prefix: ${TagPrefix} Force: ${Force} Output root: ${OutDir}

Procedure

  1. Resolve versions. The repo is already cloned locally at /tmp/otel-component-telemetry/<repo basename> — do not clone it yourself. Versions to scan is either a count of recent releases or one exact tag. For a count, list that many released versions from git tag. For an exact tag, scan only that tag. When Tag prefix is non-empty, consider only tags beginning with that literal prefix, check out the full tag, and strip the prefix to obtain the version used in frontmatter and the output filename. In monorepos where packages version independently of repo tags and no tag prefix is provided (e.g. opentelemetry-js experimental packages), use the package's own version from its manifest at each release tag, and name files after the package version.

  2. Get source. Check out each resolved tag into its own temp directory: git worktree add "$(mktemp -d)" <tag>. Never scan a branch — only pinned tags.

  3. Ground truth in the code. Analyse the instrumentation inside a codebase deeply and identify all emitted instrumentation data points required to fill the table format below.

  4. Record conditionality. If a signal, metric, or attribute is gated (feature gate, opt-in config, experimental semconv env var), it still gets a row — with the gate named in Notes.

  5. Apply the skip/force rule, run the self-check, write the file(s).

Updates

  • A version whose file already exists is skipped — existence means scanned.
  • If your prompt says force: true, scan it anyway and reconcile: compare our findings with the existing file and edit only rows that are wrong or missing. Do not rewrite the whole file.

Never modify files of other components.

Output

Output one file per scanned version under the output root given above, mirroring repo + path:

${OutDir}/<repo basename>/<path>/v<version>.md

Example: ${OutDir}/opentelemetry-collector-contrib/receiver/kafkareceiver/v0.158.0.md

Follow the below format strictly:

md
---
repo: $repo
path: $path
version: v$version
scope_name: $scope_name
commit_sha: $tag_or_sha
last_verified: $YYYY-MM-DD
---

# $component

## Traces

| Span name | Kind | Attributes | Notes |
|---|---|---|---|

## Metrics

| Metric name | Type | Unit | Attributes | Notes |
|---|---|---|---|---|

## Logs

| Log/event name | Attributes | Notes |
|---|---|---|

## Sources

- $files_consulted

Omit any signal section the component does not emit — never write empty tables. Notes names the gate when emission is conditional, - otherwise.

© ollygarden, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (scripts) in tools/otel-telemetry-emission-scan of ollygarden/opentelemetry-agent-skills.

  • SKILL.md
  • config.json
  • scripts/scan.sh

Open the folder on GitHubat commit 12296db

Compare with similar skills

Otel Component Telemetry next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Otel Component Telemetry compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Otel Component Telemetry this skillollygarden/opentelemetry-agent-skills106—~782Automated safety check: PassApache-2.0
Motel Debugkitlangton/motel298—~2.2kAutomated safety check: PassMIT
Tempsgotempsh/temps831—~2kAutomated safety check: PassApache-2.0
Axiom Metrics Queryopenclaw/clawhub9.5k—~2.6kAutomated safety check: PassMIT
UModel Root Cause Analysisalibaba/UnifiedModel415—~1.9kAutomated safety check: PassCustom licence
Agent Kill Switchvivekchand/clawmetry426—~1.1kAutomated safety check: PassMIT

Similar skills

  • Motel Debug

    kitlangton/motel

    Debug applications with motel, a local OpenTelemetry ingest and query server.

    298 GitHub stars~2.2k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

  • Temps

    gotempsh/temps

    Manage, deploy, operate, and instrument applications with Temps.

    831 GitHub stars~2k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Axiom Metrics Query

    openclaw/clawhub

    Explores and queries OpenTelemetry metrics in Axiom MetricsDB, listing datasets, metrics and tags first and picking the right aggregation for each metric's type.

    9.5k GitHub stars~2.6k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • UModel Root Cause Analysis

    alibaba/UnifiedModel

    Investigates a service incident to its root cause by querying a UModel object graph alongside metrics, logs, topology and recent deployments.

    415 GitHub stars~1.9k tokensUpdated 16 days ago
    DevOps & CloudAuto-check passed

  • Agent Kill Switch

    vivekchand/clawmetry

    Give the human an off switch and a cost meter for the coding agents on this machine, using ClawMetry.

    426 GitHub stars~1.1k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed

  • Agentmeasure

    roy-tong/AgentMeasure

    Check whether agent telemetry preserves measurement semantics.

    219 GitHub stars~753 tokensUpdated today
    DevOps & CloudAuto-check passed

More from ollygarden/opentelemetry-agent-skills

All 19 skills in this repo

  • Otel Collector Builder

    ollygarden/opentelemetry-agent-skills

    Build custom OpenTelemetry Collector distributions with OCB (OpenTelemetry Collector Builder).

    106 GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Otel Go

    ollygarden/opentelemetry-agent-skills

    OpenTelemetry in Go — SDK setup, API surface, breaking changes, contrib instrumentation libraries (otelhttp, otelgrpc, otelmongo), compile-time zero-code instrumentation (otelc), and performance…

    106 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Otel Ottl

    ollygarden/opentelemetry-agent-skills

    OpenTelemetry Transformation Language (OTTL) expert for writing and debugging telemetry transformations in the OpenTelemetry Collector.

    106 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Otel Span Events To Logs Migration

    ollygarden/opentelemetry-agent-skills

    Migrate OpenTelemetry Span Events (AddEvent, RecordException, and language equivalents) to the Logs API following the accepted OTEP 4430 migration plan.

    106 GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Otel Telemetrygen

    ollygarden/opentelemetry-agent-skills

    Build safe, version-pinned telemetrygen commands for synthetic OTLP traces, metrics, and logs.

    106 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Otel Upgrade

    ollygarden/opentelemetry-agent-skills

    Assess OpenTelemetry package and Collector upgrades across ecosystems.

    106 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Otel Component Telemetry

What does Otel Component Telemetry do?

Scan one OpenTelemetry component at pinned upstream versions and record the telemetry it emits (spans, metrics, logs) as change-point files under skills/otel-telemetry-emissions/. Otel Component Telemetry is an agent skill from ollygarden/opentelemetry-agent-skills. Scan one OpenTelemetry component at pinned upstream versions and record the telemetry it emits (spans, metrics, logs) as change-point files under skills/otel-telemetry-emissions/.

When should I use Otel Component Telemetry?

Otel Component Telemetry fits situations like: tasks that involve Observability.

How do I install Otel Component Telemetry in Claude Code?

Run `npx skills add ollygarden/opentelemetry-agent-skills --skill otel-component-telemetry -a claude-code`. Or copy the skill folder (tools/otel-telemetry-emission-scan in ollygarden/opentelemetry-agent-skills) into .claude/skills/otel-component-telemetry in your project. Claude Code loads it when a task matches its description.

How do I install Otel Component Telemetry in Codex?

Run `npx skills add ollygarden/opentelemetry-agent-skills --skill otel-component-telemetry -a codex`. Or copy the skill folder (tools/otel-telemetry-emission-scan in ollygarden/opentelemetry-agent-skills) into .agents/skills/otel-component-telemetry in your project. Codex loads it when a task matches its description.

Can I use Otel Component Telemetry in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ollygarden/opentelemetry-agent-skills --skill otel-component-telemetry -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/otel-component-telemetry, .gemini/skills/otel-component-telemetry, .github/skills/otel-component-telemetry and .opencode/skills/otel-component-telemetry in your project.

What does Otel Component Telemetry need to run?

Going by SKILL.md and its folder, Otel Component Telemetry needs a shell for the scripts in its folder and the command-line tools its instructions call (git). Our summary lists: A Bash shell.

Does Otel Component Telemetry access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Otel Component Telemetry safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Otel Component Telemetry use?

Otel Component Telemetry is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Otel Component Telemetry use?

About 782 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Otel Component Telemetry?

Skills that share tags, products or a category with Otel Component Telemetry: Motel Debug (kitlangton/motel, 298 stars), Temps (gotempsh/temps, 831 stars), Axiom Metrics Query (openclaw/clawhub, 9.5k stars) and UModel Root Cause Analysis (alibaba/UnifiedModel, 415 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Otel Component Telemetry?

ollygarden (a GitHub organization) maintains it in ollygarden/opentelemetry-agent-skills, which has 106 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 10, 2026.

Source: ollygarden/opentelemetry-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.