[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BGY7D0734P19A0YV64AR5S":3,"skill-same:01M7BGY7D0734P19A0YV64AR5S":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":13,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7BGY7D0734P19A0YV64AR5S","nemo-relay-get-started",null,"Use this skill when first-time NeMo Relay users want to try Relay, choose the least-complex supported quick start, or verify initial value through the CLI, a maintained integration, or direct Python, Node.js, or Rust instrumentation before production setup.","dawsonblock\u002FNEMO","dawsonblock","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F56236740?v=4","01M72Y87EG0A5JP9CKS7EYX8VM","01M7BGVFAXJ69RPAJYQ1XB52MZ",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-get-started\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: nemo-relay-get-started\ndescription: Use this skill when first-time NeMo Relay users want to try Relay, choose the least-complex supported quick start, or verify initial value through the CLI, a maintained integration, or direct Python, Node.js, or Rust instrumentation before production setup.\nlicense: Apache-2.0\nmetadata:\n  author: NVIDIA Corporation and Affiliates\n---\n\n# Get Started With NeMo Relay\n\nGuide a new user to visible Relay value with the least complicated applicable\ntrial. Do not begin with production deployment or Relay's full architecture.\nKeep the first run focused on one observable success path.\n\n## Choose A Try-Now Path\n\nEvaluate these paths in order. Use the first one that fits the user's stated\ngoal and existing environment.\n\n1. **CLI try-now (default)**: choose this for a generic \"try Relay\" request or\n   when the user wants value without modifying application code. Run Codex or\n   Claude Code through the local CLI wrapper. Read\n   [CLI Try-Now](references\u002Fcli-try-now.md).\n2. **Hermes Agent native path**: choose this when Hermes Agent owns the\n   execution boundary. Explain that NeMo Relay is built in and requires no\n   separate Relay installation, observability plugin, or Relay CLI setup.\n   State explicitly: \"Hermes Agent understands NeMo Relay plugin\n   configurations.\" Stop after confirming the native integration. Do not\n   provide installation or observability-configuration instructions, and do\n   not continue into the generic plugin progression.\n3. **Built-in integrations try-now**: choose this when an existing LangChain,\n   LangGraph, Deep Agents, or OpenClaw application owns the execution boundary.\n   Prefer the maintained supported integration over manual wrapping. Read\n   [Built-In Integrations Try-Now](references\u002Fbuilt-in-integrations-try-now.md).\n4. **Language-specific manual try-now**: choose this when the user's Python,\n   Node.js, or Rust application directly owns its tool or LLM call sites and no\n   maintained integration is the better boundary. Read\n   [Manual Language Try-Now](references\u002Fmanual-language-try-now.md).\n\nDo not ask the user to choose among all four when their request, manifest, or\nframework already identifies the boundary. For an unspecified request, use the\nCLI path. When more than one CLI agent is available, ask one concise question\nto select the agent.\n\n## Resolve Installation Without Looping\n\nSelect the try-now path before choosing an install package.\n\n- CLI path -> verify `nemo-relay --version`; if missing, use\n  `nemo-relay-install` for the CLI outcome.\n- Hermes Agent native path -> do not install or configure Relay separately.\n- Built-in integration path -> use `nemo-relay-install` for the named\n  framework or harness package.\n- Manual language path -> use `nemo-relay-install` for the detected language\n  package.\n\nIf installation already succeeded, preserve the chosen path and continue from\nits next step. Do not ask the install-path question again or bounce between the\ninstall and get-started skills.\n\n## Apply The Common First-Value Contract\n\nDo not apply this section to the Hermes Agent native path.\n\nFollow the selected reference, then:\n\n1. Inspect the target environment and existing Relay configuration before\n   proposing changes.\n   Treat repository-local `.nemo-relay\u002Fconfig.toml` and\n   `.nemo-relay\u002Fplugins.toml` as unsupported project configuration. Do not\n   create, edit, merge, or trust those files as active Relay configuration.\n2. Explain the attachment boundary and show the exact minimal change.\n3. Obtain confirmation before writing configuration, modifying application\n   code, or launching a model-consuming run.\n4. Use a non-sensitive, read-only trial and exercise one representative tool\n   and LLM path when the selected surface exposes both.\n5. Verify observable evidence from the selected path rather than treating a\n   successful application result as proof that Relay is active.\n6. Summarize the captured root, tool, and model relationships without dumping\n   prompts, credentials, or complete event payloads.\n\nExplain only the concepts visible in the result: the chosen attachment\nboundary, scopes and parentage, captured lifecycle events, and how subscribers\nor the Observability plugin make those events inspectable. Keep instrumentation\nand export distinct.\n\n## Continue With One Plugin\n\nDo not apply this section to the Hermes Agent native path.\n\nStop the initial try-now workflow when the selected path's success checks pass.\nThen make one additional built-in plugin the primary suggested next step.\n\nExplain Relay's core progression: instrument an execution boundary once, then\nchange or extend behavior through plugin configuration without repeatedly\nrewriting those call sites. Easy plugin configuration and reconfiguration is\nthe main value to demonstrate after the first observable proof.\n\nIf the selected path did not use plugin-managed Observability, add it first to\nestablish the reusable plugin path. If Observability already produced the\nproof, ask what outcome matters next and recommend exactly one plugin:\n\n- Adaptive -> adaptive runtime behavior and optimization\n- NeMo Guardrails -> policy checks around managed execution\n- PII Redaction -> sanitization of sensitive observability payloads\n- Model Pricing -> cost estimates for managed LLM responses\n\nUse the\n[plugin overview](https:\u002F\u002Fdocs.nvidia.com\u002Fnemo\u002Frelay\u002Fdev\u002Fconfigure-plugins\u002Fabout) to\nselect the next component. Preview its smallest configuration, obtain\nconfirmation, and verify its behavior before layering in another plugin.\n\nUse another handoff only after the user accepts or declines plugin progression,\nor when the demonstrated boundary does not yet cover the intended workflow:\n\n- Direct application expansion -> `nemo-relay-instrument-calls`\n- Unsupported framework or harness integration ->\n  `nemo-relay-integrate-upstream`\n- Additional exporters or durable observability configuration ->\n  `nemo-relay-plugin-observability`\n- A different package or supported integration -> `nemo-relay-install`\n- Persistent Claude Code or Codex loading -> `nemo-relay-install`; for Codex\n  Desktop, complete its recovery-note safety gate before changing global config\n- Missing hooks, gateway traffic, or events -> `nemo-relay doctor`,\n  `nemo-relay doctor --json`, or `nemo-relay-debug-runtime-integration`\n\nDo not configure production OTLP backends, model pricing, guardrails, adaptive\ntuning, custom plugins, Go or FFI examples during the quick start. Mention\noptional plugins only after the initial proof and add only the one the user\nselects.\n\n## Public Entry Points\n\nUse these public entry points for current product documentation:\n\n- [CLI overview](https:\u002F\u002Fdocs.nvidia.com\u002Fnemo\u002Frelay\u002Fdev\u002Fnemo-relay-cli\u002Fabout)\n- [Maintained integrations](https:\u002F\u002Fdocs.nvidia.com\u002Fnemo\u002Frelay\u002Fdev\u002Fsupported-integrations\u002Fabout)\n- [Language quick starts](https:\u002F\u002Fdocs.nvidia.com\u002Fnemo\u002Frelay\u002Fdev\u002Fgetting-started\u002Fquick-start)\n- [Plugin selection](https:\u002F\u002Fdocs.nvidia.com\u002Fnemo\u002Frelay\u002Fdev\u002Fconfigure-plugins\u002Fabout)\n","# Get Started With NeMo Relay\n\nGuide a new user to visible Relay value with the least complicated applicable\ntrial. Do not begin with production deployment or Relay's full architecture.\nKeep the first run focused on one observable success path.\n\n## Choose A Try-Now Path\n\nEvaluate these paths in order. Use the first one that fits the user's stated\ngoal and existing environment.\n\n1. **CLI try-now (default)**: choose this for a generic \"try Relay\" request or\n   when the user wants value without modifying application code. Run Codex or\n   Claude Code through the local CLI wrapper. Read\n   [CLI Try-Now](references\u002Fcli-try-now.md).\n2. **Hermes Agent native path**: choose this when Hermes Agent owns the\n   execution boundary. Explain that NeMo Relay is built in and requires no\n   separate Relay installation, observability plugin, or Relay CLI setup.\n   State explicitly: \"Hermes Agent understands NeMo Relay plugin\n   configurations.\" Stop after confirming the native integration. Do not\n   provide installation or observability-configuration instructions, and do\n   not continue into the generic plugin progression.\n3. **Built-in integrations try-now**: choose this when an existing LangChain,\n   LangGraph, Deep Agents, or OpenClaw application owns the execution boundary.\n   Prefer the maintained supported integration over manual wrapping. Read\n   [Built-In Integrations Try-Now](references\u002Fbuilt-in-integrations-try-now.md).\n4. **Language-specific manual try-now**: choose this when the user's Python,\n   Node.js, or Rust application directly owns its tool or LLM call sites and no\n   maintained integration is the better boundary. Read\n   [Manual Language Try-Now](references\u002Fmanual-language-try-now.md).\n\nDo not ask the user to choose among all four when their request, manifest, or\nframework already identifies the boundary. For an unspecified request, use the\nCLI path. When more than one CLI agent is available, ask one concise question\nto select the agent.\n\n## Resolve Installation Without Looping\n\nSelect the try-now path before choosing an install package.\n\n- CLI path -> verify `nemo-relay --version`; if missing, use\n  `nemo-relay-install` for the CLI outcome.\n- Hermes Agent native path -> do not install or configure Relay separately.\n- Built-in integration path -> use `nemo-relay-install` for the named\n  framework or harness package.\n- Manual language path -> use `nemo-relay-install` for the detected language\n  package.\n\nIf installation already succeeded, preserve the chosen path and continue from\nits next step. Do not ask the install-path question again or bounce between the\ninstall and get-started skills.\n\n## Apply The Common First-Value Contract\n\nDo not apply this section to the Hermes Agent native path.\n\nFollow the selected reference, then:\n\n1. Inspect the target environment and existing Relay configuration before\n   proposing changes.\n   Treat repository-local `.nemo-relay\u002Fconfig.toml` and\n   `.nemo-relay\u002Fplugins.toml` as unsupported project configuration. Do not\n   create, edit, merge, or trust those files as active Relay configuration.\n2. Explain the attachment boundary and show the exact minimal change.\n3. Obtain confirmation before writing configuration, modifying application\n   code, or launching a model-consuming run.\n4. Use a non-sensitive, read-only trial and exercise one representative tool\n   and LLM path when the selected surface exposes both.\n5. Verify observable evidence from the selected path rather than treating a\n   successful application result as proof that Relay is active.\n6. Summarize the captured root, tool, and model relationships without dumping\n   prompts, credentials, or complete event payloads.\n\nExplain only the concepts visible in the result: the chosen attachment\nboundary, scopes and parentage, captured lifecycle events, and how subscribers\nor the Observability plugin make those events inspectable. Keep instrumentation\nand export distinct.\n\n## Continue With One Plugin\n\nDo not apply this section to the Hermes Agent native path.\n\nStop the initial try-now workflow when the selected path's success checks pass.\nThen make one additional built-in plugin the primary suggested next step.\n\nExplain Relay's core progression: instrument an execution boundary once, then\nchange or extend behavior through plugin configuration without repeatedly\nrewriting those call sites. Easy plugin configuration and reconfiguration is\nthe main value to demonstrate after the first observable proof.\n\nIf the selected path did not use plugin-managed Observability, add it first to\nestablish the reusable plugin path. If Observability already produced the\nproof, ask what outcome matters next and recommend exactly one plugin:\n\n- Adaptive -> adaptive runtime behavior and optimization\n- NeMo Guardrails -> policy checks around managed execution\n- PII Redaction -> sanitization of sensitive observability payloads\n- Model Pricing -> cost estimates for managed LLM responses\n\nUse the\n[plugin overview](https:\u002F\u002Fdocs.nvidia.com\u002Fnemo\u002Frelay\u002Fdev\u002Fconfigure-plugins\u002Fabout) to\nselect the next component. Preview its smallest configuration, obtain\nconfirmation, and verify its behavior before layering in another plugin.\n\nUse another handoff only after the user accepts or declines plugin progression,\nor when the demonstrated boundary does not yet cover the intended workflow:\n\n- Direct application expansion -> `nemo-relay-instrument-calls`\n- Unsupported framework or harness integration ->\n  `nemo-relay-integrate-upstream`\n- Additional exporters or durable observability configuration ->\n  `nemo-relay-plugin-observability`\n- A different package or supported integration -> `nemo-relay-install`\n- Persistent Claude Code or Codex loading -> `nemo-relay-install`; for Codex\n  Desktop, complete its recovery-note safety gate before changing global config\n- Missing hooks, gateway traffic, or events -> `nemo-relay doctor`,\n  `nemo-relay doctor --json`, or `nemo-relay-debug-runtime-integration`\n\nDo not configure production OTLP backends, model pricing, guardrails, adaptive\ntuning, custom plugins, Go or FFI examples during the quick start. Mention\noptional plugins only after the initial proof and add only the one the user\nselects.\n\n## Public Entry Points\n\nUse these public entry points for current product documentation:\n\n- [CLI overview](https:\u002F\u002Fdocs.nvidia.com\u002Fnemo\u002Frelay\u002Fdev\u002Fnemo-relay-cli\u002Fabout)\n- [Maintained integrations](https:\u002F\u002Fdocs.nvidia.com\u002Fnemo\u002Frelay\u002Fdev\u002Fsupported-integrations\u002Fabout)\n- [Language quick starts](https:\u002F\u002Fdocs.nvidia.com\u002Fnemo\u002Frelay\u002Fdev\u002Fgetting-started\u002Fquick-start)\n- [Plugin selection](https:\u002F\u002Fdocs.nvidia.com\u002Fnemo\u002Frelay\u002Fdev\u002Fconfigure-plugins\u002Fabout)\n",{"name":5,"license":14,"metadata":23,"description":7},{"author":24},"NVIDIA Corporation and Affiliates","main","13944d7d2b1a4bc9aa91fa061bed6fe63fad7979","skills\u002Fnemo-relay-get-started","https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO","https:\u002F\u002Fgithub.com\u002Fdawsonblock","2026-09-30 06:03:35",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add dawsonblock\u002FNEMO --skill nemo-relay-get-started",{"tool":37,"command":38},"bunx","bunx skills add dawsonblock\u002FNEMO --skill nemo-relay-get-started",{"tool":40,"command":41},"pnpm","pnpm dlx skills add dawsonblock\u002FNEMO --skill nemo-relay-get-started","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-get-started\u002FSKILL.md",true,[45,51,55,59,63,67,71],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"BENCHMARK.md","REFERENCE","参考文档",5221,"https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-get-started\u002FBENCHMARK.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"evals\u002Fevals.json",17224,"https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-get-started\u002Fevals\u002Fevals.json",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fbuilt-in-integrations-try-now.md",4012,"https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-get-started\u002Freferences\u002Fbuilt-in-integrations-try-now.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fcli-try-now.md",9704,"https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-get-started\u002Freferences\u002Fcli-try-now.md",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fmanual-language-try-now.md",3130,"https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-get-started\u002Freferences\u002Fmanual-language-try-now.md",{"path":68,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":69,"sourceHtmlUrl":70},"skill-card.md",4693,"https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-get-started\u002Fskill-card.md",{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"skill.oms.sig","OTHER","其他",5345,"https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-get-started\u002Fskill.oms.sig",[78,85,92,99,106,113],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M7BGZHFG0R2E7EN6JKK8A6XK","nemo-relay-plugin-observability","Use this skill when choosing or configuring NeMo Relay 0.6 or 0.7 observability through the built-in plugin, subscribers, or exporters, including raw ATOF events, ATIF trajectories, OpenTelemetry, OpenInference, or custom event handling.","https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-plugin-observability\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M7BGZDJ0YSBESTS38D9FDRNA","nemo-relay-plugin-build","Use this skill when building or packaging reusable NeMo Relay runtime behavior as an embedded configuration component or a manifest-backed `rust_dynamic` native or `worker` gRPC plugin, with deterministic validation and rollback-safe registration.","https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-plugin-build\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M7BGZ9KYD60WWHH6C5H9DKPM","nemo-relay-plugin-adaptive-tuning","Use this skill when baseline NeMo Relay instrumentation exists and the user wants to configure or evaluate adaptive plugin behavior, including telemetry, state, adaptive_hints, tool_parallelism, ACG, hint consumption, or measured rollout.","https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-plugin-adaptive-tuning\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":18},"01M7BGZ3XE0H92KR4E3ENNXQNX","nemo-relay-migrate-from-flow","Use this skill when migrating applications, examples, integrations, documentation, manifests, or repository code from NeMo Flow to NeMo Relay across Python, Rust, Node.js, Go, C FFI, CLI, configuration, and observability surfaces.","https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-migrate-from-flow\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":18},"01M7BGYWESQ44Z80VBZ3B3WB30","nemo-relay-integrate-upstream","Use this skill when assessing, extending, or implementing NeMo Relay support in an agent harness or agent framework, including coding agents and orchestration runtimes, when the host lacks Relay support or an existing integration needs deeper coverage. It identifies the host's execution boundaries and extension points, selects an appropriate attachment method for each boundary, and verifies the resulting coverage.","https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-integrate-upstream\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":18},"01M7BGYRQ1PTFVVC8KGA8ZE4MN","nemo-relay-instrument-typed-wrappers","Use this skill when adding NeMo Relay typed wrappers, domain types, or provider codecs while preserving JSON middleware semantics and caller-visible behavior.","https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-instrument-typed-wrappers\u002FSKILL.md",[],[]]