$ loading_
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.
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
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.
Ask questions against an open investigation log — what witnesses said, where accounts conflict, what gaps exist, what the strongest evidence is on each issue. Use when the attorney needs to query the investigation record without re-reading every entry.
EU AI Act per-system inventory — track each AI system's role (provider, deployer, importer, distributor, authorized representative, product manufacturer) and risk tier (prohibited, high-risk, limited, minimal, GPAI, GPAI+systemic). Role and tier are assessed per system, not per company. Use when the user says "ai inventory", "add an ai system", "what systems do we have", "classify this ai system", "eu ai act register", or "ai system registry".
Draft a firm AI usage policy from published model policies, adapted to your practice profile — a research-and-synthesis tool whose output is a draft for attorney review and adoption, not a finished policy. Use when user says "draft an AI policy", "we need an AI policy", "build an AI usage policy", "our firm needs a GenAI policy", or similar requests to generate a first-cut internal AI policy.
Review vendor AI terms — agreement, addendum, or ToS AI provisions — against your governance positions; flag training-on-data, liability, model changes, and AI policy consistency. Use when user says "review this AI agreement", "check OpenAI terms", "what did we agree to with [vendor]", "vendor sent an AI addendum", "is this AI contract okay", or attaches vendor AI terms.
Route a contract issue to the right approver per the escalation matrix in `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`, and draft the ask. Use when the user says "who needs to approve this", "escalate this", "does this need GC sign-off", "route this for approval", or when another skill finds an issue that exceeds the reviewer's authority.
Freedom-to-operate triage — a structured first look at potentially blocking patents, not an FTO opinion. Use when a product, process, or feature is being evaluated for blocking patents, when asked whether anything stops a launch, or to build a claim-chart first pass against the most plausible patents before patent counsel review. This skill never concludes a product is clear to launch.