Skip to content

Add Nsight AI Porting Agent to the skills catalog - #866

Open
nv-unnikrishnankgs wants to merge 1 commit into
NVIDIA:mainfrom
nv-unnikrishnankgs:catalog/add-nsight-ai-porting-agent-20261113
Open

nv-unnikrishnankgs wants to merge 1 commit into
NVIDIA:mainfrom
nv-unnikrishnankgs:catalog/add-nsight-ai-porting-agent-20261113

Conversation

@nv-unnikrishnankgs

Copy link
Copy Markdown
Contributor

Onboarding type

  • New product onboarding (new components.d/<slug>.yml file)
  • Other: add a skill to the existing Nsight component and align product grouping.

Summary

  • Register Nsight AI Porting Agent as the flat catalog entry nsight-port-cpu-to-gpu.
  • Source: NVIDIA/nsight.
  • Add the canonical umbrella product Nsight and use it for both Nsight component entries. This intentionally changes Compute Sanitizer's catalog product grouping from Compute Sanitizer to Nsight; its source path and catalog directory remain unchanged.
  • Update only that existing generated metadata field so the catalog's byte-stability check stays consistent.

Registration

repo: NVIDIA/nsight
path: skills/nsight-port-cpu-to-gpu/
catalog_dir: nsight-port-cpu-to-gpu

Scope and licensing

This is an existing-component catalog change, not a new component-file onboarding. The source is already public under NVIDIA and declares CC-BY-4.0 AND Apache-2.0. No new license or third-party component is introduced. No skill files, evals, cards, signatures, or generated skill copies are included in this PR; the catalog sync remains responsible for copying the public source.

Validation

  • Public source directory and SKILL.md exist on NVIDIA/nsight:main.
  • Flat catalog_dir is unique across the component registries.
  • YAML and JSON Schema validation passed.
  • Upstream source-onboarding checks passed for the porting skill, including the signed payload hashes and benchmark requirements.
  • Both Nsight entries resolve to the canonical Nsight product; the existing metadata update changes only product.primary.
  • Diff contains only the component YAML, schema enum, and the one-field generated metadata update.

All PRs

  • All commits signed off with DCO (git commit -s equivalent sign-off).

Other context

The generated metadata update is included because the metadata CI requires checked-in output to stay byte-stable with the component's declared product. All other existing catalog metadata is unchanged.

Register the CPU-to-GPU porting skill and group Nsight skills under the canonical Nsight product. Keep the existing generated product metadata consistent.

Signed-off-by: Unnikrishnan Kizhakkemadam Sreekumar <unnik@nvidia.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant