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.

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 you get
• SKILL.md, an offline Node scanner and the 39-rule table with release-note links

See it first
The real output of the bundled example is on getreadystack.com/skills/otel-collector-config-check/ — free, no sign-up, so you see what it finds before you pay.

Install in 30 seconds
Unzip into ~/.claude/skills/, 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 it does not do
It does not start a Collector or validate the full schema; it reads YAML text only.

FAQ
Q: How is this different from asking Claude without the skill?
A: The skill carries a dated rule table and a scanner that reads every file, so Claude quotes the exact date and line instead of guessing from memory.
Q: How do I get the files?
A: In your Whop library after paying: the lesson “otel-collector-config-check.zip”.