validate-plugin
Skill1 starsChanged 47 days agoApache-2.0View on GitHub
Run the local validation suite for the otel-as-code plugin before committing or opening a PR — hook tests, fixture integrity, plugin.json manifest checks, shell syntax, and terraform-validate on every committed snapshot. Covers the GitHub Actions CI checks plus extra local-only sanity.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- grafana/grafana-zabbixtheir own version, first seen Oct 8, 2026
- farzanmrz/meta-devtheir own version, first seen Jul 6, 2026
- langburd/agent-skillstheir own version, first seen Jun 8, 2026
- jpoindexter/theft-kittheir own version, first seen May 20, 2026
- Mintsolester/claude-meistertheir own version, first seen Apr 20, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- grafana/grafana-zabbix★ 2.3ksame name
- langburd/agent-skills★ 4same name
- jpoindexter/theft-kit★ 1same name
- farzanmrz/meta-dev★ 0same name
- Mintsolester/claude-meister★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- otel-backendSkill
- otel-business-attrsSkill
- otel-collectorSkill
- otel-evaluateSkill
- otel-initSkill
- otel-instrumentSkill
- otel-remediateSkill
- otel-uninstrumentSkill
- semconv-disciplineSkill
- new-backendSkill
- business-attr-uxSkill
- collector-topologySkill
- deployment-remediationSkill
- language-maturitySkill
- semconv-disciplineSkill
- terraform-patternsSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Run the project's CI checks locally (plus a couple of local-only sanity checks) and report a concise PASS/FAIL per group plus an overall …
- Very specific: line 24
If the claude CLI isn't available: confirm both .claude-plugin/plugin.json and .claude-plugin/marketplace.json are valid JSON, plugin.json …
- Very specific: line 33
Run the snapshot loop under bash -eo pipefail to match CI semantics (the local shell is zsh, which behaves differently on glob no-match).
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Validate the otel-as-code plugin
Run the project's CI checks locally (plus a couple of local-only sanity checks) and report a concise PASS/FAIL per group plus an overall verdict. On failure, show the failing command's output.
1. Hook tests (CI: lint-hooks)
Iterate every suite under tests/hooks/ — do NOT hardcode the list, so new tests run automatically:
for t in tests/hooks/*.test.sh; do echo "== $t =="; bash "$t" || exit 1; done2. Fixture integrity (CI: validate-fixtures)
- nodejs-greenfield:
package.json,index.js,Dockerfileexist ANDpackage.jsonhas NO@opentelemetrydependency. - python-greenfield:
pyproject.toml,app.py,Dockerfileexist ANDpyproject.tomlhas NOopentelemetrydependency. - nodejs-brownfield:
tracing.jsexists AND still contains the three seeded violations —service.nameas a span attribute,http.method, and un-namespacedorderId— which the lint tests assert against.
3. Plugin manifest & structure (CI: validate-plugin-manifest)
claude plugin validate . --strict— must pass. Validatesplugin.json(metadata-only),marketplace.json, and the auto-discovered components (commands/*.md,agents/*.md,skills/<name>/SKILL.md,hooks/hooks.json).- If the
claudeCLI isn't available: confirm both.claude-plugin/plugin.jsonand.claude-plugin/marketplace.jsonare valid JSON, plugin.json declares NO inline component arrays, and the convention dirs/files exist.
4. Shell sanity (local-only — no CI equivalent)
bash -non everyhooks/*.shandtests/**/*.sh.
5. Terraform snapshots (CI: validate-terraform)
For each tests/snapshots/<vendor>/main.tf.snap:
- Copy it to a temp dir as
main.tf, thenterraform init -backend=false -input=false+terraform validate. terraformis NOT installed locally — download a pinned binary (e.g. 1.7.x fromreleases.hashicorp.com) to a temp path and use that. (CI installs it viahashicorp/setup-terraform.)- Run the snapshot loop under
bash -eo pipefailto match CI semantics (the local shell is zsh, which behaves differently on glob no-match).
Report
One line PASS/FAIL per group (hooks / fixtures / manifest / shell / terraform) and an overall verdict. This is the gate to clear before committing.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

