node-release

Automates versioning and npm publishing with no long-lived secrets and no guessed facts. The failures this skill fixes: models wire NPM_TOKEN secrets in 2026, miss that a package's first version can't be published via OIDC, get the trusted-publisher registration subtly wrong (case, filename, indirection), and leave releases half-done when publish fails after tagging.

When NOT to use

• Exports maps, bundling, tarball contents → node-packaging (release assumes its gates already pass).
• Verifying dependencies' provenance → node-supply-chain.
• Test/lint CI → node-ci.

Workflow