Update and remove Skills without losing your work

Know which copy you are maintaining

npx --yes https://howai.build/cli/howai-cli-0.1.5.tgz list --api https://howai.build --agent claude-code

The CLI lists HowAI-managed installations in that directory. A ZIP copied manually has no installation receipt and is not adopted automatically. Check personal and project directories if the agent appears to use a different copy.

Skill: project-update
Installed version: record the CLI result
Target: record the full directory
Local changes: keep a patch or separate copy
Regression task: brief.md and its expected outputs

Update one package

npx --yes https://howai.build/cli/howai-cli-0.1.5.tgz update cobalt-system-deck --api https://howai.build --agent claude-code

Before updating, review the current instructions and requirements. Afterward, run the same small test task and inspect the actual files. A new version number does not establish that the output still meets your project's needs.

Omitting the slug updates managed installations for the chosen origin and target. Start with one package when you have local customizations or a critical workflow.

Handle local edits deliberately

HowAI checks managed files and stops when changes would be replaced or removed. Save a copy or patch outside the installation directory, compare it with the new package, and decide what to reapply.

For a deliberate version choice, use install with --version only when that exact release is available and your account may access it. Preserve a known-good copy before changing a working environment.

Remove a managed installation

npx --yes https://howai.build/cli/howai-cli-0.1.5.tgz uninstall cobalt-system-deck --api https://howai.build --agent claude-code

Use the same target as installation. After removal, refresh your agent and check for another copy if the Skill still appears. For manually installed files, remove only the reviewed Skill folder yourself; avoid deleting the shared parent directory.

Keep team updates reviewable

• Record the package version and requirements.
• Review the diff before distributing a changed project copy.
• Do not commit service secrets with the package.
• Run a representative task after the update.
• Confirm that you have permission to redistribute a package to teammates.

FAQ