nvidia/nemo-relay · Archived

contribute-integration

Contribute a new or updated third-party framework integration for NeMo Relay

First seen Jul 3, 2026

Installation

$ npx skills add nvidia/nemo-relay --skill contribute-integration

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from nvidia/nemo-relay · top by installs.

npx skills add nvidia/nemo-relay

Browse all from nvidia/nemo-relay

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 134
License LICENSE
Default branch main
Open issues 2
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseApache-2.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,350 B
  • docs SUMMARY.md 106 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Contribute A Framework Integration

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 an integration with a framework or plugin such as LangChain, LangGraph, Deep Agents, or OpenClaw through its public APIs.

Default Guidance

  • Keep NeMo Relay optional
  • Use stable, documented framework or plugin APIs
  • Wrap tool and LLM paths at the correct framework boundary
  • Preserve the framework's original behavior when NeMo Relay is absent

Checklist

  • Integration pattern follows docs/integrate-into-frameworks/adding-scopes.mdx
  • Integration uses public framework or plugin APIs
  • Managed tool adapters return ToolExecutionResult to Relay and unwrap

.result only at the framework boundary; opaque annotations are preserved through forwarding execution intercepts

  • Relevant integration tests or smoke path pass
  • Docs updated if activation or usage changed

References

  • docs/integrate-into-frameworks/about.mdx
  • validate-change