components.d/deepstream: flat layout + discussions override - #109
Merged
Conversation
Restructure to one-entry-per-skill (flat-layout convention adopted 2026-05-28 — skills land at skills/<skill-name>/ top level). Add links.discussions: false since NVIDIA-AI-IOT/DeepStream_Coding_Agent has Discussions disabled. Source repo is fully 5/5 compliant as of Unni's PR #3 today (sig + skill-card + evals.json + BENCHMARK.md for both deepstream-dev and deepstream-import-vision-model). DeepStream is the second component to reach full artifact compliance after Skill Card Generator. Next sync will land both skills flat at skills/deepstream-dev/ and skills/deepstream-import-vision-model/. Signed-off-by: Moshe Abramovitch <moshea@nvidia.com>
3 tasks
mosheabr
added a commit
that referenced
this pull request
May 28, 2026
PR #109 flattened components.d/deepstream.yml to put DeepStream skills at top-level: skills/deepstream-dev/ and skills/deepstream-import-vision-model/. The next sync (PR #110) correctly mirrored content into those flat locations. However, the previous nested skills/deepstream/ directory (with the same two skills under a 'deepstream' parent dir) was left behind by the sync — anti-pattern #1 in the catalog-pr-reviewer skill: the sync workflow doesn't auto-clean directories that are no longer referenced by any components.d/<slug>.yml entry. Removing it here to eliminate the duplicate and complete the flat-layout cutover. Authoritative content now lives at: - skills/deepstream-dev/ - skills/deepstream-import-vision-model/ Signed-off-by: Moshe Abramovitch <moshea@nvidia.com>
2 tasks
mosheabr
pushed a commit
that referenced
this pull request
May 29, 2026
TileGym PR NVIDIA/TileGym#132 migrated all 7 cuTile skill folders from `.agents/skills/` to the canonical release-facing `skills/` path. The previous `.agents/skills` was retained as a backward-compatibility symlink for tools that still expect the agentskills.io layout, but the sync workflow's git sparse-checkout + rsync does not reliably follow that symlink — it would either copy just the symlink-as-file or miss the contents. Update `path` from `.agents/skills/` → `skills/` so the sync workflow reads from the public-facing path directly. Single-entry parent-path form is retained (rather than per-skill flat layout) because all 7 cuTile skills are intended for the public catalog — there is no contributor/maintainer-only skill subset to filter out — and the parent-path form auto-discovers any new TileGym skills without requiring further nvidia/skills PRs. Also add the standard Apache SPDX header to match the convention adopted across components.d/ on 2026-05-28 (cf. #109, #113). Catalog effect: skills under `nvidia/skills/skills/TileGym/<name>/` will continue to populate via the existing per-skill sync-compliance gate (`skill.oms.sig` + `skill-card.md` + `evals.json`). The first TileGym skills landing `evals.json` are tracked in NVIDIA/TileGym#135 (adding-cutile-kernel, cutile-python); the remaining 5 will follow in subsequent PRs. Signed-off-by: Hannah Li <hanli@nvidia.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
components.d/deepstream.ymlto flat layout (one entry per skill) per the convention adopted 2026-05-28links.discussions: falsesince the source repo (NVIDIA-AI-IOT/DeepStream_Coding_Agent) has Discussions disabledSource state
Both DeepStream skills are fully 5/5 artifact-compliant as of Unni Sreekumar's merge today (
3daf16ainNVIDIA-AI-IOT/DeepStream_Coding_AgentPR #3):DeepStream is the second component to reach full artifact compliance after Skill Card Generator (which landed earlier today). Good Computex story.
What sync will do after this merges
skills/deepstream/<skill>/(nested under PascalCase-ish parent dir)skills/deepstream-dev/andskills/deepstream-import-vision-model/(flat top-level)Today the catalog shows 0 DeepStream skills because the previous yml + missing source artifacts → enforcement workflow dropped them. After this lands, the next 06:00 / 18:00 UTC sync will publish both skills cleanly.
Heads-up — allowlist gap (for Sayali)
NVIDIA-AI-IOTis NOT innvskills-ci/config/onboarded-repositories.jsonallowed_owners(currently: NVIDIA, NVIDIA-AI-Blueprints, NVIDIA-dev, ai-dynamo, nvidia-riva, NVIDIA-NeMo, nv-legate). That's why Unni signed in GitLab (DeepStreamSDK/ds-copilot) and mirrored to GitHub manually. The artifacts are correctly there now, but addingNVIDIA-AI-IOTwould let future DeepStream signing runs happen natively in GitHub. Filing this as a separate ask.Test plan
skills/deepstream-dev/andskills/deepstream-import-vision-model/land in catalog with full artifact set🤖 Generated with Claude Code