skill-manager

To safely uninstall community plugins, the skill-manager verifies hub install-log history, resolves installed paths, requires typed user confirmation, and appends an audit log entry to install-log.yaml. It refuses removal if the plugin is not found or was already uninstalled.

Yes, you can disable a community skill without deleting files. The disable workflow renames the skill's entry files and any installed agent or frontmatter files, preserving user configuration by default while quieting the skill's functionality.

Re-enabling a disabled community skill reverses the previous disable renames, restoring the entry files and functionality. This is only supported if the skill's most recent logged action was a disable, and the re-enable action is appended to the audit log.

Guardrails include typed user confirmation before deletions or renames, explicit refusal of first-party plugin paths, out-of-scope skill refusal, and file rename or delete safety checks to prevent accidental changes to unrelated files.

Yes, skill management maintains an append-only audit trail. Every uninstall, disable, and re-enable operation is logged by appending an entry to the install-log.yaml file, ensuring a verifiable history of community skill changes.

Typed confirmation is required to enforce file rename and delete safety. Before uninstalling or disabling a community skill, the user must review the exact files affected and explicitly type yes to prevent accidental modifications to installed paths.