skills-update-check

To check for updates to globally-installed skills, initiate a deterministic update detection process at session start or on request. It identifies the package runner using lockfile priority and global binaries, then parses outputs to summarize available updates or up-to-date states.

The once-per-session guard works by searching conversation history for a completion marker and skipping the update check if it has already executed. This prevents redundant or missed update checks for globally-installed skills during a single session.

Yes, the skills update check works with diverse package runners. It detects the runner using lockfile priority, checking for bun, pnpm, yarn, and npm sequentially, then falls back to global binaries to run skills commands consistently across environments.

To update global skills without interrupting your workflow, the check runs in the background and interprets output states. Upon detecting available updates, it prompts you before performing global updates, ensuring a non-blocking update workflow.

Global skills update detection supports package runners determined by lockfile priority, specifically bun, pnpm, yarn, and npm. It uses this priority order and global binaries as fallbacks to run skills commands consistently across different lockfile environments.