Add nvidia-skill-finder as catalog-only router skill

benchmarks.json

@@ -1,7 +1,7 @@
 {
   "schema_version": 2,
   "source": "skills/*/BENCHMARK.md",
-  "skill_count": 229,
+  "skill_count": 230,
   "result_row_count": 2070,
   "skills_without_results": [
     "deepstream-generate-pipeline",
@@ -18,6 +18,7 @@
     "mcore-run-on-slurm",
     "mcore-split-pr",
     "mcore-testing",
+    "nvidia-skill-finder",
     "omniverse-cad-to-simready",
     "omniverse-realtime-viewer",
     "omniverse-usd-performance-tuning",
@@ -2470,6 +2471,21 @@
       "has_results": true,
       "average_uplift_pct": 29.5
     },
+    {
+      "skill": "skill",
+      "evaluation_date": "2026-06-25",
+      "profile": "external",
+      "environment": null,
+      "tasks": null,
+      "attempts_per_task": null,
+      "pass_threshold_pct": null,
+      "verdict": "PASS",
+      "agents": [],
+      "catalog_dir": "nvidia-skill-finder",
+      "component": "NVIDIA Skills",
+      "has_results": false,
+      "average_uplift_pct": null
+    },
     {
       "skill": "omniverse-cad-to-simready",
       "evaluation_date": "2026-05-28",

catalog-exceptions.yml

@@ -11,3 +11,7 @@ exceptions:
     reason: Contributor-facing skill, intentionally uncataloged (per cuOpt team, 2026-06-01)
     owner: rgsl888prabhu
     component: cuOpt
+  - dir: nvidia-skill-finder
+    reason: Catalog infrastructure router skill; maintained via direct PR (no components.d upstream)
+    owner: jdudash
+    component: NVIDIA Skills

skills/nvidia-skill-finder/BENCHMARK.md

@@ -0,0 +1,58 @@
+# Evaluation Report
+
+Evaluation of the `skill` skill before publication through NVSkills-Eval.
+
+This benchmark summarizes 3-Tier Evaluation from NVSkills-Eval results for the skill. The goal is to document whether the skill is safe, discoverable, effective, and useful for agents before it is published for broader workflow use.
+
+## Evaluation Summary
+
+- Skill: `skill`
+- Evaluation date: 2026-06-25
+- NVSkills-Eval profile: `external`
+- Overall verdict: PASS
+- Tier 3 live agent evaluation: not available in this report
+
+## Agents Used
+
+- Tier 3 agent details were not available in this report.
+
+## Metrics Used
+
+Reported benchmark dimensions:
+
+- Security: checks whether skill-assisted execution avoids unsafe behavior such as secret leakage, destructive commands, or unauthorized access.
+- Correctness: checks whether the agent follows the expected workflow and produces the correct final output.
+- Discoverability: checks whether the agent loads the skill when relevant and avoids using it when irrelevant.
+- Effectiveness: checks whether the agent performs measurably better with the skill than without it.
+- Efficiency: checks whether the agent uses fewer tokens and avoids redundant work.
+
+Underlying evaluation signals used in this run:
+
+- No Tier 3 evaluation signal details were available in this report.
+
+## Test Tasks
+
+Tier 3 evaluation task details were not available in this report.
+
+## Results
+
+Tier 3 dimension rollup was not available in this report.
+
+## Tier 1: Static Validation Summary
+
+Tier 1 validation passed with observations. NVSkills-Eval ran 9 checks and found 4 total findings.
+
+Top findings:
+
+- LOW QUALITY/quality_discoverability: Description very long (718 chars, recommend 50-150) (`[nvidia-skill-finder] skills/nvidia-skill-finder/SKILL.md`)
+- LOW QUALITY/quality_reliability: No prerequisites/requirements documented (`[nvidia-skill-finder] skills/nvidia-skill-finder/SKILL.md`)
+- LOW QUALITY/quality_reliability: No limitations documented (`[nvidia-skill-finder] skills/nvidia-skill-finder/SKILL.md`)
+- LOW QUALITY/quality_reliability: No troubleshooting section documented (`[nvidia-skill-finder] skills/nvidia-skill-finder/SKILL.md`)
+
+## Tier 2: Deduplication Summary
+
+This tier was not run or did not produce findings in this report.
+
+## Publication Recommendation
+
+The skill is suitable to proceed toward NVSkills-Eval publication based on this benchmark. Skill owners should keep this file with the skill and refresh it when the evaluation dataset, skill behavior, or target agents materially change.

skills/nvidia-skill-finder/SKILL.md

@@ -0,0 +1,162 @@
+---
+name: nvidia-skill-finder
+description: >-
+  Use for NVIDIA-related requests where an NVIDIA skill might help, even if the user did not ask for a skill. Trigger on NVIDIA products, hardware, software, SDKs, GPUs, Jetson/JetPack/L4T/BSP/SDK Manager/driver/flashing/setup, CUDA, NIM, NeMo, Omniverse/OpenUSD/SimReady, RAPIDS/cuDF, cuPyNumeric, cuOpt, Dynamo, Holoscan, TensorRT, DeepStream, VSS, TAO, NGC/NVCF. Do not use for generic non-NVIDIA route, optimize, deploy, AI, video, data, or infrastructure tasks.
+license: CC-BY-4.0 AND Apache-2.0
+metadata:
+  author: NVIDIA
+  tags:
+    - nvidia
+    - skills
+    - discovery
+    - catalog
+    - router
+  domain: agent-skills
+---
+
+# NVIDIA Skill Finder
+
+## Purpose
+
+Help users discover, install, and start using NVIDIA skills that may not be
+installed yet. Treat this skill as a stable NVIDIA capability detector and
+catalog router, not as a mirror of every external skill's trigger text.
+
+Use the live catalog as the source of truth for specific skill names,
+descriptions, and availability. Keep only stable taxonomy guidance here.
+
+## When to Use this Skill 
+Use this skill to find the best NVIDIA skill for a product, task, or workflow.
+The user does not need to explicitly ask for a skill. If the request is about
+NVIDIA hardware, software, SDKs, drivers, setup, troubleshooting, or an
+NVIDIA-adjacent workflow, check whether the live catalog has a skill that could
+help before proceeding too far with general guidance.
+
+Typical triggers:
+
+- Asks "how do I do X" where X might be a common task that an NVIDIA skill can help with.
+- Says "find a skill for X" or "is there a skill for X".
+- Expresses interest in extending agent capabilities in NVIDIA domains.
+- Mentions they need help with a specific NVIDIA catalog domain covered below.
+- Asks about installing, configuring, troubleshooting, or using an NVIDIA
+  product, device, SDK, or service.
+
+Continue with this skill only when the request is plausibly related to an NVIDIA product area or taxonomy category.
+
+Strong signals:
+
+- The user mentions NVIDIA, CUDA, GPU acceleration, NIM, NeMo, Omniverse, OpenUSD,
+  SimReady, cuOpt, RAPIDS/cuDF, cuPyNumeric, Dynamo, Holoscan, TensorRT, VSS,
+  DeepStream, Jetson, JetPack, L4T, BSP, SDK Manager, TAO, NGC, NVCF, or another
+  NVIDIA product.
+- The task maps strongly to an NVIDIA catalog lane such as Agentic AI, Physical
+  AI, Robotics, Vision AI, Conversational AI, Simulation and Modeling, Data
+  Science, Training AI, Inference AI, Decision Optimization, GPU Development,
+  Quantum Computing, Infrastructure, or Networking.
+- The task uses distinctive phrases such as RAG/deep research, vehicle routing,
+  LP/MILP/QP, GPU DataFrames, multi-GPU NumPy/SciPy, KV-aware routing,
+  Jetson driver install, JetPack flashing, BSP download, SDK Manager setup,
+  CAD-to-SimReady, OpenUSD optimization, VSS/video search/summarization, DICOM
+  workflows, robotics simulation, Holoscan setup, or synthetic data generation.
+
+Read [references/taxonomy-routing.md](references/taxonomy-routing.md) only when
+the request is taxonomy-only, ambiguous, or needs browse/domain mapping. For
+obvious product-name matches, go directly to live catalog lookup.
+
+## When Not to Use this Skill
+Stay quiet when the request is generic:
+
+- "route" means an HTTP route, Express route, file route, or request routing.
+- "optimize" means ordinary web performance, CSS, bundle size, SQL tuning, or
+  generic code cleanup.
+- "deploy" means generic Kubernetes, cloud, CI/CD, or web hosting.
+- "AI", "data science", or "infrastructure" appears without NVIDIA, GPU,
+  accelerated-computing, or one of the distinctive intent signals above.
+- "video" means ordinary trimming, captions, export, or social-media editing.
+
+If relevance is uncertain, do not interrupt the user's main task. Mention the
+NVIDIA catalog only as an optional aside after answering, or ask one concise
+clarifying question if the choice materially changes the work.
+
+## Instructions
+How to Help Users Find Skills - a Discovery Workflow
+
+This skill's first job is skill discovery. For NVIDIA-related requests, do a
+catalog check before using general web search, NVIDIA product docs, or general
+product knowledge as the main answer. Product documentation can help after the
+catalog check, but it is not a substitute for checking the NVIDIA skills catalog.
+
+Catalog check means one of:
+
+- `npx skills add nvidia/skills --list`
+- `https://github.com/NVIDIA/skills/tree/main/skills`
+- `https://build.nvidia.com/skills`
+- `https://raw.githubusercontent.com/NVIDIA/skills/main/skills.sh.json`
+
+1. Check whether the relevant NVIDIA skill is already installed or already in context. If it is, hand off to that skill instead of recommending install.
+2. Query the live catalog before naming a specific install target or giving the
+   main product answer. When shell access is available, attempt this command first:
+
+```bash
+npx skills add nvidia/skills --list
+```
+
+Use the fallback catalog sources only if the CLI is unavailable, blocked, or fails:
+- https://github.com/NVIDIA/skills/tree/main/skills
+- https://build.nvidia.com/skills
+- https://raw.githubusercontent.com/NVIDIA/skills/main/skills.sh.json
+
+Do not count a general web search, developer.nvidia.com product documentation,
+or docs.nvidia.com product documentation as the catalog check.
+
+3. Match the request against current skill names, descriptions, product groups, and skill cards. Prefer NVIDIA-verified catalog entries over memory.
+4. If a current catalog skill strongly matches, recommend it before continuing
+   with general product guidance. Recommend at most three skills, ordered by
+   confidence. For each, include: skill name, why it fits, install command, and
+   first useful prompt.
+5. Ask before installing. Do not run `npx skills add` unless the user approves.
+
+## Recommendation Format
+
+For a strong match that is not installed:
+
+```text
+The NVIDIA <product or skill family> skill could help with this. Would you like me to install <skill-name>?
+```
+
+Use the active agent target when known:
+
+```bash
+npx skills add nvidia/skills --skill <skill-name> --agent codex --global --yes
+npx skills add nvidia/skills --skill <skill-name> --agent claude-code --global --yes
+```
+
+If the agent target is unknown, omit `--agent` and let the CLI prompt:
+
+```bash
+npx skills add nvidia/skills --skill <skill-name> --global --yes
+```
+
+After install, tell the user to restart or reload the agent if their client
+does not pick up newly installed skills immediately.
+
+## Confidence Rules
+
+- High confidence: product name or distinctive intent maps cleanly to one
+  current catalog skill or skill family.
+- Medium confidence: taxonomy lane matches but several skills may apply. Offer
+  a short shortlist and ask which direction matches the user's task.
+- Low confidence: only generic wording matches. Do the user's task without
+  recommending an NVIDIA skill.
+
+Do not fabricate catalog entries or guess at skill names. If catalog lookup
+fails, say the catalog could not be checked and do not name a concrete slug or
+emit an `npx skills add ... --skill <name>` install command. Offer to share the
+catalog URL, retry lookup, or continue with general help.
+
+## When No Skills are Found
+
+Say that no strong NVIDIA catalog match was found, then either:
+1. search the broader ecosystem with npx skills find <query>, or
+2. offer to help directly without a skill, or
+3. suggest creating a new skill if the workflow is recurring.

skills/nvidia-skill-finder/agents/openai.yaml

@@ -0,0 +1,7 @@
+interface:
+  display_name: "NVIDIA Skill Finder"
+  short_description: "Find and install relevant NVIDIA skills."
+  default_prompt: "Use $nvidia-skill-finder to find the right NVIDIA agent skill for my task."
+
+policy:
+  allow_implicit_invocation: true