npm
npm registry ops: login, whoami, names, publish; 1Password tmux.
How do I install this agent skill?
npx skills add https://github.com/steipete/agent-scripts --skill npmIs this agent skill safe to install?
- Gen Agent Trust Hubwarn
The skill manages npm registry operations using 1Password for authentication. It follows security best practices such as log redaction, restricted file permissions, and temporary configuration files. However, it employs dynamic library loading to locate npm-profile across various system paths at runtime, which is a medium-severity finding. Additionally, its handling of external inputs like package names presents a surface for indirect prompt injection.
- Socketwarn
1 alert: gptAnomaly
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
npm
Use for npm registry/account tasks: npm whoami, package availability, package reservation, publish, org checks, and auth debugging.
Auth
- Use
one-passwordfirst for secret rules. - Never run
opdirectly in the shell tool. - Primary item:
npm Registry - steipete - Release AutomationinMolty. - Default to
OP_SERVICE_ACCOUNT_TOKEN; no desktop unlock. The item carries the working registry session (registry_token) plus username/password/TOTP fallback. - Desktop
npmjsfallback is explicit only: pass--account my.1password.comwhen Molty is unavailable and the user wants the fallback. Explicitrelease/publishrequests 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-worktmux session (clawdbot-op.sock; seeone-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.
- All helpers share
scripts/npm-auth.sh: storedregistry_tokensession first, thenscripts/npm-auth-login.mjsregistry login with a fresh six-digit OTP; successful fallback sessions are cached back to the same item. Do not hand-roll field extraction, registry login, or cache writes. - Installed skill directory symlinks are supported. Shell entrypoints resolve physical siblings; sourced
npm-auth.shownsNPM_AUTH_SCRIPT_DIRwithout changing the caller'sSCRIPT_DIRor working directory. Node helpers also support file symlinks, including--preserve-symlinks-main. - Credential selection prefers canonical field
id, thenpurpose, then a unique label; duplicate label-only matches are rejected (legacynpmjsmay retain same-label fields). - For ad-hoc authenticated registry commands, use
scripts/npm-service.sh -- <npm args...>; usepublish-package.shfor a local package. - npm 11 prompt piping is brittle; avoid
printf ... | npm login --auth-type=legacy. - Avoid
expectfor npm login unless necessary; logs can echo prompts and are easy to get wrong. - Prefer the helper's registry API login path (
npm-profileloginCouch) for automation. - If auth shape is ambiguous or
npm whoamifails, stop and ask for the exact field label / credential fix. Do not probe more 1Password items or open another tmux window/session.
Package Publishing
From the package root, inside the same auth tmux window:
/Users/steipete/Projects/agent-scripts/skills/npm/scripts/publish-package.sh
The helper verifies identity, refuses an existing package version, publishes with a fresh OTP, retries one expired OTP, verifies registry visibility with the same temporary npmrc (including restricted packages), and cleans auth files.
Package Reservation
Use scripts/reserve-packages.sh from inside the same tmux window:
/Users/steipete/Projects/agent-scripts/skills/npm/scripts/reserve-packages.sh package-one package-two
What it does:
- reads the Molty release-automation item once via
op - reuses the stored registry session or creates one from username/password/TOTP
- publishes
0.0.0placeholder packages with a generic README - continues after per-package publish failures
- redacts tokens/OTP in logs
- cleans temp npmrc/work dirs
Notes:
- npm may reject names as too similar to already-published names. Treat that as a registry policy result, not an auth failure.
- npm CLI prompt piping is brittle on npm 11. Prefer the helper’s registry API login path over scripted
npm login. - For scoped packages,
npm viewcan lag/404 even when the package exists. Checknpm access get status <pkg>;publicor a publish failure sayingpreviously published versionsmeans the name is reserved.
Offline Regression Tests
From the repo root; synthetic fixtures only, no real 1Password/npm auth. Always use an empty environment (the shell mock checks its environment for token leaks):
test_home="$(mktemp -d)"
(
set -e
trap 'rm -rf "$test_home"' EXIT
env -i HOME="$test_home" PATH="$PATH" node --test skills/npm/scripts/*.test.mjs </dev/null
env -i HOME="$test_home" PATH="$PATH" /bin/bash skills/npm/scripts/npm-auth.test.sh </dev/null
)
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/steipete/agent-scripts/npm">View npm on skillZs</a>