Motel Debug
kitlangton/motel
Debug applications with motel, a local OpenTelemetry ingest and query server.
Assess OpenTelemetry package and Collector upgrades across ecosystems.
Install Otel Upgrade
$ npx skills add ollygarden/opentelemetry-agent-skills --skill otel-upgrade -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ollygarden/opentelemetry-agent-skills otel-upgrade --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ollygarden/opentelemetry-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/otel-upgrade .claude/skills/otel-upgrade && rm -rf skills-srcUse ~/.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/
Install the "otel-upgrade" agent skill from https://github.com/ollygarden/opentelemetry-agent-skills/tree/main/skills/otel-upgrade into .claude/skills/otel-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "otel-upgrade", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ollygarden/opentelemetry-agent-skills/tree/main/skills/otel-upgradeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ollygarden/opentelemetry-agent-skills --skill otel-upgrade -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ollygarden/opentelemetry-agent-skills otel-upgrade --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ollygarden/opentelemetry-agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/otel-upgrade .agents/skills/otel-upgrade && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "otel-upgrade" agent skill from https://github.com/ollygarden/opentelemetry-agent-skills/tree/main/skills/otel-upgrade into .agents/skills/otel-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "otel-upgrade", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ollygarden/opentelemetry-agent-skills --skill otel-upgrade -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ollygarden/opentelemetry-agent-skills otel-upgrade --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ollygarden/opentelemetry-agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/otel-upgrade .cursor/skills/otel-upgrade && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "otel-upgrade" agent skill from https://github.com/ollygarden/opentelemetry-agent-skills/tree/main/skills/otel-upgrade into .cursor/skills/otel-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "otel-upgrade", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ollygarden/opentelemetry-agent-skills.git --path skills/otel-upgrade--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ollygarden/opentelemetry-agent-skills --skill otel-upgrade -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ollygarden/opentelemetry-agent-skills otel-upgrade --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ollygarden/opentelemetry-agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/otel-upgrade .gemini/skills/otel-upgrade && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "otel-upgrade" agent skill from https://github.com/ollygarden/opentelemetry-agent-skills/tree/main/skills/otel-upgrade into .gemini/skills/otel-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "otel-upgrade", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ollygarden/opentelemetry-agent-skills otel-upgradeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ollygarden/opentelemetry-agent-skills --skill otel-upgrade -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ollygarden/opentelemetry-agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/otel-upgrade .github/skills/otel-upgrade && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "otel-upgrade" agent skill from https://github.com/ollygarden/opentelemetry-agent-skills/tree/main/skills/otel-upgrade into .github/skills/otel-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "otel-upgrade", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ollygarden/opentelemetry-agent-skills --skill otel-upgrade -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ollygarden/opentelemetry-agent-skills otel-upgrade --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ollygarden/opentelemetry-agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/otel-upgrade .opencode/skills/otel-upgrade && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "otel-upgrade" agent skill from https://github.com/ollygarden/opentelemetry-agent-skills/tree/main/skills/otel-upgrade into .opencode/skills/otel-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "otel-upgrade", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
otel-upgrade- GitHub stars
- 106
- Token cost
- ~1.1k tokens
- SKILL.md length
- 394 words
- Files
- 3 (incl. references)
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Assess OpenTelemetry package and Collector upgrades across ecosystems.
- Works in 7 steps: Inspect the repository and runtime… → Establish the exact current and… → Query authoritative registries and… → …
- Instrumentation
- SKILL.md covers Choose the workflow, Shared instructions and Report
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Otel Upgrade is an agent skill from ollygarden/opentelemetry-agent-skills. Assess OpenTelemetry package and Collector upgrades across ecosystems. Use when choosing or validating API, SDK, instrumentation, exporter, Collector distribution, component, image, chart, Operator, OCB build, or configuration versions, including compatibility, required changes, telemetry and runtime behavior, and rollout risk.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/collector-upgrade.md` and `references/dependency-upgrade.md`).
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
- Instrumentation
- Collector distribution
- Configuration versions
- Including compatibility
Example prompts
- “/otel-upgrade”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Inspect the repository and runtime evidence before choosing the workflow or assuming the ecosystem.
- Establish the exact current and candidate versions. Record wrappers, distributions, artifacts, and embedded dependencies separately rather…
- Query authoritative registries and tagged primary upstream sources for current stable releases. Record the lookup date. Treat release…
- Distinguish the latest available stable release from the highest validated compatible candidate. Do not call a candidate validated when…
- Preserve the user's working tree by validating in a temporary copy, worktree, or equivalent isolated environment. Start with the latest…
- Connect upstream changes to this repository's actual usage and available downstream contracts. Treat unavailable consumers, environments…
- Use applicable specialized skills only when they are available. Otherwise use primary upstream sources and repository evidence, and report…
What it can do on your machine
Read from SKILL.md and the folder at commit 9900032. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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 Upgrade loads about 1.1k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 86 tokens; SKILL.md has 394 words of instructions outside code blocks.
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); files beside SKILL.md are not scanned.
SKILL.md
The full file from ollygarden/opentelemetry-agent-skills at commit 9900032, republished under its Apache-2.0 licence (© ollygarden). 394 words, ~1,056 tokens.
Download SKILL.mdSave it as
.claude/skills/otel-upgrade/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- otel-upgrade
- description
- Assess OpenTelemetry package and Collector upgrades across ecosystems. Use when choosing or validating API, SDK, instrumentation, exporter, Collector distribution, component, image, chart, Operator, OCB build, or configuration versions, including compatibility, required changes, telemetry and runtime behavior, and rollout risk.
OpenTelemetry Upgrade
Find the highest stable target supported by the available repository evidence and provide concise, case-specific upgrade advice. Unless the user asks for implementation, assess the upgrade without changing project files.
Choose the workflow
| Request or repository evidence | Read |
|---|---|
| Package manifests, lockfiles, APIs, SDKs, instrumentation libraries, exporters, plugins, or dependency constraints | Dependency upgrade |
| Collector binaries, images, charts, Operators, configuration, feature gates, components, OCB manifests, builds, or runtime behavior | Collector upgrade |
| A custom Collector involving independently versioned or third-party modules | Read the Collector workflow first, then the dependency workflow for relevant module constraints. |
Read only the applicable reference. Read both when the upgrade crosses both surfaces.
Shared instructions
- Inspect the repository and runtime evidence before choosing the workflow or assuming the ecosystem.
- Establish the exact current and candidate versions. Record wrappers, distributions, artifacts, and embedded dependencies separately rather than treating one version as proof of another.
- Query authoritative registries and tagged primary upstream sources for current stable releases. Record the lookup date. Treat release candidates, beta/alpha packages, nightly artifacts, and untagged source as prereleases unless that package line intentionally publishes with a prerelease identifier; do not silently replace a project's existing experimental package line with a stable package from a different line. If no stable release meets a stated requirement, assess prereleases separately and label them clearly.
- Distinguish the latest available stable release from the highest validated compatible candidate. Do not call a candidate validated when the relevant checks could not run.
- Preserve the user's working tree by validating in a temporary copy, worktree, or equivalent isolated environment. Start with the latest stable candidate. If it fails, diagnose the cause and test selected lower versions when useful; do not assume compatibility is monotonic.
- Connect upstream changes to this repository's actual usage and available downstream contracts. Treat unavailable consumers, environments, and exact-version coverage as unverified.
- Use applicable specialized skills only when they are available. Otherwise use primary upstream sources and repository evidence, and report any resulting verification gaps.
Show full SKILL.md (60 more words)Show less
Dependency resolution, compilation, configuration acceptance, and passing tests establish different and limited kinds of evidence. State exactly what each result demonstrates.
Report
Keep the report concise and tailored to the repository.
## Recommendation
Recommend upgrading `<subject>` from `<current>` to `<target>`, remaining on `<current>`, or deferring the upgrade. Explain the evidence, effort, and risk.
## Relevant Findings
- `<Material finding>` — explain its effect on this repository and any required action.
## Proposed Upgrade Path
Give the smallest coordinated sequence of dependency, artifact, code, configuration, and rollout changes.
## Validation
State the exact candidates, artifacts, configurations, platforms, and checks covered, their results, and what those results demonstrate.
## Remaining Risk
Mention only material behavior, environments, integrations, consumers, or artifacts that could not be verified. Omit this section when no material unverified areas were identified.Link material upstream claims to authoritative release notes, documentation, or source. If the latest available version is not the highest validated compatible version, name both and explain the blocker.
© 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 (references) in skills/otel-upgrade of ollygarden/opentelemetry-agent-skills.
- SKILL.md
- references/collector-upgrade.md
- references/dependency-upgrade.md
Open the folder on GitHubat commit 9900032
Compare with similar skills
Otel Upgrade 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Otel Upgrade this skillollygarden/opentelemetry-agent-skills | 106 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Motel Debugkitlangton/motel | 298 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Tempsgotempsh/temps | 833 | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Axiom Metrics Queryopenclaw/clawhub | 9.5k | — | ~2.6k | Automated safety check: Pass | MIT | |
| UModel Root Cause Analysisalibaba/UnifiedModel | 415 | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Agent Kill Switchvivekchand/clawmetry | 426 | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Temps
gotempsh/temps
Manage, deploy, operate, and instrument applications with Temps.
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.
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.
Agent Kill Switch
vivekchand/clawmetry
Give the human an off switch and a cost meter for the coding agents on this machine, using ClawMetry.
Agentmeasure
roy-tong/AgentMeasure
Check whether agent telemetry preserves measurement semantics.
More from ollygarden/opentelemetry-agent-skills
All 20 skills in this repoOtel Collector Builder
ollygarden/opentelemetry-agent-skills
Build custom OpenTelemetry Collector distributions with OCB (OpenTelemetry Collector Builder).
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…
Otel Ottl
ollygarden/opentelemetry-agent-skills
OpenTelemetry Transformation Language (OTTL) expert for writing and debugging telemetry transformations in the OpenTelemetry Collector.
Otel Profiles
ollygarden/opentelemetry-agent-skills
OpenTelemetry profiles signal and the eBPF profiler (otelcol-ebpf-profiler, profiling receiver).
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.
Otel Telemetrygen
ollygarden/opentelemetry-agent-skills
Build safe, version-pinned telemetrygen commands for synthetic OTLP traces, metrics, and logs.
Related
Works with
Categories
Questions about Otel Upgrade
What does Otel Upgrade do?
Assess OpenTelemetry package and Collector upgrades across ecosystems. Otel Upgrade is an agent skill from ollygarden/opentelemetry-agent-skills. Assess OpenTelemetry package and Collector upgrades across ecosystems.
When should I use Otel Upgrade?
Otel Upgrade fits situations like: instrumentation; collector distribution; configuration versions; including compatibility.
How do I install Otel Upgrade in Claude Code?
Run `npx skills add ollygarden/opentelemetry-agent-skills --skill otel-upgrade -a claude-code`. Or copy the skill folder (skills/otel-upgrade in ollygarden/opentelemetry-agent-skills) into .claude/skills/otel-upgrade in your project. Claude Code loads it when a task matches its description.
How do I install Otel Upgrade in Codex?
Run `npx skills add ollygarden/opentelemetry-agent-skills --skill otel-upgrade -a codex`. Or copy the skill folder (skills/otel-upgrade in ollygarden/opentelemetry-agent-skills) into .agents/skills/otel-upgrade in your project. Codex loads it when a task matches its description.
Can I use Otel Upgrade 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-upgrade -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-upgrade, .gemini/skills/otel-upgrade, .github/skills/otel-upgrade and .opencode/skills/otel-upgrade in your project.
What does Otel Upgrade need to run?
SKILL.md names no scripts, command-line tools or credentials: Otel Upgrade is instructions for the agent only.
Does Otel Upgrade access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Otel Upgrade 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. Review the folder before installing.
What licence does Otel Upgrade use?
Otel Upgrade 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 Upgrade use?
About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.6k tokens, read only when the agent opens those files.
What are the alternatives to Otel Upgrade?
Skills that share tags, products or a category with Otel Upgrade: Motel Debug (kitlangton/motel, 298 stars), Temps (gotempsh/temps, 833 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 Upgrade?
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 11, 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.