skills.rest
nvie
nvieCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

liveblocks-new-npm-package

Creates a minimal placeholder package and publishes it to NPM under the @liveblocks org.

3|Updated Apr 14, 2026
Search Tags:#npm#publish#registry#package#placeholder#liveblocks#scoped package
One-click install
npx skills add https://github.com/nvie/skills --skill liveblocks-new-npm-package-nvie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: liveblocks-new-npm-package
Source: https://github.com/nvie/skills/tree/main/skills/liveblocks-new-npm-package
Command: npx skills add https://github.com/nvie/skills --skill liveblocks-new-npm-package-nvie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Claiming a new package name on NPM requires publishing an initial version, but setting up even a minimal package by hand is repetitive and error-prone. This Skill scaffolds the exact minimal placeholder package and hands you the single publish command. ## Core Features & Use Cases - Minimal Placeholder Generation: Creates a temp directory containing only a package.json (name, version 0.0.0, Apache-2.0 license, main entry) and an index.js placeholder file. - Guided Publish Command: Outputs the exact npm publish --access public command with the real temp path substituted, so scoped packages publish correctly on the free tier. - Use Case: You want to reserve the name @liveblocks/foobar before starting real development. The Skill creates the placeholder files and gives you the command to claim the name immediately. ## Quick Start Ask the assistant to publish a new @liveblocks placeholder package named foobar to NPM.

Frequently Asked Questions about liveblocks-new-npm-package

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

FAQPage Schema
How do I publish a new scoped package to NPM for the first time?▼

Create a minimal package.json with the scoped name and version 0.0.0 plus a placeholder index.js, then run npm publish --access public from that directory. The --access public flag is required for scoped packages on the free tier.

How to claim an NPM package name with a placeholder?▼

Publish a minimal 0.0.0 version containing only package.json and an index.js placeholder file. This reserves the name on the registry, and you fill in the real implementation later.

Why does npm publish fail for scoped packages?▼

Scoped packages default to private access, which requires a paid NPM plan. Add the --access public flag to publish scoped packages publicly on the free tier, and verify you are logged in with publish rights to the org.

Does the skill run npm publish automatically?▼

No, the skill only creates the placeholder files in a temp directory and prints the exact publish command. The user runs npm publish themselves after confirming they are logged in with an account that has publish rights to the @liveblocks org.

What files does a minimal NPM placeholder package need?▼

Exactly two files: a package.json with name, version 0.0.0, license, and main fields, plus an index.js containing a placeholder comment. No README, description, or extra fields are included.

Related Skills

Explore More Software Engineering Skills→
remix-runremix-run
33.3k

publish-placeholder-package

Publish a minimal placeholder npm package at version 0.0.0 to reserve the package name.

Official
Intermediate
Thank-you-LinusThank-you-Linus
206

release-beta

Automate beta prerelease creation with AI-assisted version detection and release-note generation.

Official
Advanced
MearmanMearman
3

npm-exists

Check whether an npm package name exists in the registry.

Community
Intermediate
LuminaVaultLuminaVault

architecture-diagram

Generate HTML-based architecture diagrams from system component descriptions.

Official
Intermediate