Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ruvnet/diag-harness
Kernel-version skew check (ADR-027). Reports manifest surface + manifest kernel + installed kernel + verdict (match/patch-diff/minor-diff/major-diff). Exits 1 on minor/major skew with a copy-pasteable `npm install @metaharness/[email protected]` next step. Exits 2 if no .harness/manifest.json at path.
Passed 19 of 20 test cases with the skill, and 7 of 20 without it.
and 12 more in the full report
14 fixed7 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to check if a harness was generated from the CLI or Web UI. Is this information stored in `package.json` under `generator`, or inside `.harness/manifest.json`?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies meta.surface as the manifest field path. | Missed | Passed |
The instructions your model reads when the skill loads.
Codex skill: kernel-version skew check for a scaffolded harness — the ADR-027 diagnostic UX loop.
Single-question check: does my local @metaharness/kernel match what this harness was scaffolded against? That's the cross-machine compatibility question almost every "this harness doesn't work" support ticket turns out to be.
Reads .harness/manifest.json:
| Field | Source | Meaning |
|---|---|---|
meta.surface | iter 56 | Which surface produced the harness (cli or web-ui) |
meta.kernel_version | iter 58 | The @metaharness/kernel version stamped at scaffold time |
Resolves the local @metaharness/kernel via createRequire rooted at the harness's own package.json (real Node resolution). Computes the skew verdict and prints a copy-pasteable next step.
| Verdict | Exit | Message |
|---|---|---|
match | 0 | PASS kernel versions match exactly |
patch-diff | 0 | WARN patch-level skew (usually safe; may include bugfixes) |
minor-diff | 1 | WARN minor-level skew (new kernel features may be missing) + Run: npm install @metaharness/[email protected] |
major-diff | 1 | FAIL MAJOR skew — APIs may have changed; expect breakage + Run: npm install @metaharness/[email protected] |
no .harness/manifest.json at path | 2 | FAIL no .harness/manifest.json found at this path |
/diag-harness # cwd
/diag-harness path=./my-harness
harness diag # cwd
harness diag ./my-harness # explicit path
harness diag ./my-harness --json # machine-readable for CI
harness diag ./my-harness --bundle # support-ticket JSON (iter 90)
test cases passed, vs 7 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.