NVIDIA Agent Skills (2026): Inside the Free 100+ Skill Catalog — Which Skill to Use for What

NVIDIA's free page ships verified, signed agent skills too. The map: what's in the catalog, which skill for which use case, and your first install.

---

Last week I showed you NVIDIA's free model catalog 100+ frontier models, $0, one API key. Turns out that page has a second act most people scroll straight past: a full skills catalog free, NVIDIA-verified instruction packs your agents can install.

Here's why that matters. An agent skill is a folder of instructions that teaches an AI to do a task correctly. Anyone can write one. What NVIDIA did differently — and it's a first from a company this size — is ship a governed catalog: every skill is security-scanned, carries a verifiable NVIDIA signature, and comes with a machine-readable "skill card" describing exactly what it does and where its boundaries are (per NVIDIA's announcement).

The catalog spans more than a hundred skills — route optimization, GPU data-crunching, video pipelines, RAG systems, medical imaging, even quantum computing all mirrored in the open at github.com/NVIDIA/skills.

The thesis of this guide: these skills turn your agent from "can write code about X" into "operates X correctly" and since they're free, the only question is which ones map to your work. That's the map below.

---

---

What Exactly Are NVIDIA Agent Skills? (60 Seconds)

Quick grounding, because two ideas meet here:

Agent skills (the format) — an open standard, originally from Anthropic, now hosted at agentskills.io: a skill is a folder with a SKILL.md file of instructions that compatible agents (Claude Code, Codex, and a growing list) auto-load when a task matches.

NVIDIA's catalog (the library) — NVIDIA publishing its own skills, one per hard capability, so agents use NVIDIA's libraries and platforms the right way. Per their engineering blog, the catalog adds what the wild-west skill ecosystem lacks:

• Verified + signed — every published skill carries an NVIDIA signature you can check

• Security scanned — instruction safety and supply-chain checks before publication

• Skill cards — machine-readable metadata: identity, provenance, quality, behavioral boundaries

• Synced daily — skills mirror from the actual product repos, so instructions track the current library versions

Why this matters practically: the #1 failure mode of agents on specialist work is confidently wrong usage — deprecated APIs, wrong parameters, plausible-looking code that professionals would wince at. For example, ask a bare agent to "use cuOpt for these routes" and you'll often get code written against an API version that no longer exists — confident, clean, wrong. A vendor-written skill is the vendor telling your agent, in the agent's own format, exactly how the tool is meant to be used, synced against the current version.

---

Install: Your First NVIDIA Skill in 5 Minutes