---
name: Framework Integration Contribution
slug: framework-integration-contribution
category: AI Engineering
description: Framework Integration Contribution guides adding or updating a third-party framework or plugin integration for NeMo Relay. Use it when wiring Relay into public APIs for frameworks like LangChain or LangGraph while preserving default behavior when Relay is absent.
github: "https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/contribute-integration"
language: Rust
stars: 165
forks: 67
install: "npx degit https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/contribute-integration ~/.claude/skills/contribute-integration"
installs_to: ~/.claude/skills/contribute-integration
source_path: .agents/skills/contribute-integration/SKILL.md
collection_size: 25
category_size: 3670
collection_url: "https://dirskills.com/collections/NVIDIA/NeMo-Relay"
added: 2026-09-08T05:35:14.768Z
last_synced: 2026-09-08T05:35:14.768Z
canonical_url: "https://dirskills.com/skills/framework-integration-contribution"
---

# Framework Integration Contribution

Framework Integration Contribution guides adding or updating a third-party framework or plugin integration for NeMo Relay. Use it when wiring Relay into public APIs for frameworks like LangChain or LangGraph while preserving default behavior when Relay is absent.

**Install:**

```bash
npx degit https://github.com/NVIDIA/NeMo-Relay/tree/main/.agents/skills/contribute-integration ~/.claude/skills/contribute-integration
```

## README

# 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`