Skip to content
Get packs

npm Registry Operations

Handles npm login checks, package name reservation, and publishing via 1Password-backed auth.

Source Download skill
Repository
steipete/agent-scripts
Stars
7,433
Licence
MIT
Files
12 files

What it does

Once installed, the agent knows how to run npm registry tasks for a specific maintainer account: checking who is logged in, checking whether a package name is free, reserving names with placeholder 0.0.0 packages, and publishing a local package. Credentials are supposed to come from a 1Password item through helper scripts, not typed into the shell, and temporary npm config files are deleted afterwards. The skill is written for one maintainer's setup, with hard-coded paths and item names.

Great for

  • Maintainers of npm packages who use the same 1Password vault layout as the author
  • Developers who want a scripted, auditable way to publish and reserve npm package names
  • Teams studying how to handle registry tokens and OTPs safely in agent workflows

Skip it if

  • Anyone without the matching 1Password item and vault; the helpers stop or fail without it, and the paths point to a specific author's machine
  • Bulk squatting or reserving many package names, since the skill itself is built for placeholder reservations that npm may treat as a policy problem
  • Environments where agents should not hold release credentials, because the skill can publish to a public registry under a real account

Try asking

  • “Check whether the npm package names my-tool and my-tool-cli are available and who I am logged in as”
  • “Publish the package in the current folder to npm using my release account”
  • “Reserve the package names alpha-utils and beta-utils with placeholder versions”
  • “Debug why npm whoami is failing for my registry login”
Step-by-step guide: how to use npm Registry OperationsInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 12 original files, the MIT licence and an attribution note.

    npm.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip npm.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip npm.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Run the offline tests first (node --test and npm-auth.test.sh with an empty environment) to confirm the helpers work before touching real credentials.
  • Edit the hard-coded item name, vault and absolute script paths to match your own setup before relying on it.
  • Always check the package version and target against the repo release before publishing, since publishes cannot be undone on npm.

What's inside

  • scripts/npm-auth-cache.mjs
  • scripts/npm-auth-cache.test.mjs
  • scripts/npm-auth-login.mjs
  • scripts/npm-auth-login.test.mjs
  • scripts/npm-auth.sh
  • scripts/npm-auth.test.sh
  • scripts/npm-cli-test-helpers.mjs
  • scripts/npm-service.sh
  • scripts/publish-package.sh
  • scripts/publish-package.test.sh
  • scripts/reserve-packages.sh
  • SKILL.md

Redistributed unmodified from steipete/agent-scripts under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.