Individual skill
npm
npm registry ops: login, whoami, names, publish; 1Password tmux.
skills/npm/SKILL.md
Source commit d210c0a77c8f9ae5e1d939b13238a75e87cdb69a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 2, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 7,470
- Repository last updated
- Oct 30, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- engineering Derived category
Declared tags are partial or unavailable.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,592 bytesSKILL.mdcore · 4,592 bytesSKILL.mdcore · 4,592 bytesSKILL.mdcore · 4,592 bytesscripts/npm-auth-cache.mjsruns · 2,594 bytesscripts/npm-auth-cache.test.mjsruns · 3,167 bytesscripts/npm-auth-login.mjsruns · 3,681 bytesscripts/npm-auth-login.test.mjsruns · 1,574 bytesscripts/npm-auth.shruns · 4,800 bytesscripts/npm-auth.test.shruns · 4,422 bytesscripts/npm-cli-test-helpers.mjsruns · 3,869 bytesscripts/npm-service.shruns · 2,643 bytesscripts/publish-package.shruns · 3,737 bytesscripts/publish-package.test.shruns · 5,265 bytesscripts/reserve-packages.shruns · 4,591 bytes
Read excerpt
# npm
Use for npm registry/account tasks: `npm whoami`, package availability, package reservation, publish, org checks, and auth debugging.
## Auth
- Use `one-password` first for secret rules.
- Never run `op` directly in the shell tool.
- Primary item: `npm Registry - steipete - Release Automation` in `Molty`.
- Default to `OP_SERVICE_ACCOUNT_TOKEN`; no desktop unlock. The item carries the working registry session (`registry_token`) plus username/password/TOTP fallback.
- Desktop `npmjs` fallback is explicit only: pass `--account my.1password.com` when Molty is unavailable and the user wants the fallback. Explicit `release`/`publish` requests are consent for its unlock prompt.
- Stop and ask if the item is missing, the account/vault is ambiguous, credentials are malformed, npm denies package access, or the requested package/version does not match the repo release target.
- Run npm auth work inside one task window of the shared `op-work` tmux session (`clawdbot-op.sock`; see `one-password`). Reuse the window on failure; kill it when the npm task is done. Never mint an npm-specific socket or session.
- Keep npm auth in a temp npmrc; delete it after the command.