Skip to content
Back to search

opentelemetry-agent-skills

SkillGitHubIncomplete

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/ollygarden/opentelemetry-agent-skills with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/ollygarden/opentelemetry-agent-skills'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/ollygarden--opentelemetry-agent-skills/badge.svg)](/listings/ollygarden--opentelemetry-agent-skills)

HTML

<a href="/listings/ollygarden--opentelemetry-agent-skills"><img src="/api/listings/ollygarden--opentelemetry-agent-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

skills.sh

Install all skills:

npx skills add https://github.com/ollygarden/opentelemetry-agent-skills

Or install a single skill by pointing at its folder, e.g.:

npx skills add https://github.com/ollygarden/opentelemetry-agent-skills/tree/main/skills/otel-go

Claude Code

1. Register the repository as a plugin marketplace:

   /plugin marketplace add ollygarden/opentelemetry-agent-skills

2. Install a skill:

   /plugin install <skill-name>@opentelemetry-agent-skills

For example:

   /plugin install otel-go@opentelemetry-agent-skills

Cursor, Codex, GitHub Copilot, and other agents

The `skills` CLI installs into the coding agents it detects. Pass `-a` to choose one, such as `cursor`, `codex`, or `github-copilot`:

npx skills add ollygarden/opentelemetry-agent-skills -a cursor

