npm-publishing
Installation
SKILL.md
npm Publishing
Core Rule
Never expose credentials. Do not print, paste, commit, or log npm tokens, .npmrc, .env, OTPs, cookies, recovery codes, or full auth URLs after they are consumed. Prefer verified commands and registry checks over assumptions. If npm prints an auth URL, open it directly for the user when possible, but do not preserve it in commits, docs, or logs.
Use this skill when the user asks to make a repo installable through npm, publish a package, fix npm auth, add trusted publishing, or verify npm installation.
Package Readiness
Inspect the repo before editing:
git status -sb
cat package.json
ls -la
For a CLI package, ensure package.json has the expected basics: