uninstall Skill
Uninstall a community skill that was installed via the hub. Confirms before deleting files, refuses to touch first-party plugin skills, and logs every action. Use when the user wants to fully remove a community skill ("uninstall [skill]", "remove this skill") rather than just disable it. Published by anthropics in claude-for-legal.
Decision snapshot
Is this a fit?
Security review, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
25 days ago · Apache-2.0 license
No specific cautions were detected. Review the source and requested permissions before installing.
What is uninstall Skill?
Uninstall a community skill that was installed via the hub. Confirms before deleting files, refuses to touch first-party plugin skills, and logs every action. Use when the user wants to fully remove a community skill ("uninstall [skill]", "remove this skill") rather than just disable it. Published by anthropics in claude-for-legal. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Security review
- Security review use cases
Declared skill metadata
- Source file: legal-builder-hub/skills/uninstall/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use uninstall Skill
- Use it for security review.
Built with
Editorial notes
Source
- Creator: anthropics
- Repository: anthropics/claude-for-legal
- Skill file: legal-builder-hub/skills/uninstall/SKILL.md
What it does
Uninstall a community skill that was installed via the hub. Confirms before deleting files, refuses to touch first-party plugin skills, and logs every action. Use when the user wants to fully remove a community skill ("uninstall [skill]", "remove this skill") rather than just disable it.
Skill instructions
/uninstall Run the uninstall workflow from the skill-manager reference skill against the named skill. Safety rules: 1. Only uninstall community skills installed through this hub. Check ~/.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. 2. Never uninstall a first-party plugin's skill. The 12 core plugins that ship with claude-for-legal are off-limits from this command. If the named skill resolves to a path inside one of those plugins, refuse. 3. Confirm before removing files. Show the user every path that will be deleted. Proceed only on explicit yes. 4. Log the uninstall. Append to 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, dis
Verified compatibility and discovery
Frequently asked questions
What is uninstall?
uninstall is a open-source AI agent skill with Copy skill directory. Uninstall a community skill that was installed via the hub. Confirms before deleting files, refuses to touch first-party plugin skills, and logs every action.
Who is uninstall best for?
uninstall is best for reusing agent instructions, scripts, and references, security review workflows.
How do I install uninstall?
Install or run uninstall using Copy skill directory. Check uninstall for the latest setup command.
Is uninstall actively maintained?
uninstall may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
