skills.rest
toilahuongg
toilahuonggCOMMUNITY
Explore all skills by this author →
GitHub

npm-publish

Publish npm packages with dry-runs, scoped public publishing, and post-publish verification.

Updated Aug 23, 2026
Search Tags:#automation#versioning#npm#publish#package.json#nodejs#package
One-click install
npx skills add https://github.com/toilahuongg/Google-Antigravity-Kit --skill npm-publish-toilahuongg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: npm-publish
Source: https://github.com/toilahuongg/Google-Antigravity-Kit/tree/main/.agent/skills/npm-publish
Command: npx skills add https://github.com/toilahuongg/Google-Antigravity-Kit --skill npm-publish-toilahuongg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides developers through publishing packages to the npm registry, addressing the complexities of authentication, package metadata, versioning, and safe release workflows.

Core Features & Use Cases

  • Prerequisites checks: ensure you are authenticated with npm (e.g., via npm whoami) and perform a login if necessary.
  • Package configuration guidance: verify name, version, main/exports, files, and private flags; choose npmignore or files to minimize package size.
  • Versioning and publishing: perform dry-runs, bump versions (patch/minor/major), and support scoped public publishing for first-time releases.
  • Post-publish verification: validate the published version with npm view and push git tags as needed.

Quick Start

Log in to npm, configure package.json, and perform a dry-run publish to validate the package before final release.

Frequently Asked Questions about npm-publish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish an npm package safely without making configuration mistakes?▼

To publish an npm package safely, perform a dry-run to validate package.json fields like name, version, main/exports, and files, and ensure you are authenticated via npm login before executing the final release.

What do I need to configure in package.json before publishing a Node.js package?▼

Before publishing a Node.js package, configure the name, version, main/exports, and private fields in package.json. Use the files array or .npmignore to minimize package size and ensure only necessary files are included in the published version.

Can I publish a scoped npm package publicly for the first time?▼

Yes, you can publish a scoped npm package publicly for the first time. The publishing process supports scoped public publishing, allowing you to release your Node.js package under your namespace while making it accessible to all users on the npm registry.

How do I verify an npm package after publishing a new version?▼

To verify an npm package after publishing a new version, use the npm view command to validate the published version on the registry. You should also push git tags to your repository to maintain version tracking and ensure release consistency.

Why does my npm publish fail even when my package.json is configured?▼

Your npm publish may fail because you are not authenticated with the npm registry. You must run npm whoami to check your login status, and if necessary, execute npm login to authenticate your account before attempting to publish the package.

Related Skills

Explore More Software Engineering Skills→
baekenoughbaekenough
34

npm-publish

Automate npm package publishing with pre-publish validation and dry-run checks.

Community
Advanced
kwt00kwt00

release

Automate Grok plugin releases with version bumps, tests, tags, npm publish, and GitHub releases.

Community
Advanced
yeohj0710yeohj0710

list-npm-package-content

List npm package tarball contents to validate published files.

Community
Intermediate
InneiInnei
32

release-orchestrator

Automate multi-package releases with version bumping, publishing, and downstream updates.

Community
Advanced