Currently, PicoClaw allows installing skills via install_skill, but there's no built-in way to remove or uninstall them. This makes it hard to clean up unused, broken, or deprecated skills — for example, gitlab-manager when Node.js is not available.
I propose adding a new command: uninstall_skill --slug [--force]
This would make it easier to keep the environment clean and avoid clutter from skills that don't work in the current setup. Right now, users have to manually rename or move files, which works but is not intuitive or safe.
Example usage:
uninstall_skill --slug gitlab-manager
As a safety feature, the command could optionally move the skill folder to a .backup/ directory instead of deleting it permanently, so users can restore it if needed.
This would bring PicoClaw closer to the behavior of standard package managers and improve the experience for users who iterate on their configurations.
Currently, PicoClaw allows installing skills via install_skill, but there's no built-in way to remove or uninstall them. This makes it hard to clean up unused, broken, or deprecated skills — for example, gitlab-manager when Node.js is not available.
I propose adding a new command: uninstall_skill --slug [--force]
This would make it easier to keep the environment clean and avoid clutter from skills that don't work in the current setup. Right now, users have to manually rename or move files, which works but is not intuitive or safe.
Example usage:
uninstall_skill --slug gitlab-manager
As a safety feature, the command could optionally move the skill folder to a .backup/ directory instead of deleting it permanently, so users can restore it if needed.
This would bring PicoClaw closer to the behavior of standard package managers and improve the experience for users who iterate on their configurations.