How do I install the Bun Publish skill?

Run npx skillmds@latest add laurigates/bun-publish in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Bun Publish safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Bun Publish?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Bun Publish free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Bun Publish?

laurigates (@laurigates) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Bun Publish by laurigates — Agent Skill

Name: Bun Publish
Rating: 4.5 (4 reviews)
Author: laurigates

File contents

/bun:publish

Publish package to npm registry after building with Bun.

When to Use This Skill

Use this skill when...	Use bun-publishing instead when...
Executing a single `npm publish` action with the right flags	Looking up broader npm publishing workflow guidance and conventions
Previewing a publish with `--dry-run` before releasing	Configuring `publishConfig`, scoped-package access, or provenance setup
Releasing a scoped package with `--access public`	Use bun-build when you need to produce build artifacts before publishing
Enabling supply-chain `--provenance` signing on a release	Use bun-lockfile-update when bumping dependencies before a release

Parameters

--dry-run: Preview publish without executing
--access: Access level (public or restricted)
--provenance: Enable supply chain provenance signing

Context

Detect package configuration:

cat package.json | jq '{name, version, publishConfig, bin, files, scripts: {prepublishOnly: .scripts.prepublishOnly}}'

Execution

Pre-publish Validation

# Type check
bun run tsc --noEmit 2>&1 | head -20

# Build
bun run build

# Verify tarball contents
npm pack --dry-run

Publish

Dry run (default for first attempt):

npm publish --dry-run {{ "--access " + ACCESS if ACCESS }}

Actual publish:

# Standard package
npm publish {{ "--access " + ACCESS if ACCESS }} {{ "--provenance" if PROVENANCE }}

# Scoped package (auto-detect from name starting with @)
npm publish --access public {{ "--provenance" if PROVENANCE }}

Scoped Package Detection

If package.json name starts with @:

Automatically add --access public unless explicitly restricted
Warn if publishConfig.access is not set in package.json

Post-publish

Display published version: npm view <package> version
Show installation command: npm install <package>
Link to npm package page

Error Handling

402 Payment Required:

Scoped packages require --access public for public registry
Add publishConfig.access: "public" to package.json

Missing authentication:

Run npm login to authenticate
Or set NPM_TOKEN environment variable

---name: bun-publishdescription: Bun publish to npm. Use when the user wants to release to npm, preview with --dry-run, publish a scoped package with --access public, or enable --provenance signing.--- # /bun:publish Publish package to npm registry after building with Bun. ## When to Use This Skill | Use this skill when... | Use bun-publishing instead when... | |---|---| | Executing a single `npm publish` action with the right flags | Looking up broader npm publishing workflow guidance and conventions | | Previewing a publish with `--dry-run` before releasing | Configuring `publishConfig`, scoped-package access, or provenance setup | | Releasing a scoped package with `--access public` | Use bun-build when you need to produce build artifacts before publishing | | Enabling supply-chain `--provenance` signing on a release | Use bun-lockfile-update when bumping dependencies before a release | ## Parameters - `--dry-run`: Preview publish without executing - `--access`: Access level (`public` or `restricted`) - `--provenance`: Enable supply chain provenance signing ## Context Detect package configuration: ```bash cat package.json | jq '{name, version, publishConfig, bin, files, scripts: {prepublishOnly: .scripts.prepublishOnly}}' ``` ## Execution ### Pre-publish Validation ```bash # Type check bun run tsc --noEmit 2>&1 | head -20 # Build bun run build # Verify tarball contents npm pack --dry-run ``` ### Publish **Dry run (default for first attempt):** ```bash npm publish --dry-run {{ "--access " + ACCESS if ACCESS }} ``` **Actual publish:** ```bash # Standard package npm publish {{ "--access " + ACCESS if ACCESS }} {{ "--provenance" if PROVENANCE }} # Scoped package (auto-detect from name starting with @) npm publish --access public {{ "--provenance" if PROVENANCE }} ``` ## Scoped Package Detection If `package.json` name starts with `@`: - Automatically add `--access public` unless explicitly restricted - Warn if `publishConfig.access` is not set in package.json ## Post-publish 1. Display published version: `npm view <package> version` 2. Show installation command: `npm install <package>` 3. Link to npm package page ## Error Handling **402 Payment Required:** - Scoped packages require `--access public` for public registry - Add `publishConfig.access: "public"` to package.json **Missing authentication:** - Run `npm login` to authenticate - Or set `NPM_TOKEN` environment variable

Frequently asked questions

Bun Publish