[zac-wang-nv]

Onboarding type

• New product onboarding (new components.d/<slug>.yml file)
• Other (catalog change, README fix, infrastructure, etc.)

All PRs

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

Other context

Update components.d/video-search-and-summarization.yml for the current shape of the VSS Blueprint repo.

ref: main → ref: develop. The skills tree on develop moved to skills/vss-build-vision-ai/ plus skills/operations/<skill>/; the flat skills/<skill>/ paths the catalog currently points at no longer exist there.

Keep only the build skill and the operational skills. The component now lists:

• vss-build-vision-ai (replaces the retired vss-deploy-profile)
• vss-ask-video, vss-generate-video-report, vss-generate-video-report-rag (new), vss-manage-alerts, vss-manage-video-io-storage, vss-query-analytics, vss-search-archive, vss-summarize-video

Dropped from the catalog: vss-deploy-profile, vss-deploy-dense-captioning, vss-deploy-detection-tracking-2d, vss-deploy-detection-tracking-3d, vss-deploy-video-embedding, vss-generate-video-calibration, vss-setup-behavior-analytics, vss-setup-video-analytics-api. These are per-microservice deployment and tooling skills that VSS no longer publishes to the catalog; vss-build-vision-ai is the single supported deployment entry point.

Heads-up for the sync: that is 8 orphaned skills/<catalog_dir>/ directories, above the PRUNE_CAP of 5 in prune-orphans.sh, so the next sync will write them to the overflow list and flag for triage rather than delete them. I kept this PR to the component file only, since skills/, versions.json, and the .sig files are workflow-owned. Happy to add the deletions here if the PIC prefers, or the prune can be run in two batches.

Every listed path was verified to contain a SKILL.md at its root on NVIDIA-AI-Blueprints/video-search-and-summarization@develop. YAML parses; all catalog_dir values remain unique across components.d/.

🤖 Generated with Claude Code

[mosheabr]

Thanks for this — the path and ref work is accurate, and I appreciate you calling out the prune-cap overflow upfront rather than letting the sync surprise us.

I can't merge it as it stands, though. Requesting changes on three things, all in the source repo rather than in this PR.

1. develop has no signatures. None of the nine declared paths carries a skill.oms.sig on that branch. main does — skills/vss-ask-video/skill.oms.sig is there today, which is what the catalog is currently serving.

This is the one that matters most, because it means the PR wouldn't do what you want even if I merged it. At the next sync all nine would be held with "no signature in source." The seven existing skills would keep serving their old content from main, vss-build-vision-ai and vss-generate-video-report-rag would never land, and the eight dropped skills would still be pruned. The catalog would lose eight skills and gain nothing.

2. The BENCHMARK.md files are placeholders. Each one reads Overall verdict: NOT RUN — no controlled benchmark completed, 0 attempts per task, no agents recorded. We need a real evaluation with a PASS verdict before these can publish.

3. vss-build-vision-ai has no skill card. The other eight have skill-card.md; this one doesn't.

What's already good: DCO sign-off is in place, YAML parses, every declared path does have a SKILL.md at its root, and all catalog_dir values are unique across components.d/ — I checked all of them.

The fix is to run /nvskills-ci on develop in the VSS repo so the skills get evaluated, carded and signed there, then update this PR. One heads-up: that has to run from a branch in the VSS repo itself — the signing flow doesn't work from forks, so a fork PR there would silently produce nothing.

Happy to re-review as soon as develop has the artifacts. And on the eight orphans — once the rest is sorted, tell me whether you'd like them pruned in one pass or split into two batches to stay under the cap.

[mosheabr]

Closing as superseded by #726, which publishes only vss-build-vision-ai from release/3.3.0 for the 3.3.0 release. Zac confirmed the scope in our Slack thread. Thanks!