publish-placeholder-package

Name: publish-placeholder-package
Availability: InStock
Author: Remix

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

33.3k|2.8k|Updated Oct 26, 2020

Search Tags:#npm #verification #trust #oidc #package-management #placeholder #ci-publishing

Ready to run

npx skills add https://github.com/remix-run/remix --skill publish-placeholder-package

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: publish-placeholder-package
Source: https://github.com/remix-run/remix/tree/main/.agents/skills/publish-placeholder-package
Command: npx skills add https://github.com/remix-run/remix --skill publish-placeholder-package

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you reserve an npm package name by publishing a minimal placeholder package at version 0.0.0, enabling CI/OIDC configuration before a full release.

Core Features & Use Cases

Reserve an npm package name by publishing a minimal placeholder at 0.0.0 to unblock CI publishing.
Prepare repository configuration and metadata (repository URL and publish settings) for future releases.
Use case: when creating a brand-new package that cannot yet be released, you can bootstrap the workflow and trust process.

Quick Start

Create a temporary directory, publish a minimal package.json with version 0.0.0 for the target package, and verify it appears on npm before configuring trusted publishing.

Frequently Asked Questions about publish-placeholder-package

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

FAQPage Schema

How do I reserve an npm package name before setting up CI publishing?▼

Reserve an npm package name by publishing a minimal placeholder package at version 0.0.0. This secures the name and allows you to configure OIDC trusted publishing permissions before your full release.

What is a 0.0.0 placeholder package used for in npm package management?▼

A 0.0.0 placeholder package is used to claim a namespace on npm. It enables teams to prepare repository metadata and establish trusted publishing workflows before the actual package code is ready for a full release.

Can I configure OIDC trusted publishing for a brand-new npm package?▼

Yes, you can configure OIDC trusted publishing for a brand-new npm package by first reserving the name with a placeholder. This verifies the package exists on npm before you enable trusted publishing for CI workflows.

What's the best way to bootstrap an npm release workflow when the package is not ready?▼

The best way is to create a temporary workspace and publish a minimal package.json with repository metadata at version 0.0.0. This bootstraps the release workflow and trust process without requiring full package contents.

Do I need a temporary workspace to publish a placeholder npm package?▼

Yes, you need a temporary workspace to write a minimal package.json containing repository metadata. This isolated environment allows you to publish the 0.0.0 placeholder to npm safely before enabling CI publishing.