Opentelemetry
Platform-agnostic OpenTelemetry reference — signal selection (traces/metrics/logs), span design, context propagation (W3C TraceContext), sampling strategies, and OTLP exporter config. Use before writing any OTel instrumentation to get design decisions right. Platform-specific skills (otel-node, cloudflare-workers-otel-utels) layer on top of this.
Install
npx skills add mizchi/skills --skill opentelemetrygit clone --depth 1 https://github.com/mizchi/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/opentelemetry ~/.claude/skills/opentelemetryPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# OpenTelemetry — Core Patterns
JavaScript examples use Node 24+ and the SDK 3.x/API 1.10 generation, checked
on 2026-11-16. SDK 2.x requires API 1.9.x; do not upgrade only the API package.
See the [SDK 3 migration guide](https://github.com/open-telemetry/opentelemetry-js/blob/main/doc/3.x/migration-guide.md)
and the tested example in `otel-node` before choosing package versions.
## Signal Selection
Pick the right signal before writing code:
| Signal | Use for | Cost |
|---|---|---|
| **Traces** | Request lifecycle, latency attribution, distributed causality | High (per-request) |
| **Metrics** | Aggregated counts, rates, histograms — dashboards and alerting | Low (pre-aggregated) |
| **Logs** | Discrete events with context — errors, audit, debug | Medium |
Rule of thumb: metrics answer "how often / how fast", logs answer "what happened", traces answer "why". Don't use traces where metrics suffice.
## Span Design
### Naming convention
```
<verb> <noun> → "fetch user", "send email"
<provider>.<operation> → "db.query", "http.get", "cache.set"
```
Never put variable data (IDs, values) in the span name — use attributes. A span name is a cardinality key in your trace index.
### Attributes
```typescript
span.setAttributes({
"db.system.name": "sqlite",
"db.operation.name": "SELECT",
"db.collection.name": "users",
"user.id": userId, // high-cardinality: OK as attribute, not in name
});
```Details
- Skill name
opentelemetry- Repository
- mizchi/skills
- Path
opentelemetry/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Opentelemetry skill do?
Platform-agnostic OpenTelemetry reference — signal selection (traces/metrics/logs), span design, context propagation (W3C TraceContext), sampling strategies, and OTLP exporter config. Use before writing any OTel instrumentation to get design decisions right. Platform-specific skills (otel-node, cloudflare-workers-otel-utels) layer on top of this.
How do I install the Opentelemetry skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add mizchi/skills --skill opentelemetry. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Opentelemetry popular?
It lives in mizchi/skills, which has 423 GitHub stars and 6 forks.
Related skills
Actions CI Tuning
423mizchi/skills
Use when auditing or improving GitHub Actions workflows for a project. Covers cache setup (npm/pnpm/yarn), job parallelism, shard-based test splitting, artifact handling pitfalls, and Playwright-specific patterns. Trigger on: slow CI, cache miss, flaky shard jobs, merge-reports failures, or an explicit 'tune CI' request.
AI Index
423mizchi/skills
Method and tooling for measuring how AI-generated a piece of prose reads, in Japanese or English. Two layers — a deterministic lint for removable surface tells (scripts/slopscore.py, no API) and a judgment layer of typed probabilistic questions (Jev noul/score) for the tells that survive editing. Includes measured human/AI baselines, a gap-first calibration procedure, and labeled fixtures. Use when building or calibrating an AI-likeness score, or when a draft needs a defensible number rather than a vibe. For writing guidance use natural-writing-ja / natural-writing-en instead.
Apm Usage
423mizchi/skills
Reference for APM manifests, installation, targeted updates, deployment paths and lockfiles. Invoke when the user explicitly asks about APM or apm.yml, or an unfamiliar APM command/error needs exact CLI details. Do not automatically invoke for every project that happens to have installed skills.
Using Medusa Cloud
237medusajs/medusa-agent-skills
Manages Medusa Cloud resources through the Cloud CLI (mcloud). Use when deploying, debugging deployments, managing environments, environment variables, or any Medusa Cloud operation. CRITICAL for mcloud commands, deployment failures, build logs, Cloud setup, and CI/CD workflows.
Mcloud Logs
237medusajs/medusa-agent-skills
Execute mcloud logs to fetch and stream runtime logs for Cloud environments. Use when reading backend or storefront logs, filtering by time range, searching for errors, or scoping logs to a specific deployment.
Utels Project Bootstrap
423mizchi/skills
Register utels.dev projects and deliver returned ingest tokens to Cloudflare Worker secrets through cf without exposing tokens in command arguments or logs.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.