external-skill-libraries

Run the library's own installer through the mise tasks: libraries:list to see options, then libraries:install -- <name> for a dry run and --yes to execute. The tool runs a name-collision precheck first and refuses rather than silently overwriting existing skills.

Skill names are one flat namespace per home, so the first writer holds the name and the second library's entry silently never loads. The precheck detects occupied names, including symlinks, and refuses the colliding library before its installer runs.

Use libraries:migrate -- <library>, which reads the other channel's lock file to prove the occupied names come from the same upstream, removes them through that channel's own remove verb, re-runs the precheck, then installs. Unproven names are left untouched.

No. The tool only invokes each library's own installer, which writes into the operator's home directory, so no upstream bytes enter the repository and no NOTICE attribution obligation attaches. Vendoring foreign content remains prohibited.

A dry run's job is to describe what would happen, and reporting a refusal is a correct description, so it exits 0. Only a real --yes operation that fails exits 1, and an unusable invocation exits 2.

ECC's surface cannot be enumerated offline, so without --names-from the precheck is reported as SKIPPED, not passed, and the install is gated behind --acknowledge-ecc-surface. Its README-documented setup command does not exist in the published npm artifact; the real front door is ecc install --target claude --profile <name>.