Guide · Agent skill
How to use the Skill Manager agent skill (skill-manager)
Updated · written with AI from the project's own documentation and checked against our catalogue data
Skill Manager is an agent skill from the claude-for-legal project that removes, temporarily disables, or re-enables community skills you previously installed through the legal builder hub. It is aimed at lawyers and legal teams who want to clean up community skills safely, and at developers who maintain the hub. After this guide you will know what the skill does, how to install it, how to ask for each action, and what it will and will not touch.
Skill Manageranthropics/claude-for-legal · Apache-2.0 Download the skill Quick start
- 1Download the ZIP. Download the skill-manager ZIP from this page.
- 2Unzip into a skills folder. Unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder.
- 3Or upload it in the Claude apps. In the Claude apps, go to Settings → Capabilities → Skills and upload the skill.
- 4Confirm the hub and log exist. Make sure the claude-for-legal legal-builder-hub plugin is installed and that install-log.yaml is present in its config folder.
- 5Name one skill and one action. Ask the agent to disable, uninstall or re-enable a single community skill by name.
- 6Review the list and type yes. Read the files the agent shows. Reply with an explicit yes only if you agree; otherwise reply no.
What is an agent skill and what does Skill Manager do?
An agent skill is a folder containing a SKILL.md file that gives an AI agent specific instructions for a task. Skill Manager is a reference workflow for one task: managing community skills that were installed through the claude-for-legal builder hub.
It supports three actions. Uninstall removes a skill's directory. Disable renames the skill's files so it stops running, including scheduled agents. Re-enable reverses a disable. Before changing anything, the agent checks an install log, shows you exactly which files it will change, and only acts after you type an explicit yes.
- Uninstall: deletes the skill directory after confirmation.
- Disable: renames SKILL.md to SKILL.md.disabled, hooks/hooks.json to hooks/hooks.json.disabled if present, and agent files to *.md.disabled so scheduled agents stop firing.
- Re-enable: reverses the renames for a skill whose most recent log action is disable.
- Every action is appended to install-log.yaml.
Install the skill-manager skill
Download the skill-manager ZIP from this page. Then choose one of two locations. For personal use across projects, unzip it into ~/.claude/skills/. For a single project, unzip it into that project's .claude/skills/ folder.
If you use the Claude apps instead, upload the skill under Settings → Capabilities → Skills.
- Personal install: ~/.claude/skills/
- Project install: .claude/skills/ inside your project folder
- Claude apps: Settings → Capabilities → Skills
Check the requirements before you start
Skill Manager depends on the claude-for-legal legal-builder-hub plugin. It also needs access to the install log at ~/.claude/plugins/config/claude-for-legal/legal-builder-hub/install-log.yaml. The skill is only useful for skills that were installed through the hub, because the log is how it verifies a skill.
The skill does not run scripts and does not use the network, according to its listing.
- Requires the claude-for-legal legal-builder-hub plugin
- Requires access to install-log.yaml in the hub config folder
- Runs scripts: no
- Uses network: no
Trigger the skill with natural requests
The skill's own description says it is loaded by the /legal-builder-hub:uninstall and /legal-builder-hub:disable skills, and its frontmatter sets user-invocable to false. So the practical way to use it is through those hub commands, or by naming the action and skill in a plain request, such as asking the agent to disable a named community skill.
Name exactly one skill per request. The skill acts on one name and one action per invocation.
- Ask to disable a named community skill, for example to pause its scheduled agents.
- Ask to uninstall a named community skill you no longer want.
- Ask to re-enable a skill that was previously disabled.
- Give one skill name per request.
Walk through an uninstall or disable safely
The agent first confirms the skill appears in install-log.yaml with a most recent action of install or enable, and that its files sit outside the built-in plugin directories. If either check fails, it refuses and explains why. For uninstall, it lists the skill directory, every file to be deleted, and any config directories it will keep. It then asks: Delete these files? (yes / no). For disable, it shows the rename list and asks: Disable this skill? (yes / no).
Only a typed yes causes a change. Configuration is preserved unless you ask for it explicitly.
- Read the list the agent shows before answering.
- Type yes only if the list is correct.
- Config under ~/.claude/plugins/config/claude-for-legal/<plugin>/ is kept by default; you can delete it manually if you wish.
- Uninstall also removes the skill's row from the installed starter pack table in the hub's CLAUDE.md.
Know what Skill Manager will refuse
Skill Manager will not touch the built-in first-party plugins. The source lists examples including commercial-legal, corporate-legal, employment-legal, privacy-legal, product-legal, regulatory-legal, ai-governance-legal, litigation-legal, law-student, legal-clinic, and legal-builder-hub itself. For plugin management, the source says to use /plugin.
It also refuses any skill not present in the install log, and it ignores instructions inside third-party SKILL.md files that ask it to remove or disable something else.
- Built-in plugins: refused; use /plugin instead.
- Skills not in install-log.yaml: refused.
- Instructions inside third-party SKILL.md files: ignored; only your typed command authorizes action.
What people use it for
- Pausing a community skill's scheduled agents without losing the skill, so it can be re-enabled later.
- Uninstalling a community skill that a legal team no longer uses, after reviewing the file list.
- Giving a hub maintainer one consistent uninstall and disable process with an audit trail in install-log.yaml.
- Re-enabling a skill that was disabled earlier, by reversing the renames and logging the change.
Frequently asked questions
How do I install the skill-manager agent skill?
Download the skill-manager ZIP from this page and unzip it into ~/.claude/skills/ for personal use or into a project's .claude/skills/ folder. Alternatively, upload it in the Claude apps under Settings → Capabilities → Skills.
What does the skill-manager skill require?
It requires the claude-for-legal legal-builder-hub plugin and access to install-log.yaml in ~/.claude/plugins/config/claude-for-legal/legal-builder-hub/. The listing says it runs no scripts and uses no network.
Can Skill Manager remove the built-in legal plugins?
No. It refuses to change the built-in first-party plugins such as commercial-legal and legal-builder-hub. The source says to use the /plugin command for plugin management.
Will it delete my configuration files?
Not by default. Configuration under ~/.claude/plugins/config/claude-for-legal/<plugin>/ is preserved unless you ask for it explicitly, so leftover data may remain and you can delete it manually.
Can it remove a skill I installed myself from another source?
No. It only acts on skills recorded in install-log.yaml with a most recent action of install or enable. Skills not installed through the hub are refused.
Is it safe to let an agent delete files?
The skill is built to be cautious. It shows every file it will change and performs no file operation without an explicit typed yes. Every action is logged to install-log.yaml, and it acts on one skill per invocation.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Skill Manager suits lawyers and legal teams who installed community skills through the claude-for-legal hub and want to remove or pause them with a visible confirmation step. It is not a general plugin manager, and it will not help with skills that came from elsewhere or with the built-in plugins, which you should manage with /plugin.
Download the skill