Advanced Installation
Use this guide when you need more control than the root README quickstart: non-interactive installs, specific agents, global vs project scope, updates, removals, or a manual fallback.
Requirements
- Node.js and npm available on your PATH. The examples use
npx, which ships with npm. - A current
skillsCLI — version 1.5.16 or newer. Running vianpx skills@latestalways uses the latest. Versions 1.5.15 and earlier do not create the Claude Code skills link, so installed skills won’t appear in Claude Code (Codex and other agents that read.agents/skills/directly are unaffected). - Access to
https://github.com/NVIDIA/skills. - An AI agent that supports Agent Skills, such as Claude Code, Codex, Cursor, OpenCode, Windsurf, Gemini CLI, or another compatible agent.
List Skills Before Installing
Use this when you want to inspect the catalog before selecting a skill.
Install One Skill
Use the skill name from the name: field in the skill’s SKILL.md. In this catalog, names usually match the leaf folder under skills/<product>/.
Install to a Specific Agent
You can pass --agent more than once:
Choose Project or Global Scope
Project installs are the default. They place links under the current project’s agent-specific skills directory so the skills travel with that project.
Global installs make the skill available across projects for the selected agent:
Non-Interactive Install
Use --yes when scripting setup or bootstrapping a development environment:
Update or Remove Installed Skills
Manual Fallback
Prefer npx skills add because it handles agent directories, global vs project scope, and updates. If you cannot use Node.js or npm, you can still copy a skill directory manually:
- Open the product folder under
skills/. - Copy the specific skill directory containing
SKILL.md. - Place it in your agent’s skills directory.
Common global locations are:
Manual installs do not participate in npx skills update, so use them only as a fallback.
Troubleshooting
Installed skills don’t appear in your agent
- Check your CLI version first. Run
npx skills --version. If it is older than 1.5.16, upgrade by installing vianpx skills@latest .... Versions 1.5.15 and earlier fail to link skills into Claude Code’s.claude/skills/directory, so the files install but the agent never sees them. - Reload skills in your session. In Claude Code, run
/reload-skills(or restart the session) so newly installed skills are picked up.
Verify your agent can see an installed skill
After installing <skill-name>, confirm it landed where your agent looks:
If .claude/skills/<skill-name> is missing or empty on Claude Code, it is almost always the stale-CLI issue above — upgrade to 1.5.16+ and re-run the install.