mcpbeat

Contribute API

nvidia/contribute-api

Contribute a new NeMo Relay public API surface safely, with binding parity and docs in mind

260 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
102
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/NVIDIA/NeMo-Relay --skill contribute-api

The instruction itself

5 sections, as written by the author

Contribute A New API Surface

Companion Guidance

Use karpathy-guidelines alongside this skill for implementation or review

work. Keep changes scoped, surface assumptions, and define focused validation

before editing.

Use this skill when contributing a public API addition or behavior change to the

runtime or bindings.

Default Guidance

  • Start from the shared core behavior first
  • Decide which bindings must expose the new surface
  • Follow the parity checklist in add-binding-feature
  • Update docs and examples in the same branch

Minimum Acceptance

  • Public behavior is clearly described
  • Every affected binding is covered
  • The validation matrix matches the changed surfaces
  • PR notes explain the user-facing change

References

  • add-binding-feature
  • validate-change
  • CONTRIBUTING.md
  • review-doc-style

How to use it

Copy the folder

Take nvidia/contribute-api from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.