skill-manager

Disable or re-enable hub-installed community skills with install-log verification.

Updated May 15, 2026
One-click install
npx skills add https://github.com/az9713/claude-for-legal-tutorial --skill skill-manager-az9713
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-manager
Source: https://github.com/az9713/claude-for-legal-tutorial/tree/main/legal-builder-hub/skills/skill-manager
Command: npx skills add https://github.com/az9713/claude-for-legal-tutorial --skill skill-manager-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you remove or quiet an installed community skill without accidentally affecting first-party skills, while keeping an audit trail and requiring explicit confirmation before any file changes.

Core Features & Use Cases

  • Uninstall community skills with safeguards: Removes only skills that are recorded in the hub install log as the most recent install or enable, and refuses to touch first-party plugins.
  • Disable community skills by renaming key entry files: Renames SKILL.md (and related hooks and scheduled agent files when present) so the skill stops firing safely instead of deleting configuration by default.
  • Re-enable previously disabled skills: Reverses the disable renames and logs an enable action when the most recent logged action is disable.
  • Preserve configuration by default: Keeps user configuration under ~/.claude/plugins/config/claude-for-legal/ unless you explicitly choose to remove it.
  • Always logs actions: Appends uninstall, disable, or enable entries to install-log.yaml and updates the hub’s installed starter pack table.

Quick Start

Use the command "Disable the community skill named <skill-name> in the legal builder hub" and answer yes only when the skill lists the exact files it will rename.

Frequently Asked Questions about skill-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely uninstall community skills without affecting first-party plugins?

To safely uninstall community skills, verify the skill in the hub install log and execute the removal workflow outside built-in plugin directories. This preserves first-party plugin integrity while removing only community-added skills.

What happens to configuration files when I disable a community skill?

Disabling a community skill renames key entry files like SKILL.md and associated hooks, stopping it from firing. Your configuration under ~/.claude/plugins/config/ is preserved by default unless you explicitly choose to remove it.

Can I re-enable a previously disabled community skill?

Yes, you can re-enable a disabled community skill if the most recent logged action in install-log.yaml is disable. The workflow reverses the entry file renames and logs a new enable action.

How does the audit trail work for community skill lifecycle management?

The audit trail uses an append-only logging mechanism that records every uninstall, disable, and enable action to install-log.yaml. This ensures a complete historical record of all community skill modifications.

Why does disabling a skill rename SKILL.md instead of deleting files?

Renaming SKILL.md instead of deleting files provides safe deletion by preventing data loss while stopping the skill from firing. This approach preserves your configuration and allows straightforward re-enablement later.

Do I need to type yes explicitly to remove community skills?

Yes, destructive operations like uninstalling or disabling community skills require an explicit typed yes confirmation. This safeguard ensures you acknowledge the exact files that will be renamed or removed.