1.18.0 - 2026-09-03
New here? This toolkit checks a library of agent skills - the kind Claude Code and Codex load - against a written standard, and tells you what it meets and what it does not. It runs the same way on your laptop and in CI, and gives the same answer both times, because nothing about the grading involves a model.
What changed for you
| What | Why it matters | |
|---|---|---|
| 📘 | The GitHub Action is documented | It existed before, explained nowhere except a comment in its own config file |
| 🏷️ | It has a clearer name | Agent Skills Toolkit Grader, was Advanced Skill Library Standard Gate. Nothing breaks |
| 📊 | The full result is published | Previously you got a badge. Now you get the whole report |
| ⚖️ | Every grade states its own limits | A tier says the structure matches a standard. It does not say the skills are good |
Do you need to do anything? No. No check was added, changed or removed, so nothing that passed before will start failing. The Standard stays at 0.15 and the check count stays at 34.
Add it to your CI
Two lines in a workflow and every push gets checked. Full guide: run the gate in GitHub Actions.
- uses: actions/checkout@v7
- uses: product-on-purpose/agent-skills-toolkit@v1.18.0
with:
path: .The rename does not affect this. uses: points at the repository, not the display name, so existing workflows keep working untouched.
Read the full result online
These are regenerated automatically on every deploy, so their date and their numbers cannot drift apart.
- The full report - every check, whether it passed, and what to do about the ones that did not
- The same thing as data - if you want to script against it
- The family registry - every plugin in the marketplace, graded together
Where to start
| If you want to | Go here |
|---|---|
| Understand what this is | What the tiers mean |
| Try it without installing anything | Install and run via npm |
| Add it to CI | Run the gate in GitHub Actions |
| Understand a failure | Troubleshoot the gate |
| Know the limits of the claim | What a tier does not certify |
| Read everything | The documentation site |
Under the hood - what we fixed about our own process
Most of this release is the toolkit checking its own work in places it previously could not.
We now test the Action the way you use it. It had shipped broken to everyone twice, because our own CI called the underlying scripts directly and never went through the Action itself. The path you use was the one path nobody tested.
The marketplace report is measured fresh on every deploy rather than being a snapshot someone ran by hand. The old one had gone three weeks stale carrying two claims that were no longer true.
A release can no longer be tagged with broken release notes. The check that catches that used to run after publishing, which is how the previous release went out with a formatting placeholder as its heading.
A monthly job now watches the upstream specification we track. It had existed for several releases and nothing ever ran it.