Skill Manager Plus

Problem

skill-manager addresses a concrete lifecycle issue: after an official SKILL package is downloaded from the Store and installed into a project, users may still need to add rules or correct entries without directly mutating the official content, and without losing personal customizations during updates.

How It Works

• Install and update: it downloads, unzips, and validates the package by checking for SKILL.md, extracts name and description, and uses the presence of _user/<skill>/ to decide between fresh install and update. Updates replace base/ while preserving extensions/, patches/, and registry.md under _user/<skill>/.
• Layered structure: base/ stores the official read-only content; extensions/ stores new user additions; patches/ stores targeted corrections to existing entries; the root SKILL.md is generated from a template and defines how final effective content is assembled.
• Customization and validation: user requests can be classified as append or patch, with entries written to the matching directory and registry. After updates, it checks whether patch targets and original text remain valid, and flags items that need review.

Boundaries

The skill manages SKILL lifecycle operations; it does not execute tasks by using an installed SKILL. skill-manager itself, each SKILL's root SKILL.md, and base/ are protected against direct modification. Uninstallation removes personal customizations as well, so it requires confirmation.