Skip to content
TrustedSkillsbeta
Back to all skills

Npm Publish

Listed
b-open-io·vlatest·backend

This skill automates publishing npm packages to your registry, streamlining deployment and saving development time.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add b-open-io/prompts --skill npm-publish --full-depth -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

b-open-io

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No obfuscated payloads: failed

    Contains 1 obfuscated or encoded payload pattern.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

    What it found

    • modules/dev-ops/skills/npm-publish/.clawnet/unsigned-skill.json:48834-character base64 literal
      "opReturnHex": "6a2231394878696756345179427633744870515663554551797131707a5a56646f4175744df60e2d2d2d0a6e616d653a206e706d2d7075626c6973680a76657273696f6e3a20312…

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Only contacts known or declared hosts: www.npmjs.com, registry.npmjs.org.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    www.npmjs.compackage registryregistry.npmjs.orgpackage registry

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned b-open-io/prompts at 3e198cc712.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
3e198cc712
Manifest
modules/dev-ops/skills/npm-publish/SKILL.md
Scanned
11 files, 904 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The npm-publish skill automates the process of uploading and publishing packages to the npm registry, streamlining the release workflow for Node.js developers. It handles authentication, versioning, and metadata configuration to ensure your libraries are distributed correctly without manual CLI intervention.

When to use it

  • Automating the release of new versions of a library after code changes are committed.
  • Deploying private packages to scoped registries or public npm accounts securely.
  • Managing multiple package releases in a CI/CD pipeline to ensure consistent deployment.
  • Publishing packages with specific tags (e.g., latest, beta) based on semantic versioning rules.

Key capabilities

  • Authenticates with the npm registry using stored credentials or tokens.
  • Reads and validates package.json metadata before upload.
  • Handles file attachments, including tarballs and source code archives.
  • Supports tagging strategies for different release channels.

Example prompts

  • "Publish version 1.2.0 of my 'data-utils' package to npm using the configured registry credentials."
  • "Upload the latest build artifacts for 'api-client' and tag it as 'beta' on the npm registry."
  • "Automatically publish any new packages in the current directory that pass validation checks."

Tips & gotchas

Ensure your AI agent has access to valid npm authentication tokens or API keys, as publishing requires secure identity verification. Always verify that package.json fields like name and version are unique before triggering a publish action to avoid registry conflicts.