Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashintel/publishing-packages
Conventions for publishing npm packages from this repository, including when a PR needs a changeset and how to write one.
Passed 19 of 23 test cases with the skill, and 10 of 23 without it.
and 6 more in the full report
9 fixed10 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am about to write a changeset for a patch update in `@hashintel/crypto`. What file inside the `@hashintel/crypto` package directory should I review first to check for package-specific changeset conventions and accepted bump levels?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies `AGENTS.md` as the package-specific configuration file. | Missed | Passed |
The instructions your model reads when the skill loads.
npm-publishable packages in this repository are versioned and released with changesets. The changeset configuration, including which packages are ignored, lives in .changeset/config.json.
A PR that changes an npm-publishable package adds a changeset file under .changeset/. The changeset text becomes the package's published changelog entry, so write it for the package's consumers:
A package's own AGENTS.md can carry further conventions, such as the bump level it accepts; check it before writing the changeset.
test cases passed, vs 10 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.