Safely uninstall hub-installed community skills with confirmation and audit logging.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "uninstall" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/claude-for-legal/main/legal-builder-hub/skills/uninstall/SKILL.md 2. Save it as ~/.claude/skills/uninstall/SKILL.md 3. Reload skills and tell me it's ready
Please uninstall the community skill named community-reporter, and list the file paths to be removed before deletion.
It verifies that the skill is a hub-installed community skill, shows the paths to be deleted, and only uninstalls and logs the action after explicit confirmation.
I don't want this skill to run anymore, but I want to keep its files and configuration. What should I do?
It advises against uninstalling and suggests using the disable workflow to stop the skill while keeping files intact.
Please uninstall a skill that comes with a first-party plugin.
It refuses clearly and explains that first-party plugin skills are outside the allowed uninstall scope.
Developers or DevOps users can use it to fully remove community skills they no longer need after testing several options. This helps reduce clutter in the local environment while preserving an audit trail.
In environments that require change tracking, users can review the paths to be deleted before confirming removal. The tool records the uninstall action and timestamp for traceability.
When a user mistakes a first-party plugin skill for a community skill, this skill refuses the operation. That prevents accidental removal of protected built-in capabilities.
The documentation explains how /uninstall works and focuses on safety constraints. It runs the uninstall workflow from the skill-manager reference skill and only allows removal of community skills installed through the hub and recorded in the install logs. It must refuse first-party plugin skills, show every path to be deleted, proceed only after an explicit yes, and append an uninstall entry with a timestamp to install-log.yaml. If the user only wants to stop usage, disable is recommended instead.
Run the uninstall workflow from the skill-manager reference skill against
the named skill.
Safety rules:
~/.claude/plugins/config/claude-for-legal/legal-builder-hub/install-log.yaml
and the CLAUDE.md installed starter pack table. If the skill is not recorded
there, refuse and tell the user.yes.install-log.yaml with action uninstall
and timestamp so the audit trail is intact.If the user wants to stop a skill from running but keep the files (e.g., for
later re-enable, or to preserve configuration), suggest /legal-builder-hub:disable
instead.
Detailed uninstall, disable, and re-enable workflows live in the
skill-managerreference skill — load it before doing substantive work.
It uninstalls community skills that were installed through the hub, rather than simply disabling them. Before removal, it confirms the file paths to delete and logs the uninstall action.
No. It only handles community skills installed through the hub and recorded in the install log; it refuses to remove skills that belong to first-party plugins.
If you want to keep the files for later re-enabling or to preserve configuration, you should use the disable workflow instead of uninstalling. The docs suggest /legal-builder-hub:disable.
Safely review and install community skills with explicit user approval.
Search watched skill registries, preview matches, and inspect SKILL.md before installing.
Temporarily disable or re-enable an installed community skill without deleting files.
Get a concise briefing on one legal matter's status, changes, deadlines, and risks.
Manage matter workspaces to separate, switch, and archive client contexts.
Draft DMCA notices, triage incoming claims, and prepare counter-notice drafts.
Safely uninstall, disable, and re-enable community skills with audit logging.
Check installed community skills for updates with diffs and explicit approval.
Install Codex skills from curated lists or GitHub repositories into your local environment.
Suggests relevant community skills based on your task and recent plugin activity.
Perform ClawHub moderation actions like bans, role changes, and status checks.
Assess a skill’s trustworthiness, risks, and design quality before installation.