Skip to content

Add TileGym to the NVIDIA Agent Skills catalog#22

Merged
mosheabr merged 1 commit intoNVIDIA:mainfrom
hannahli-nv:add-tilegym
May 4, 2026
Merged

Add TileGym to the NVIDIA Agent Skills catalog#22
mosheabr merged 1 commit intoNVIDIA:mainfrom
hannahli-nv:add-tilegym

Conversation

@hannahli-nv
Copy link
Copy Markdown
Contributor

@hannahli-nv hannahli-nv commented Apr 17, 2026

Onboarding type

  • New product onboarding (new components.d/tilegym.yml for NVIDIA/TileGym)

For new product onboarding — author affirmations

By submitting this PR, I confirm on behalf of my team:

  • Skills cleared for open source release per NVIDIA's internal IP review process (six-question check, all answers affirmative)
  • License selected: Dual (Apache 2.0 + CC-BY 4.0)
  • No new license or new third-party component introduced beyond what the source repo already carries
  • Source repo is public and under an NVIDIA-owned GitHub org (NVIDIA/TileGym)
  • .agents/skills/ path used (TileGym is on the canonical layout; .claude/skills is a symlink → ../.agents/skills)

What this PR adds

components.d/tilegym.yml registering NVIDIA/TileGym for catalog sync under the new components.d schema. TileGym ships 6 skills under .agents/skills/:

  • adding-cutile-kernel — guides adding a new cuTile kernel op to TileGym
  • converting-cutile-to-julia — port a cuTile Python kernel to Julia
  • converting-cutile-to-triton — port a cuTile kernel to Triton
  • cutile-python — author and orchestrate cuTile Python kernels
  • improve-cutile-kernel-perf — iteratively optimize cuTile kernel performance
  • monkey-patch-kernels-to-transformers — integrate TileGym kernels into HuggingFace Transformers

links.discussions: false — TileGym has Issues but no Discussions tab. CONTRIBUTING.md and SECURITY.md are present at default paths.

The commit history of this branch was rebased to the new schema: a merge commit drops the obsolete components.yml/README.md edits (both superseded — components.yml is gone, README.md is now auto-generated), and a follow-up commit adds the single components.d/tilegym.yml entry.

All PRs

  • All commits signed off with DCO (Signed-off-by: Hannah Li <hanli@nvidia.com>)

@hannahli-nv hannahli-nv requested a review from mosheabr as a code owner April 17, 2026 07:09
@mosheabr mosheabr mentioned this pull request May 1, 2026
12 tasks
@hannahli-nv hannahli-nv requested a review from sayalinvidia as a code owner May 4, 2026 05:38
Copy link
Copy Markdown
Collaborator

@mosheabr mosheabr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve.

Verified end-to-end:

  • Source repo NVIDIA/TileGym: public NVIDIA-org, not archived
  • LICENSE explicitly dual-licenses .agents/ content as CC-BY-4.0 AND Apache-2.0 (rest of repo is MIT). The .agents/ scope is exactly what syncs into the catalog, so the skill content matches the menu — Dual claim verified at source.
  • has_discussions: false upstream → correctly set as links.discussions: false in tilegym.yml
  • 6 skill directories upstream match the body's enumerated list
  • Single-file PR (components.d/tilegym.yml only) — correct under the post-#40 flow
  • Filename slug matches name-derived slug
  • All 6 commits DCO signed
  • All 5 author affirmations checked

Thanks for patiently rebasing and migrating through the architecture flip.

Registers NVIDIA/TileGym for catalog sync under the new components.d/<slug>.yml
schema. TileGym ships 6 skills under .agents/skills/:

  - adding-cutile-kernel
  - converting-cutile-to-julia
  - converting-cutile-to-triton
  - cutile-python
  - improve-cutile-kernel-perf
  - monkey-patch-kernels-to-transformers

links.discussions is set to false because TileGym has Issues but no
Discussions tab. CONTRIBUTING.md and SECURITY.md are at default paths.

License: Dual (Apache-2.0 + CC-BY-4.0).
Signed-off-by: Hannah Li <hanli@nvidia.com>
@mosheabr mosheabr merged commit 908854f into NVIDIA:main May 4, 2026
1 check passed
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.

2 participants