Local Skill Installer

When to Use

Use when the user asks to validate, install, package, remove or restore a specific local skill in a workspace. Merely creating a skill does not authorize installation, overwriting another skill, installing every discovered candidate or changing global agent configuration.

Scope and setup

Run from the workspace whose installations you intend to manage. Paths supplied to the installer, validator and packager must resolve inside that current workspace; symlink paths and skill-tree links/special files are rejected. The scripts use ./skills, ./.claude/skills, ./.skill-installer/data (backups/staging/log) and ./dist (ZIPs). They do not target a particular user's Windows directory or install globally.

Install scripts/requirements.txt into a suitable isolated Python environment before using the helpers. PyYAML is required; malformed, duplicate-key or non-mapping frontmatter is rejected rather than heuristically recovered. Treat discovered skills and their bundled programs as untrusted until reviewed. Validation checks structure and selected secret filenames; it does not prove a skill safe or detect every credential.

Workflow

Resolve these bundled script paths relative to this skill, while keeping the working directory set to the target workspace:

# Read-only structural check of an explicitly selected local directory.
python /path/to/skill-installer/scripts/validate_skill.py ./incoming/my-skill