Jason Dudash
55f8f7a5a4
Replace cuopt-user-rules with cuopt-numerical-optimization-api-python in the curated nvidia-skills bundle. cuopt-user-rules was pruned from the cuOpt catalog in NVIDIA/skills#300, so it would dangle on the next sync; cuopt-numerical-optimization-api-python is the flagship cuOpt skill (the README quickstart example) and remains in the catalog. Structural change (skill set changed) bumps the plugin minor version 1.0.3 -> 1.1.0 via version-plugins.py, reflected in all three (Claude, Codex, Cursor) plugin manifests. Signed-off-by: Jason Dudash <jdudash@nvidia.com>
plugins/ — generated plugin bundles
Each subdirectory here is a self-contained plugin built from a source
definition in plugins.d/ by
.github/scripts/build-plugins.py.
A plugin folder typically contains:
.claude-plugin/plugin.json— Claude plugin manifest.codex-plugin/plugin.json— Codex plugin manifestskills/— the bundled skills (real files or symlinks back into the top-levelskills/catalog, depending onskill_files:in the source yaml)assets/— optional logo and other hand-maintained assets
Don't edit these files directly
With the exception of curated plugins (see below), everything under
plugins/<name>/ is regenerated on every build. To change a
plugin's metadata or skill list, edit plugins.d/<name>.yml and re-run:
.github/scripts/build-plugins.sh
See plugins.d/README.md for the full
authoring workflow.
Curated plugins
A plugin folder that contains its own .skills-manifest.yml (instead of
having a matching plugins.d/<name>.yml) is curated — the build
script only refreshes its skills/ links and leaves the manifests,
assets, and marketplace entries hand-edited. The current example is
nvidia-skills/, which ships to the official
Anthropic and OpenAI plugin marketplaces.