See the [skills CLI documentation](https://github.com/vercel-labs/skills#supported-agents) for every supported agent.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 107 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "opentelemetry-agent-skills",
  3. "owner": {
  4. "name": "OllyGarden"
  5. },
  6. "metadata": {
  7. "description": "Reusable OpenTelemetry agent skills (language-agnostic and per-language)",
  8. "version": "1.0.0"
  9. },
  10. "plugins": [
  11. {
  12. "name": "otel-collector",
  13. "source": "./skills/otel-collector",
  14. "description": "OpenTelemetry Collector component configuration: config keys, defaults, validation rules, signal support, stability, and gotchas. Progressive disclosure via components/<name>/README.md plus on-demand detail files."
  15. },
  16. {
  17. "name": "otel-collector-builder",
  18. "source": "./skills/otel-collector-builder",
  19. "description": "Building custom OpenTelemetry Collector distributions with OCB: builder manifest authoring, core/contrib/provider version alignment, local component development, CI/Docker/multi-arch builds, and troubleshooting."
  20. },
  21. {
  22. "name": "otel-declarative-config",
  23. "source": "./skills/otel-declarative-config",
  24. "description": "OpenTelemetry declarative YAML configuration for SDK setup (otelconf, OTEL_CONFIG_FILE, file_format). Points at upstream schema, env-var substitution, and configuration precedence."
  25. },
  26. {
  27. "name": "otel-ottl",
  28. "source": "./skills/otel-ottl",
  29. "description": "OpenTelemetry Transformation Language (OTTL) expert for writing and debugging telemetry transformations in the Collector (transform, filter, routing, tail_sampling)."
  30. },
  31. {
  32. "name": "otel-profiles",
  33. "source": "./skills/otel-profiles",
  34. "description": "OpenTelemetry profiles signal and the eBPF profiler: deploying otelcol-ebpf-profiler on hosts and Kubernetes (including kind/k3d), version-pinned receiver keys, exporting OTLP profiles to backends, verification, and troubleshooting."
  35. },
  36. {
  37. "name": "otel-sdk-versions",
  38. "source": "./skills/otel-sdk-versions",
  39. "description": "OpenTelemetry SDK, Collector, configuration schema, semantic conventions, and Weaver release version lookup."
  40. },
  41. {
  42. "name": "otel-semantic-conventions",
  43. "source": "./skills/otel-semantic-conventions",
  44. "description": "OpenTelemetry semantic convention lookup and naming guidance for attributes, groups, and span naming."
  45. },
  46. {
  47. "name": "otel-span-events-to-logs-migration",
  48. "source": "./skills/otel-span-events-to-logs-migration",
  49. "description": "Migrate OpenTelemetry Span Events (AddEvent, RecordException) to the Logs API following the OTEP 4430 deprecation plan."
  50. },
  51. {
  52. "name": "otel-telemetry-emissions",
  53. "source": "./skills/otel-telemetry-emissions",
  54. "description": "Version-pinned inventory of the telemetry (spans, metrics, logs, attributes) emitted by OpenTelemetry collector components and SDK instrumentation packages. Lookup by component and version, including how emission changed across versions."
  55. },
  56. {
  57. "name": "otel-telemetrygen",
  58. "source": "./skills/otel-telemetrygen",
  59. "description": "Construct telemetrygen commands for generating synthetic OpenTelemetry traces, metrics, and logs via OTLP; load-test collectors and validate pipelines."
  60. },
  61. {
  62. "name": "otel-upgrade",
  63. "source": "./skills/otel-upgrade",
  64. "description": "Assess OpenTelemetry package and Collector upgrades across ecosystems, including version selection, dependency compatibility, Collector distributions, configuration, builds, runtime behavior, telemetry changes, and rollout risk."
  65. },
  66. {
  67. "name": "otel-weaver",
  68. "source": "./skills/otel-weaver",
  69. "description": "OpenTelemetry Weaver registry authoring, codegen, and CI enforcement (registry check/generate/diff)."
  70. },
  71. {
  72. "name": "otel-go",
  73. "source": "./skills/otel-go",
  74. "description": "OpenTelemetry in Go: declarative SDK setup with otelconf, API surface, contrib instrumentation libraries (otelhttp, otelgrpc), compile-time zero-code instrumentation (otelc), performance tuning, breaking-change audits."
  75. },
  76. {
  77. "name": "otel-java",
  78. "source": "./skills/otel-java",
  79. "description": "OpenTelemetry in Java: Javaagent zero-code instrumentation, Spring Boot Starter, manual autoconfigure SDK, declarative YAML configuration, BOM dependency management."
  80. },
  81. {
  82. "name": "otel-js",
  83. "source": "./skills/otel-js",
  84. "description": "OpenTelemetry in Node.js / JavaScript / TypeScript: NodeSDK, declarative YAML configuration, auto-instrumentations, ESM vs CJS import patterns."
  85. },
  86. {
  87. "name": "otel-python",
  88. "source": "./skills/otel-python",
  89. "description": "OpenTelemetry in Python: declarative SDK setup (experimental file config), API surface and logging bridge, zero-code instrumentation (opentelemetry-distro / opentelemetry-instrument) and contrib catalog, performance tuning, breaking-change audits."
  90. },
  91. {
  92. "name": "otel-dotnet",
  93. "source": "./skills/otel-dotnet",
  94. "description": "OpenTelemetry in .NET: DI/builder SDK setup (OpenTelemetry.Extensions.Hosting), native BCL instrumentation (ActivitySource, Meter, ILogger), zero-code CLR-profiler agent and contrib instrumentation catalog, performance tuning, breaking-change audits. Note: .NET has no declarative YAML config yet."
  95. },
  96. {
  97. "name": "otel-ruby",
  98. "source": "./skills/otel-ruby",
  99. "description": "OpenTelemetry in Ruby: SDK and Bundler setup, manual tracing, experimental metrics and logs, contrib instrumentation for Rails/Rack/Sinatra/Sidekiq and other gems, propagation, performance, and breaking-change audits."
  100. },
  101. {
  102. "name": "otel-browser",
  103. "source": "./skills/otel-browser",
  104. "description": "OpenTelemetry in the browser (Real User Monitoring / RUM): web tracing SDK (sdk-trace-web, context-zone) and experimental browser-sdk, event- and span-based browser instrumentations (web vitals, navigation, errors, fetch/XHR), sessions, frontend-to-backend trace propagation, bundle size / cost / PII trade-offs."
  105. }
  106. ]
  107. }
