Dash0 Agent Skills
Four OpenTelemetry skills covering application instrumentation, semantic conventions, the Collector and the OTTL language.
- 102 ★ on the repository
- Last commit
- Apache-2.0
Minimal access
Why this level
- The skills contain instructions and reference rules; they run nothing and connect to nothing on their own.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/dash0-agent-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skills contain instructions and reference rules; they run nothing and connect to nothing on their own.
This is third-party code. Review the repository files before installing.
What it does
Four Dash0 skills teach an agent to work with OpenTelemetry without tying it to one backend. The otel-instrumentation skill guides SDK setup for Node.js, Go, Python, Java, Scala, .NET, Ruby, PHP, the browser and Next.js. The otel-semantic-conventions skill suggests attribute and span names. The otel-collector skill covers receivers, processors, exporters and deployment layouts. The otel-ottl skill helps write and debug expressions that transform, filter and redact telemetry. The agent picks the skills up when a task matches their descriptions and produces standard OTLP that any compatible backend accepts.
Who it is for. Backend developers and SREs adding traces, metrics and logs to services with Claude Code, Cursor or Codex.
Good fit when
- A service needs traces, metrics and logs, and the team chose OpenTelemetry.
- Spans show up as separate roots instead of one connected trace.
- The telemetry bill grows because of high-cardinality metrics.
- A Collector pipeline of receivers, processors and an exporter has to be assembled.
- An OTTL expression has to hide card numbers in log bodies.
Not a fit when
- Telemetry comes from a vendor proprietary agent without OpenTelemetry.
- You need a dashboard or alerts in a specific backend: the skills describe code and configuration.
- The project uses a language outside the SDK list: the set has no ready rules for Rust or Elixir.
Example request
Add OpenTelemetry to my FastAPI service and check the HTTP span attributes against the semantic conventions.Limitations
The skills supply rules and examples, while the agent makes the code and configuration edits, so review changes before committing. The SDK rules cover Node.js, Go, Python, Java, Scala, .NET, Ruby, PHP, the browser and Next.js. Some rules, such as derived attributes and convention upgrades, belong to the Dash0 backend. `npx skills add` with `--all` installs all four skills, and `--skill` picks one. Claude Code is easiest with the plugin from the dash0hq/claude-marketplace marketplace, while Cursor, Codex and Copilot clone the repository into a skills directory.
How to disable. Remove the otel-instrumentation, otel-semantic-conventions, otel-collector and otel-ottl skills from the agent skills directory or disable the plugin in Claude Code.
FAQ
How do I install the Dash0 skills in Claude Code?
Run `/plugin marketplace add dash0hq/claude-marketplace`, then `/plugin install dash0-agent-skills@dash0`. The universal option for any agent with the Agent Skills format is `npx skills add https://github.com/dash0hq/agent-skills --all`.
Do I need a Dash0 account?
No. The skills are built around the OpenTelemetry specification and suit any backend that supports OTLP.
Which skills are included?
Four: otel-instrumentation, otel-semantic-conventions, otel-collector and otel-ottl. Each sits in its own skills folder with a SKILL.md file and a rules directory.
Can the skills run in CI?
Yes. The repository has a GitHub Actions example: an `npx skills add` step and a `claude -p` call with the Read, Grep and Glob tools to review instrumentation in a pull request.
Which languages have instrumentation rules?
Node.js, Go, Python, Java, Scala, .NET, Ruby, PHP, the browser and Next.js. For Next.js the rules cover the App Router and common full-stack pitfalls.
Discussion
No questions or reviews yet.
Related
SkillsSkill configures OpenTelemetry: collectors, sampling, security and telemetry from AI agents, without flooding the context.
OpenTelemetry Agent Skills helps agents instrument applications, configure Collector and check versions against primary sources.
Official Datadog skills: monitors, logs, APM, cloud integrations, RUM and LLM observability from inside the agent
Official Dynatrace skills for agents: DQL, traces, logs, Kubernetes, cloud and security work inside Claude Code and Cursor.
A skill set for website performance and scalability, currently holding ooda-loop: observe, orient, decide, act.
The official Grafana skill set: PromQL, Loki, Tempo, Alloy, k6, dashboards and alerting for Claude Code, Cursor and Codex
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Dash0 Agent Skills (this card) | no | 102 | |
| OpenTelemetry Agent Skills by OllyGarden | no | 126 | helps wire up telemetry and check versions against primary sources; the Dash0 set splits the work into instrumentation, conventions, Collector and OTTL |
| otelyssey | no | 126 | an OpenTelemetry plugin marketplace; this is four ready-made skills from one vendor |
README in short
The skills follow the Agent Skills format and rely on the OpenTelemetry specification and the Instrumentation Score. The repository includes a CLAUDE.md template for applying the skills and the @dash0/agent-skills npm package, which ships the skills directories without code.
README badge
Original SKILL.md
--- name: 'otel-instrumentation' description: Configures trace spans, defines custom metrics, sets up log exporters, and optimizes sampling strategies for OpenTelemetry instrumentation. Use when instrumenting applications with traces, metrics, or logs. Triggers on requests for observability, telemetry, tracing, metrics collection, logging integration, or OTel setup. license: Apache-2.0 metadata: author: dash0 version: '2.0.0' workflow_type: 'advisory' supports-traces: "true" supports-metrics: "true" supports-logs: "true" --- # OpenTelemetry Instrumentation Guide Expert guidance for implementing high-quality, cost-efficient OpenTelemetry telemetry. ## Rules & Quick Reference | Use Case / Rule | Description | |-----------------|-------------| | [telemetry](./rules/telemetry.md) | **Entrypoint** — signal types, correlation, and navigation | | [resolve-values](./rules/resolve-values.md) | Resolving configuration values from the codebase | | [verify-dependencies](./rules/verify-dependencies.md) | Verifying instrumentation packages and versions exist before adding them | | [resources](./rules/resources.md) | Resource attributes — service identity and environment | | [k8s](./rules/platforms/k8s.md) | Kubernetes deployment — downward API, pod spec | | [spans](./rules/spans.md) | Spans — naming, kind, status, and hygiene | | [logs](./rules/logs.md) | Logs — structured logging, severity, trace correlation | | [metrics](./rules/metrics.md) | Metrics — instrument types, naming, units, cardinality | | [sensitive-data](./rules/sensitive-data.md) | Sensitive data — PII prevention, sanitization, redaction | | [capture-database-query-parameters](./rules/capture-database-query-parameters.md) | Prepared-statement parameter capture per language (Java, .NET, Python, Node.js, Go) | | [validation](./rules/validation.md) | Telemetry validation — post-deployment verification checklist | | [nodejs](./rules/sdks/nodejs.md) | Node.js instrumentation setup | | [go](./rules/sdks/go.md) | Go instrumentation setup | | [python](./rules/sdks/python.md) | Python instrumentation setup | | [java](./rules/sdks/java.md) | Java instrumentation setup | | [scala](./rules/sdks/scala.md) | Scala instrumentation setup | | [dotnet](./rules/sdks/dotnet.md) | .NET instrumentation setup | | [ruby](./rules/sdks/ruby.md) | Ruby instrumentation setup | | [php](./rules/sdks/php.md) | PHP instrumentation setup | | [browser](./rules/sdks/browser.md) | Browser instrumentation setup | | [nextjs](./rules/sdks/nextjs.md) | Next.js full-stack instrumentation (App Router) | ## Official documentation - [OpenTelemetry Documentation](https://opentelemetry.io/docs/) - [Semantic Conventions](https://opentelemetry.io/docs/specs/semconv/) - [Dash0 Integration Hub](https://www.dash0.com/hub/integrations) ## Getting started