Feat/uninstall skills

[persano]

Summary

Adds two-way skill management to the autoskills CLI. The default picker now handles both install and uninstall in a single pass: installed skills are pre-checked, unchecking one marks it for removal, and a y/N confirmation runs before any destructive action. A new -r / --remove flag is also added for scripted removal and users who want a dedicated remove flow.

Removal is symmetrical with install: cleans up the canonical .agents/skills/<name> directory, every per-agent symlink/copy (.claude/skills/<name>, .cline/skills/<name>, etc.), the matching skills-lock.json entry, and prunes empty parent directories. When the last skill is removed, the autoskills section of CLAUDE.md is swept too.

Why

Today the only way to remove a skill is to manually delete its directory, each per-agent symlink, the skills-lock.json entry, and (if present) the CLAUDE.md section. Easy to miss something. Re-running the installer to "deselect" doesn't help either — pre-checked installed skills don't have any removal pathway.

How it works now

Default picker (npx autoskills):

• Installed skills are now pre-checked (previously pre-unchecked).
• Uncheck an installed skill to mark it for removal.
• Check a new skill to mark it for install.
• One [enter] confirms both. The bottom help line reads — install N, remove M when both apply, — remove M for pure-remove, and falls back to the existing (checked/total) counter when nothing will be removed.
• If any removals are queued, a pre-confirm prompt appears before any filesystem changes: About to install N and remove M skill(s). Continue? [y/N]. Default N. Anything other than y/Y aborts cleanly with no changes.
• Pure-install runs (no removals) skip the prompt — behavior unchanged for the common case.

-r / --remove flag:

• Lists every installed skill highlighted in red, all rows pre-unchecked.
• [space] to toggle, [enter] to remove.
• Useful for scripts (-r -y removes everything non-interactively) and when you want an explicit remove-only flow.

Behavior changes worth flagging for reviewers

• Installed skills are now pre-checked in the default picker. Previously they were pre-unchecked. This is required for symmetric semantics.
• Interactive mode skips re-downloading already-installed skills the user didn't touch. Previously npx autoskills would re-run the install for every checked row regardless of state; now untouched installed rows are no-ops. -y still installs everything detected (installs ∪ keeps), preserving today's -y behavior exactly.

Commits

1. feat(cli): add interactive --remove flag to uninstall skills — the -r flag, uninstaller.ts module, lockfile cleanup, parent-dir pruning, multiSelect confirmLabel option in ui.ts.
2. feat(cli): handle removals in the default install picker — the symmetric checkbox flow.

Kept as two commits for reviewability.

What's included

• New uninstaller.ts — listInstalledSkills, uninstallSkill, uninstallAll (mirrors installer.ts structure including TTY/verbose/simple render modes).
• New changes.ts — computeChanges (pure bucketing into installs / removes / keeps / skips) and confirmDestructive (y/N prompt with injectable input/output streams for testability). Lives in its own module because importing helpers from main.ts from a test triggers its top-level main() and aborts the test process — putting them in their own file is the cleaner fix.
• ui.ts — multiSelect gains optional confirmLabel (used by -r) and optional confirmHintFn (used by the default picker to render the — install N, remove M suffix). Existing callers are unaffected.
• main.ts — selectSkills returns the boolean state array; main() calls computeChanges and dispatches to installAll and/or uninstallAll; new printCombinedSummary for the mixed case. Help text updated.
• READMEs — both top-level and packages/autoskills/README.md document removal from the default picker and the -r flag.

Safety

• Skill names are validated against path separators and .. traversal before any filesystem operation.
• Pre-confirm prompt before any destructive action when removals are involved.
• Broken symlinks left over from prior failed installs are still cleaned up (uses lstatSync).
• -r mode pre-unchecks every row — destructive action stays opt-in.
• -y semantics are unchanged: still install-only, never removes anything. Use -r -y for unattended removal.

Tests

387/387 passing (369 existing + 18 new in tests/changes.test.ts covering install-only/remove-only/mixed flows, prompt y/N handling, stream injection, and regression cases for full-path skill identifiers and URL-style entries). Typecheck clean, oxfmt + oxlint clean.

Design notes

Three options were on the table for the default picker:

• Pure symmetric — uncheck = remove, no prompt. Rejected: one fat-fingered space + enter silently removes work.
• Modal [r] to toggle remove-mode — rejected: just duplicates -r with worse discoverability, and modal toggles in TUIs invite "which mode am I in" confusion.
• Symmetric with pre-confirm (this PR) — same mental model as the checkbox visually implies, with a cheap confirmation gate matching the pattern apt, brew, and npm all use.

-r was kept rather than deprecated because it's useful for scripts and for users who want a no-ambiguity remove flow without scanning a mixed list.