v1.16.1

1.16.1 - 2026-08-24

If you installed this toolkit from npm rather than cloning it, you could not reach Gold. Now you can.

Do you need to do anything?

Almost certainly not. No check is added, none is removed, the spine stays at 34 and the Standard stays at 0.15. Five plugins were graded before and after this change and not one moved.

The exception is if you were chasing Gold and G2 kept failing. Nothing to change on your side: re-run your pipeline, and a CI file that was already correct should now pass.

The bug

G2 asks for CI that runs the conformance gate. It recognised one way of writing that: node scripts/check.mjs, a path that exists only if you cloned this repository.

Our own install instructions tell you to use npm or the plugin marketplace. Do that, and you have no scripts/ folder at all. The command you can run was the one G2 refused. So Gold was unreachable for anyone who followed the documentation.

G2 now accepts five ways of running the same gate:

• npx agent-skills-toolkit .
• the installed command on its own, if you added the package as a dependency
• an agent-skills-toolkit GitHub Action
• node scripts/check.mjs, if you do vendor the gate
• an npm script that runs any of the above

Installing the package still does not count. Running it is the point.

Nothing about the rules changed. The Standard already asked for CI that runs the suite via the portable scripts, and npx runs exactly those from the published package. Only the checker disagreed with it.

Three more fixes, all in our own guards

• A vendor-claim watcher reported a clean run on a claim nothing could ever check. One mistyped character in a claim's source made it permanently unverifiable while the gate said everything was fine. It is one of five gates that block a release here.
• A parity check treated a corrupt file and a missing file as the same event. They are not: one is a defect, the other is nothing to compare.
• A worked example labelled a rewritten sentence as a direct quote. The page it came from carries a list; the example had flattened it into prose and still called it verbatim.

The documentation got a plain-language pass

Eighty-eight commands across 37 pages did not work for the reader they were written for. They all said node scripts/..., which needs a clone, while the install guide sends you to npm. They now use a command you can actually run.

One page had been false for three months: it told readers to wait for something that had already shipped. And the glossary is now reachable from every section rather than buried in one.

The rules behind those fixes are now built into the skill that writes our documentation, so new pages start from them.