npm-publish — community npm-publish, agent-vault-cli, community, ide skills

v1.0.0

About this Skill

Perfect for CI/CD Agents needing automated package publishing to npm using GitHub Actions Guide for bumping package versions and publishing to npm via CI/CD. Use when the user asks about publishing, releasing, version bumping, or deploying to npm.

BnayaZil BnayaZil
[0]
[0]
Updated: 3/9/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
39
Canonical Locale
en
Detected Body Locale
en

Perfect for CI/CD Agents needing automated package publishing to npm using GitHub Actions Guide for bumping package versions and publishing to npm via CI/CD. Use when the user asks about publishing, releasing, version bumping, or deploying to npm.

Core Value

Empowers agents to securely handle credentials and streamline the publishing process using GitHub Actions CI/CD, automating tests on multiple platforms and Node versions, and supporting version tagging with npm version patch, minor, and major commands

Ideal Agent Persona

Perfect for CI/CD Agents needing automated package publishing to npm using GitHub Actions

Capabilities Granted for npm-publish

Automating package publishing to npm with GitHub Actions
Streamlining version tagging and release management with npm version commands
Running tests on multiple platforms and Node versions using GitHub Actions CI/CD

! Prerequisites & Limits

  • Requires GitHub Actions CI/CD setup
  • Limited to npm package publishing
  • Dependent on Node and npm versions

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is npm-publish?

Perfect for CI/CD Agents needing automated package publishing to npm using GitHub Actions Guide for bumping package versions and publishing to npm via CI/CD. Use when the user asks about publishing, releasing, version bumping, or deploying to npm.

How do I install npm-publish?

Run the command: npx killer-skills add BnayaZil/agent-vault-cli/npm-publish. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for npm-publish?

Key use cases include: Automating package publishing to npm with GitHub Actions, Streamlining version tagging and release management with npm version commands, Running tests on multiple platforms and Node versions using GitHub Actions CI/CD.

Which IDEs are compatible with npm-publish?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for npm-publish?

Requires GitHub Actions CI/CD setup. Limited to npm package publishing. Dependent on Node and npm versions.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add BnayaZil/agent-vault-cli/npm-publish. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use npm-publish immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

npm-publish

Install npm-publish, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

NPM Publish Workflow

This project uses GitHub Actions CI/CD to automatically publish to npm when a version tag is pushed.

Quick Publish

bash
1# 1. Bump the version (updates package.json and creates a git tag) 2npm version patch # 0.1.0 -> 0.1.1 3npm version minor # 0.1.0 -> 0.2.0 4npm version major # 0.1.0 -> 1.0.0 5 6# 2. Push to trigger CI/CD 7git push && git push --tags

The CI pipeline will automatically:

  • Run tests on multiple platforms (Ubuntu, macOS) and Node versions (18, 20)
  • Build the project
  • Publish to npm if all tests pass

Version Types

CommandUse WhenExample
npm version patchBug fixes, small updates0.1.0 → 0.1.1
npm version minorNew features, backwards compatible0.1.0 → 0.2.0
npm version majorBreaking changes0.1.0 → 1.0.0

Pre-release Versions

bash
1npm version prerelease --preid=alpha # 0.1.0 -> 0.1.1-alpha.0 2npm version prerelease --preid=beta # 0.1.0 -> 0.1.1-beta.0 3npm version prerelease --preid=rc # 0.1.0 -> 0.1.1-rc.0

Setup (One-time)

Add NPM_TOKEN to GitHub repository secrets:

  1. Generate token at https://www.npmjs.com/settings/[username]/tokens
  2. Add to GitHub repo: Settings → Secrets and variables → Actions → New repository secret
  3. Name: NPM_TOKEN, Value: [your token]

Troubleshooting

CI fails to publish?

  • Verify NPM_TOKEN is set in GitHub secrets
  • Check if version already exists on npm
  • Review GitHub Actions logs

Need to skip CI tests?

  • Not recommended, but you can manually publish: npm publish --access public

Related Skills

Looking for an alternative to npm-publish or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
AI

flags

Logo of vercel
vercel

The React Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Developer