What problem does it solve?
CLI tools installed inside a sandboxed environment disappear when the sandbox is destroyed, forcing users to reinstall and reconfigure them every session. This Skill orchestrates installing, persisting, restoring, inspecting, and removing user-managed CLI tools so they survive across sandbox sessions.
Core Features & Use Cases
- Persistent CLI Installation: Installs third-party CLIs (via npm, pipx, uv, go, cargo, brew, or script installers) and persists them so they remain available in future sandbox sessions.
- Adopt, Inspect, and Remove: Adopts already-installed CLIs into persistence records, lists and validates persisted CLIs, and removes persistence records or saved state after user confirmation.
- Runtime CLI Protection: Distinguishes runtime-provided CLIs (lark-cli, dws, teamshare-cli) from user-managed ones and prevents accidental persistence or modification of runtime tools.
- Use Case: A user wants to install a code-generation CLI with
npm install -g and keep it available next week. The Skill reviews the installer, asks for confirmation, persists the CLI with its config directories and environment variable names, and restores it automatically in later sessions.
Quick Start
Install the example-cli tool with npm and persist it so it stays available in all my future sandbox sessions.