How do I install the Local Package skill?

Run npx skillmds@latest add tomevault-io/local-package 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 Local Package safe to use?

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

Which AI agents work with Local Package?

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 Local Package free to use?

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

Who published Local Package?

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

Local Package by tomevault-io — Agent Skill

Name: Local Package
Author: tomevault-io

Local Package

Use Clipboard's internal CLI to link and unlink @clipboard-health packages across repositories for local development. Use when testing local package changes, linking @clipboard-health packages between repos, or using the cbh CLI local-package command. Use when this capability is needed.

tomevault-io 5c5974b 2 files · 2.8 KB Updated Sep 17, 2026

File contents

Local Package Development

Use Clipboard's internal CLI (@clipboard-health/cli) to test package changes across repositories without publishing. The cbh local-package command wraps yalc to simplify linking packages between sibling repositories.

Prerequisites

See the CLI README for setup instructions.

Commands

Link packages

From the consuming repository, link packages from sibling repos:

cbh local-package link --packages <package-names...>

Example:

cbh local-package link --packages ui-theme ui-components

This will:

Find the package in sibling packages/* directories
Build the package with nx
Push the built package to yalc
Update your package.json to use the yalc version

Unlink packages

After testing, restore the published package versions:

cbh local-package unlink --packages <package-names...>

Example:

cbh local-package unlink --packages ui-theme ui-components

Workflow Example

To test changes to ui-theme in cbh-mobile-app:

Make changes to ui-theme in cbh-core

From cbh-mobile-app root, run:

cbh local-package link --packages ui-theme

Test your changes in cbh-mobile-app

When done, unlink:

cbh local-package unlink --packages ui-theme

Troubleshooting

Package not found: Ensure the package exists in a sibling repo's packages/ directory
Build fails: The package must have a valid nx build target
Changes not reflected: Run npm install after linking to pull in the yalc version

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: local-packagedescription: Use Clipboard's internal CLI to link and unlink @clipboard-health packages across repositories for local development. Use when testing local package changes, linking @clipboard-health packages between repos, or using the cbh CLI local-package command. Use when this capability is needed.---# Local Package DevelopmentUse Clipboard's internal CLI (`@clipboard-health/cli`) to test package changes across repositories without publishing. The `cbh local-package` command wraps [yalc](https://www.npmjs.com/package/yalc) to simplify linking packages between sibling repositories.## PrerequisitesSee the [CLI README](https://github.com/ClipboardHealth/cbh-core/tree/main/packages/cli#local-package) for setup instructions.## Commands### Link packagesFrom the consuming repository, link packages from sibling repos:```bashcbh local-package link --packages <package-names...>```Example:```bashcbh local-package link --packages ui-theme ui-components```This will:1. Find the package in sibling `packages/*` directories2. Build the package with nx3. Push the built package to yalc4. Update your `package.json` to use the yalc version### Unlink packagesAfter testing, restore the published package versions:```bashcbh local-package unlink --packages <package-names...>```Example:```bashcbh local-package unlink --packages ui-theme ui-components```## Workflow ExampleTo test changes to `ui-theme` in `cbh-mobile-app`:1. Make changes to `ui-theme` in `cbh-core`2. From `cbh-mobile-app` root, run: ```bash cbh local-package link --packages ui-theme ```3. Test your changes in `cbh-mobile-app`4. When done, unlink: ```bash cbh local-package unlink --packages ui-theme ```## Troubleshooting- **Package not found**: Ensure the package exists in a sibling repo's `packages/` directory- **Build fails**: The package must have a valid nx build target- **Changes not reflected**: Run `npm install` after linking to pull in the yalc version---> Converted and distributed by [TomeVault](https://tomevault.io/claim/clipboardhealth) — claim your Tome and manage your conversions.

Frequently asked questions