'"bunx"' is not recognized as an internal or external command on Windows when Bun is not installed; the extension now correctly falls back to npx as intendedbunx, it is only called optimally if npx is not foundDISABLE_TELEMETRY=1 to all Skills CLI invocations when the preference is enabled/opt/homebrew/opt/node@24/bin so the Skills CLI can find node when npx comes from Homebrew, while still preferring Node installs from version managers firstskills update <name> (requires skills CLI 1.5.0+), so a single outdated skill can be updated without touching the othersCommandStates components back into command filesuseSkillContent and expand skills-cli coverage around CLI error normalization and agent id mappingsearch and manage empty/error states with shared retry handling and clearer recovery copyREADME.md and add a manual smoke checklist in TESTING.mdvitest-based unit tests and an opt-in live API test for the skills extension?q=skill) that only returned skills with "skill" in the name, missing the majority of popular skillsfnm install locations, including ~/Library/Application Support/fnmfnm directory resolution preference order when resolving fnm paths.npx path preference for non-standard setupsnpx and Skills CLI failures, including a shortcut to open Extension Preferenceskills list --json for structured output instead of parsing ANSI textallowed-tools: Bash)