contribute-integration
Skill238 starsChanged 2 months agoApache-2.0View on GitHub
Add or change a third-party framework integration that attaches NeMo Relay to framework tool, LLM, or lifecycle boundaries. Do not use for core runtime or binding-only changes.
In this repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-binding-featureSkill
- add-middlewareSkill
- check-release-deploymentsSkill
- contribute-docsSkill
- create-beta-tagSkill
- create-rc-tagSkill
- create-release-tagSkill
- draft-release-notesSkill
- maintain-ciSkill
- maintain-dynamic-pluginsSkill
- maintain-observabilitySkill
- maintain-optimizerSkill
- maintain-packagingSkill
- prepare-code-freezeSkill
- prepare-prSkill
- rename-surfacesSkill
- review-doc-styleSkill
- update-project-versionSkill
- nemo-relay-debug-runtime-integrationSkill
- nemo-relay-get-startedSkill
- nemo-relay-installSkill
- nemo-relay-instrument-callsSkill
- nemo-relay-instrument-context-isolationSkill
- nemo-relay-instrument-typed-wrappersSkill
- nemo-relay-integrate-upstreamSkill
- nemo-relay-migrate-from-flowSkill
- nemo-relay-plugin-adaptive-tuningSkill
- nemo-relay-plugin-buildSkill
- nemo-relay-plugin-observabilitySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use this skill when contributing an integration with a framework or plugin such as LangChain, LangGraph, Deep Agents, Google ADK, or …
- Distinctive: line 16
Keep NeMo Relay optional
- Distinctive: line 17
Use stable, documented framework or plugin APIs
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Contribute A Framework Integration
Use this skill when contributing an integration with a framework or plugin such as LangChain, LangGraph, Deep Agents, Google ADK, 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
ToolExecutionResultto Relay and unwrap.resultonly 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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.