Skip to content
TrustedSkillsbeta
Back to all skills

Opentelemetry Instrumentation Extension

Checked
docker·vlatest·devops·MIT

This extension simplifies OpenTelemetry integration by providing pre-built instrumentation for various services, streamlining observability and debugging.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Installs under a different name. Its SKILL.md names it OpenTelemetry Instrumentation Extension, not the name it is listed under, so the command below uses that name.
  1. 1

    Run this in your project

    terminal
    $ npx skills add docker/mcp-gateway --skill "OpenTelemetry Instrumentation Extension" -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

docker

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned docker/mcp-gateway at a34df45d4e.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
a34df45d4e
Manifest
.claude/skills/otel-instrument/SKILL.md
Scanned
1 file, 306 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides OpenTelemetry instrumentation extensions. It allows for the automatic generation of traces and metrics from applications, providing valuable insights into their performance and behavior. This facilitates debugging, monitoring, and optimization efforts within complex systems.

When to use it

  • Debugging Microservices: Identify bottlenecks and errors in distributed microservice architectures by automatically instrumenting calls between services.
  • Performance Monitoring: Track key metrics like latency and throughput for applications and infrastructure components.
  • Observability Enhancement: Improve the overall observability of a system, making it easier to understand its internal workings.
  • Troubleshooting Production Issues: Quickly pinpoint the root cause of production incidents by analyzing automatically generated traces and metrics.

Key capabilities

  • Automatic trace generation
  • Metric collection
  • Instrumentation extensions for OpenTelemetry

Example prompts

  • "Instrument this application with OpenTelemetry."
  • "Generate traces for all HTTP requests in this service."
  • "Show me the latency distribution of database queries."

Tips & gotchas

This skill requires a working OpenTelemetry environment. Ensure that your applications are configured to export telemetry data to a compatible backend (e.g., Prometheus, Jaeger) for effective monitoring and analysis.