What problem does it solve? Globally installed agent skills come from two different install chains — third-party GitHub repos tracked by a lock file, and local skills installed from a source repo — and each chain needs a different update path. Worse, the npx skills update command misreports every skill as outdated when the lock file uses an older hash scheme, making it impossible to know what actually changed. ## Core Features & Use Cases - Dual-chain update checking: Distinguishes third-party skills (symlinks tracked in ~/.agents/.skill-lock.json) from local source skills (real directories installed from ~/skills) and checks each with the right method. - Content-based diffing: Downloads upstream GitHub tarballs via the gh CLI and diffs file content against installed copies, reporting OK / OUTDATED / GONE / MISSING / ERROR per skill with file-level change summaries. - Guided update and cleanup: Prints the exact npx skills update / npx skills add / npx skills remove commands to apply updates, reinstall changed local skills, and clean lock residue, then verifies with a re-check. - Use Case: Run the checker after npx skills update -g claims everything is outdated — the tarball diff reveals which skills genuinely changed upstream so you only update those. ## Quick Start Ask the agent to check all globally installed skills for upstream updates and update the ones that actually changed.
