skills-manager

Audit Claude Code skills by analyzing project state, skill metadata, usage data, and change history to propose merges, archives, or rollbacks. The process enforces safe consolidation by verifying actual code usage and generating backups before any modifications.

Yes, you can roll back skill consolidation or archives. The management process backs up the current skill state before destructive actions and maintains rollback options, requiring explicit user confirmation before applying any irreversible changes.

The best way to back up Claude Code skills is using an automated audit process that captures the current skill state prior to merging or archiving. This ensures a verifiable recovery point exists before any consolidation changes are applied.

Yes, the skill consolidation process requires explicit user confirmation for all destructive actions. It uses a verification-first approach to check actual code usage and safeguards integrity before archiving, merging, or rolling back skills.

You should consolidate Claude Code skills when a comprehensive audit identifies redundancies and overlapping effectiveness across your project state. Consolidation is appropriate when actual code usage verification confirms the skills can be safely merged or archived.

Yes, you need the yaml dependency to run skill audits and management tasks. The audit scripts and references use yaml to parse skill metadata, project state, and configuration files required for the consolidation analysis.