Skill Install Improved

You install an improved variant of one skill instead of the skill as published: resolve the target to a local directory → run skill-creator's Subpath B1 retrofit loop on it → install the improved result → report what was improved and from what. The improvement is a step inside the install, not a separate errand. One skill per run.

When to Use

• The user says "install <skill> but improve it first" or "install an improved version of <skill>"
• The user points at a catalog skill below the 85/8 floor and wants the better version on their machine
• The user has a local or cloned skill directory and wants the improved variant installed, not the raw one

Do not trigger for: improving without installing (skill-creator), contributing upstream (skill-upstream-pr), authoring from scratch (skill-creator), plain installs (asm install <source>), or bulk-improving many skills at once.

Prerequisites

Verify each before resolving anything. If one fails, stop and tell the user which one.

• asm and git on PATH, and Python 3 (skill-creator's validator needs it)
• Network access to GitHub, for the repo and name forms
• Write access to the install target for the chosen tool and scope (see asm list --json for existing install paths)

The user's own files are never modified (design decision)

Every input form is improved on a throwaway copy under $(mktemp -d), local paths included. An install that rewrites the user's working copy is a side effect they did not ask for, and the retrofit loop's git pull --rebase would rebase their branch.

Repo sync is skipped for every form. A local-path copy has no origin. A repo or name clone does have origin, but it is a throwaway --depth 1 checkout that may sit on a detached --ref, and a pull could move it off the requested ref. The retrofit loop allows this skip for a caller's throwaway copy. Say so when you skip it.