Contribute a new or updated third-party framework integration for NeMo Relay
Scanned 9/3/2026
Install to Claude Code
npx -y skills add NVIDIA/NeMo-Relay --skill contribute-integration --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Contribute Integration?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/nvidia-contribute-integration)More formats (shields.io, HTML) on the badges page.
---
name: contribute-integration
description: Contribute a new or updated third-party framework integration for NeMo Relay
author: NVIDIA Corporation and Affiliates
license: Apache-2.0
---
# 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`
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', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.