uninstall

Uninstalling community skills safely requires verifying the install log, enumerating all targeted delete paths, and requiring explicit yes confirmation before removing files. This prevents accidental deletion and maintains configuration cleanup integrity.

No, the uninstall process refuses to remove first-party plugins that ship with Claude for Legal. This safeguard prevents accidental deletion of core skills and ensures only eligible community-installed plugins are targeted.

If the target skill is not recorded in the hub's install log or starter pack table, the uninstall process refuses to proceed. This ensures only verified community skills are removed and prevents unauthorized deletions.

Yes, uninstalling a skill appends a timestamped entry to install-log.yaml to maintain traceability. This audit logging records the removal action, ensuring compliance tracking and historical accountability for configuration cleanup.

Full uninstall deletes all associated file paths after explicit confirmation, whereas disabling retains files. Uninstall targets scenarios needing complete removal of outdated community automation rather than temporary deactivation, ensuring thorough configuration cleanup.

You should not use this tool to remove first-party skills, as the system refuses to uninstall them. It is also unsuitable if the target community skill is not recorded in the hub's install log, as verification will fail and block deletion.