skill-npmpublish

Publish npm packages with private access and patch version increments.

24|26|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/hasna/skills --skill skill-npmpublish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-npmpublish
Source: https://github.com/hasna/skills/tree/main/skills/skill-npmpublish
Command: npx skills add https://github.com/hasna/skills --skill skill-npmpublish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires chalk, commander, ora, semver, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of publishing npm packages by providing sensible defaults, reducing the cognitive load and potential for errors during deployment.

Core Features & Use Cases

  • Private by Default: Automatically sets packages to private, preventing accidental public exposure.
  • Patch Bump by Default: Increments the version by a patch (0.0.1), aligning with common release practices for bug fixes.
  • Use Case: You've just finished a small bug fix for an internal library. Run this skill to publish it as a private package with a patch version bump, ensuring it's ready for use without manual configuration.

Quick Start

Publish the current npm package with default settings for private access and a patch version bump.

Frequently Asked Questions about skill-npmpublish

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

FAQPage Schema
How do I publish an npm package with a default patch version bump?

To publish an npm package with a default patch version bump, this Skill automates the version increment by 0.0.1 and pushes it to the registry. It configures packages as private by default to prevent accidental public exposure.

Do I need an NPM_TOKEN to publish a private package?

Yes, you need a valid NPM_TOKEN to authenticate and publish a private package to the registry. The target directory must also contain a valid package.json file to define the package metadata before publishing.

How can I prevent accidental public exposure when publishing to the npm registry?

You can prevent accidental public exposure by using this Skill, which sets private access configurations automatically by default. This ensures internal libraries remain secure and are not published publicly without explicit manual configuration.

What is the best way to publish a TypeScript CLI package with default settings?

The best way to publish a TypeScript CLI package with default settings is using this Skill, which applies a default patch version increment and private access. It reduces manual configuration errors during deployment for library developers.

Does this npm publish workflow support custom version increments instead of patch bumps?

No, this npm publish workflow applies a default patch version increment of 0.0.1 automatically. It is designed for common bug fix release practices rather than minor or major version updates, ensuring a safe and reliable publishing process.