Contribute a new NeMo Relay public API surface safely, with binding parity and docs in mind
Scanned 9/3/2026
Install to Claude Code
Skills Directorynpx -y skills add NVIDIA/NeMo-Relay --skill contribute-api --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Contribute Api?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/nvidia-contribute-api)More formats (shields.io, HTML) on the badges page.
---
name: contribute-api
description: Contribute a new NeMo Relay public API surface safely, with binding parity and docs in mind
author: NVIDIA Corporation and Affiliates
license: Apache-2.0
---
# 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`
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
