docs: add CLI-version requirement + install troubleshooting (VDR item 2)#356
Merged
Merged
Conversation
The VDR flagged that skills install but do not appear in Claude Code. Root cause was an upstream skills CLI bug (fixed in v1.5.16): CLIs <= 1.5.15 skip creating the .claude/skills link, so files land in .agents/skills but Claude Code never sees them. Codex reads .agents/skills directly and is unaffected. Adds a minimum-CLI-version note (>= 1.5.16), a /reload-skills tip, and a Troubleshooting section (check CLI version first; per-agent verify-access steps) to the README and advanced-install docs. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Moshe Abramovitch <moshea@nvidia.com>
jasonnvidia
reviewed
Jul 16, 2026
| The CLI runs through `npx` and prompts you to choose a skill and install destination. You do not need to clone this repo or copy skill folders by hand. | ||
|
|
||
| The skill is available the next time your agent loads skills and encounters a relevant task. For example, ask your agent to "solve a linear programming problem with cuOpt" and the skill guides it through the cuOpt Python API. | ||
| > **Requires a current `skills` CLI (v1.5.16 or newer).** Installing via `npx skills@latest add nvidia/skills` always uses the latest. On older CLIs (v1.5.15 and earlier), skills may install but not appear in Claude Code — see [Troubleshooting](docs/advanced-install.mdx#troubleshooting). |
Collaborator
There was a problem hiding this comment.
Maybe overkill to recommending to specify "@latest" here. Since we are using npx skills it will pickup the latest version when available (as long as skills isn't installed locally).
jasonnvidia
approved these changes
Jul 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
The Verified Skills VDR flagged that skills install but do not appear in Claude Code. Root cause was an upstream
skillsCLI bug, fixed in v1.5.16: CLIs ≤ 1.5.15 skip creating the.claude/skillslink, so files land in.agents/skills/but Claude Code never sees them. Codex reads.agents/skills/directly and was unaffected — which is why the VDR saw "works for Codex, not Claude Code."No code/repo change is needed (the fix is upstream); the gap is docs telling users to be on a current CLI.
Changes
README.mdskillsCLI ≥ 1.5.16 (usenpx skills@latest), with a pointer to Troubleshooting./reload-skillstip to load newly installed skills in-session.docs/advanced-install.mdxNotes
🤖 Generated with Claude Code