README.md · README · 170 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # OllyGarden Agent Skills for OpenTelemetry
  2. [![skills.sh](https://www.skills.sh/b/ollygarden/opentelemetry-agent-skills)](https://www.skills.sh/ollygarden/opentelemetry-agent-skills)
  3. [![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
  4. OllyGarden Agent Skills for OpenTelemetry are open source skills that give coding agents such as Claude Code, Cursor, Codex, and GitHub Copilot accurate, current OpenTelemetry knowledge: SDK setup for Go, Java, JavaScript, Python, .NET, Ruby, and the browser; Collector configuration and OTTL; semantic conventions; and upgrades. They follow the [Agent Skills specification](https://agentskills.io/specification), so they work with any agent that supports it. The full catalog, and how they relate to OllyGarden's opinionated [`skills`](https://github.com/ollygarden/skills) package, is at [ollygarden.com/resources/agent-skills](https://ollygarden.com/resources/agent-skills).
  5. The skills are **non-opinionated by design** — there are many valid ways to use OpenTelemetry, and prescribing conventions is out of scope.
  6. They are designed for **token-efficient, agent-friendly retrieval**: small fetch tables, lookup indexes, and scripts that point at upstream sources of truth instead of copying docs into context. The agent finds what it missed during training; answers stay current as the project evolves.
  7. ## Available Skills
  8. Language-agnostic skills:
  9. | Skill | Path | Use When |
  10. | --- | --- | --- |
  11. | `otel-collector` | `skills/otel-collector/` | Configuring OpenTelemetry Collector components — config keys, defaults, validation, signal support, stability, and gotchas. Progressive disclosure via `components/<type>/README.md` plus on-demand detail files. |
  12. | `otel-collector-builder` | `skills/otel-collector-builder/` | Building custom OpenTelemetry Collector distributions with OCB — authoring the builder manifest, aligning core/contrib/provider versions, local component development, CI/Docker/multi-arch builds, and build troubleshooting. |
  13. | `otel-declarative-config` | `skills/otel-declarative-config/` | Configuring OpenTelemetry SDK providers via a single YAML file (`otelconf`, `OTEL_CONFIG_FILE`, `file_format`). Points at the upstream schema, env-var substitution rules, and configuration precedence. |
  14. | `otel-ottl` | `skills/otel-ottl/` | Authoring or reviewing OTTL statements for `transform`, `filter`, `routing`, and `tail_sampling` processors; debugging OTTL syntax and semantics; transforming traces, metrics, logs, and profiles in the Collector. |
  15. | `otel-profiles` | `skills/otel-profiles/` | Continuous profiling with the OpenTelemetry profiles signal: deploying the eBPF profiler (`otelcol-ebpf-profiler`) on Linux hosts and Kubernetes, including kind/k3d, exporting OTLP profiles to a backend, verifying data arrives, and troubleshooting by error message. |
  16. | `otel-sdk-versions` | `skills/otel-sdk-versions/` | Choosing the latest compatible released OpenTelemetry SDK, package, or component (Collector, configuration schema, semantic conventions, Weaver) version and finding setup docs or examples. |
  17. | `otel-semantic-conventions` | `skills/otel-semantic-conventions/` | Selecting released semantic convention groups, attributes, and span naming rules; checking compliance; looking up exact upstream entries via the bundled query script. |
  18. | `otel-span-events-to-logs-migration` | `skills/otel-span-events-to-logs-migration/` | Migrating instrumentation from the deprecated Span Event API (`AddEvent`, `RecordException`) to the Logs API following the OTEP 4430 deprecation plan. |
  19. | `otel-telemetry-emissions` | `skills/otel-telemetry-emissions/` | Looking up which telemetry (spans, metrics, logs, attributes) a collector component or SDK instrumentation package emits at a specific version, and how emission changed across versions — e.g. when upgrading a component or SDK. |
  20. | `otel-telemetrygen` | `skills/otel-telemetrygen/` | Constructing `telemetrygen` commands for generating synthetic traces, metrics, and logs; load-testing collectors; validating OTTL transforms, tail sampling, and filter rules. |
  21. | `otel-upgrade` | `skills/otel-upgrade/` | Assessing OpenTelemetry package and Collector upgrades across ecosystems, including version selection, dependency compatibility, Collector distributions, configuration, builds, runtime behavior, telemetry changes, and rollout risk. |
  22. | `otel-weaver` | `skills/otel-weaver/` | Authoring an OpenTelemetry Weaver registry, writing Jinja2 templates, generating language bindings, and wiring `weaver registry check`/`generate`/`diff` into CI. |
  23. Language-specific skills:
  24. | Skill | Path | Use When |
  25. | --- | --- | --- |
  26. | `otel-go` | `skills/otel-go/` | OpenTelemetry in Go: declarative SDK setup with `otelconf`, API surface, contrib instrumentation libraries (otelhttp, otelgrpc, etc.), compile-time zero-code instrumentation (`otelc`), performance tuning, and breaking-change audits. |
  27. | `otel-java` | `skills/otel-java/` | OpenTelemetry in Java: Javaagent zero-code instrumentation, Spring Boot Starter, manual autoconfigure SDK, declarative YAML configuration, and BOM dependency management. |
  28. | `otel-js` | `skills/otel-js/` | OpenTelemetry in Node.js / JavaScript / TypeScript: NodeSDK setup, declarative YAML configuration via `@opentelemetry/configuration`, auto-instrumentations, and ESM vs CJS import patterns. |
  29. | `otel-python` | `skills/otel-python/` | OpenTelemetry in Python: declarative SDK setup via file config, API surface and logging bridge, zero-code instrumentation (opentelemetry-distro / opentelemetry-instrument) and contrib catalog, performance tuning, breaking-change audits. |
  30. | `otel-dotnet` | `skills/otel-dotnet/` | OpenTelemetry in .NET: DI/builder SDK setup (`OpenTelemetry.Extensions.Hosting`), native BCL instrumentation (`ActivitySource`, `Meter`, `ILogger`), zero-code CLR-profiler agent and contrib instrumentation catalog, performance tuning, breaking-change audits. |
  31. | `otel-ruby` | `skills/otel-ruby/` | OpenTelemetry in Ruby: SDK and Bundler setup, manual tracing, experimental metrics and logs, contrib instrumentation for Rails/Rack/Sinatra/Sidekiq and other gems, propagation, performance, and breaking-change audits. |
  32. | `otel-browser` | `skills/otel-browser/` | OpenTelemetry in the browser (Real User Monitoring / RUM): web tracing SDK (`sdk-trace-web`, `context-zone`) and experimental `browser-sdk`, event- and span-based browser instrumentations (web vitals, navigation, errors, fetch/XHR), sessions, frontend→backend trace propagation, and bundle-size/cost/PII trade-offs. |
  33. ## Installation
  34. ### skills.sh
  35. Install all skills:
  36. ```bash
  37. npx skills add https://github.com/ollygarden/opentelemetry-agent-skills
  38. ```
  39. Or install a single skill by pointing at its folder, e.g.:
  40. ```bash
  41. npx skills add https://github.com/ollygarden/opentelemetry-agent-skills/tree/main/skills/otel-go
  42. ```
  43. ### Claude Code
  44. 1. Register the repository as a plugin marketplace:
  45. ```
  46. /plugin marketplace add ollygarden/opentelemetry-agent-skills
  47. ```
  48. 2. Install a skill:
  49. ```
  50. /plugin install <skill-name>@opentelemetry-agent-skills
  51. ```
  52. For example:
  53. ```
  54. /plugin install otel-go@opentelemetry-agent-skills
  55. ```
  56. ### Cursor, Codex, GitHub Copilot, and other agents
  57. The `skills` CLI installs into the coding agents it detects. Pass `-a` to choose one, such as `cursor`, `codex`, or `github-copilot`:
  58. ```bash
  59. npx skills add ollygarden/opentelemetry-agent-skills -a cursor
  60. ```
  61. See the [skills CLI documentation](https://github.com/vercel-labs/skills#supported-agents) for every supported agent.
  62. ## Repository Structure
  63. Each skill is a self-contained folder under `skills/`, named to match its `name:` field per
  64. the [agentskills.io specification](https://agentskills.io/specification). Language-specific
  65. skills bundle task-focused references; language-agnostic skills sit alongside them.
  66. ```
  67. skills/
  68. otel-go/
  69. SKILL.md # name: otel-go
  70. references/ # declarative-setup, api, instrumentation-libraries, performance, breaking-changes, compile-time-instrumentation
  71. otel-java/
  72. SKILL.md
  73. references/
  74. otel-js/
  75. SKILL.md
  76. references/
  77. otel-python/
  78. SKILL.md
  79. references/
  80. otel-dotnet/
  81. SKILL.md
  82. references/
  83. otel-ruby/
  84. SKILL.md
  85. references/
  86. otel-browser/
  87. SKILL.md
  88. references/ # setup-sdk, instrumentation, performance
  89. otel-collector/
  90. SKILL.md
  91. components/ # one directory per Collector component (log_dedup, interval, …)
  92. otel-collector-builder/
  93. SKILL.md
  94. references/ # manifest, workflows, troubleshooting
  95. otel-declarative-config/
  96. otel-ottl/
  97. otel-profiles/
  98. SKILL.md
  99. references/ # receiver, kubernetes, nested-containers, backends, troubleshooting
  100. otel-sdk-versions/
  101. otel-semantic-conventions/
  102. otel-span-events-to-logs-migration/
  103. otel-telemetry-emissions/
  104. SKILL.md
  105. <repo>/<path>/ # generated telemetry inventories, one file per version
  106. otel-telemetrygen/
  107. otel-upgrade/
  108. SKILL.md
  109. references/ # dependency and Collector upgrade workflows
  110. otel-weaver/
  111. bin/ # the gates CI runs, runnable locally
  112. validate-skill.sh # Agent Skills spec conformance + house rules
  113. check-skill-inventory.py
  114. skills-ref.requirement # pinned validator revision; the single source
  115. docs/
  116. preferred-workflow.md # how a change moves through this repository
  117. tools/otel-agent-tools/ # Go CLI that generates bundled reference data
  118. tools/otel-telemetry-emission-scan/ # Authoring-time telemetry emission scanner
  119. ```
  120. ## Contributing
  121. Contributions are welcome — including pull requests authored and implemented by AI coding agents. See [CONTRIBUTING.md](CONTRIBUTING.md) for the full guide. The essentials:
  122. - Keep skills DRY. Prefer referencing official docs, examples, and source code that are already maintained instead of copying large amounts of additional knowledge into the skill. There will be exceptions, but the default should be to link or point to the maintained source of truth.
  123. - Design skills to be token efficient. Avoid dumping large files or broad context into a skill when a targeted lookup, focused reference, or small generated artifact will do.
  124. - Stay vendor neutral.
  125. - Skills must conform to the [Agent Skills specification](https://agentskills.io/specification). Check yours with `./bin/validate-skill.sh` and `./bin/check-skill-inventory.py` — the same gates CI runs.
  126. - PRs that add or substantively change a skill must include harness results: the same prompt run on a frontier model without and with the skill, showing the skill helps.
  127. - [`docs/preferred-workflow.md`](docs/preferred-workflow.md) walks a change through the repository end to end, from branch to merge.
  128. - Contributors sign the organization-wide
  129. [OllyGarden CLA](https://github.com/ollygarden/.github/blob/main/CLA.md) on their first pull request.
  130. All participants must follow OllyGarden's
  131. [Code of Conduct](https://github.com/ollygarden/.github/blob/main/CODE_OF_CONDUCT.md).
  132. See [SUPPORT.md](SUPPORT.md) for help and issue routing, and
  133. OllyGarden's organization-wide
  134. [governance policy](https://github.com/ollygarden/.github/blob/main/GOVERNANCE.md) for project roles
  135. and decision making. Report suspected vulnerabilities privately under the inherited
  136. [security policy](https://github.com/ollygarden/opentelemetry-agent-skills/security/policy).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.