Claude Code skills · updated 2026-10-03

OTel Collector config skill for Claude Code — removed components, renamed keys

Find Collector config lines a current Collector rejects or silently ignores

On the bundled sample: 25 findings (20 errors, 5 warnings) in 1 file from 39 rules, including the jaeger and logging exporters, memory_ballast and http.method.

Get it on Whop - $12 onceGet it on Gumroad

Who it's for

For platform and SRE teams moving an older OpenTelemetry Collector gateway to a current Collector image or Helm chart.

What breaks, and when

The jaeger exporters went in contrib v0.86.0, memory_ballast in v0.109.0, the logging exporter in v0.111.0: an old config stops the Collector starting, and http.method rules silently match nothing.

What it printed on the bundled example

== OpenTelemetry Collector Config Lint — 25 findings (20 errors, 5 warnings) in 1 file · 39 rules
  WARN  otel-sample.yaml:1  [svc-name-absent]
        No service.name resource attribute anywhere in this config: telemetry that arrives without one is bucketed under unknown_service and is unfindable in the backend.
  ERROR otel-sample.yaml:13  [recv-jaeger-remote-sampling]
        remote_sampling was removed from the jaeger receiver (deprecated in contrib v0.84.0, gate removed in v0.153.0); move it to the jaegerremotesampling extension.
  WARN  otel-sample.yaml:15  [recv-opencensus-deprecated]
        The opencensus receiver is deprecated; point OpenCensus senders at an otlp receiver or a bridge.
  ERROR otel-sample.yaml:23  [attr-http-method]
        http.method was renamed to http.request.method when the HTTP semantic conventions went stable; a rule keyed on the old name silently matches nothing once the SDK is upgraded.

What you get

• SKILL.md, an offline Node scanner and the 39-rule table with release-note links
• file:line, severity and the release that removed each component
• The stable attribute name or replacement, applied only after you agree
• CI: node scripts/scan.js . exits 1 on any error

Install

Unzip into ~/.claude/skills/ (all projects) or your-repo/.claude/skills/ (one repo), then ask Claude Code: "We're upgrading our OpenTelemetry Collector to the latest release next sprint. Will the collector config in this repo still work? Don't edit anything yet.". Needs Node 16+.

unzip otel-collector-config-check.zip -d ~/.claude/skills/

Ask Claude

“We're upgrading our OpenTelemetry Collector to the latest release next sprint. Will the collector config in this repo still work? Don't edit anything yet.”

What it does not do

It does not start a Collector or validate the full schema; it reads YAML text only. No network calls, no edits without your OK.

FAQ

What is a Claude Code skill?

A folder with a SKILL.md and scripts that Claude Code loads when your request matches it. You ask in plain words and Claude runs the scanner the skill carries.

How is this different from asking Claude without the skill?

The skill carries a dated rule table and a scanner that reads every file, so Claude quotes the exact date and line instead of answering from memory.

Does it send my code anywhere?

It does not start a Collector or validate the full schema; it reads YAML text only. No network calls, no edits without your OK.

How do I install it?

Unzip into ~/.claude/skills/ (all projects) or your-repo/.claude/skills/ (one repo), then ask Claude Code: "We're upgrading our OpenTelemetry Collector to the latest release next sprint. Will the collector config in this repo still work? Don't edit anything yet.". Needs Node 16+.

What do I get when I buy?

The zip. On Whop it is in your library as a download lesson with the zip attached; on Gumroad it is the product file.