What problem does it solve? A new npm package cannot be published by trusted-publisher CI because no trusted publisher is registered for a name that does not exist yet, so the first release fails with an E404 and requires a one-time manual publish. ## Core Features & Use Cases - E404 Diagnosis: Distinguishes a first-publish E404 from a missing package or bad build by checking npm view <name> version before changing anything. - Precondition Checklist: Verifies green CI, a successful build, passing tests, and a checked npm publish --dry-run tarball before any manual publish attempt. - Guided Hand-off: Provides the exact four commands (git pull --rebase, npm login, npm publish) to give the package owner, including --access public for scoped packages. - Use Case: A release workflow fails on a brand-new package with an npm publish E404; use this Skill to confirm the cause, run the one-time manual publish, then register the GitHub Actions trusted publisher so CI handles every later release. ## Quick Start Ask the assistant to walk you through the first publish of your new npm package after CI failed with an E404.
