cc-unlink

Unlink a local Claude Cabinet checkout and restore the published npm version.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/orenmagid/claude-cabinet --skill cc-unlink
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-unlink
Source: https://github.com/orenmagid/claude-cabinet/tree/main/templates/skills/cc-unlink
Command: npx skills add https://github.com/orenmagid/claude-cabinet --skill cc-unlink

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Remove local development linking for Claude Cabinet. Returns the project to using the published npm version.

Core Features & Use Cases

  • Disconnects from a local Claude Cabinet checkout to ensure consuming projects use the published npm package.
  • Provides guidance for typical scenarios when migrating from local development to published usage and handling potential breaking changes.

Quick Start

Run the cc-unlink command to revert to the published npm package.

Frequently Asked Questions about cc-unlink

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

FAQPage Schema
How do I unlink a local npm package and revert to the published version?

To unlink a local npm package and revert to the published version, run the cc-unlink command. This disconnects your local development checkout and restores the consuming project to using the standard published npm package.

What happens to consuming projects when I remove local development linking?

When you remove local development linking, npm unlink breaks the existing links for consuming projects. This process ensures those projects stop referencing your local checkout and switch back to the published npm package.

When do I need to switch from a local npm checkout to the published package?

You need to switch from a local npm checkout to the published package when preparing a release across projects or migrating from local development to standard published usage. This ensures all consuming projects use the official npm version.

Can I use the npm unlink command to prepare a Claude Cabinet release across multiple projects?

Yes, you can use the unlink command to prepare a Claude Cabinet release across multiple projects. It reverts all consuming projects from the local development checkout back to the published npm package.

Why does unlinking a local development checkout break links for consuming projects?

Unlinking a local development checkout breaks links for consuming projects because npm unlink removes the local file system references. This forces the projects to resolve dependencies from the published npm registry instead of the local directory.