[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BGY3APCD5JM4GQKMYTMMYG":3,"skill-same:01M7BGY3APCD5JM4GQKMYTMMYG":65},{"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},"01M7BGY3APCD5JM4GQKMYTMMYG","nemo-relay-debug-runtime-integration",null,"Use this skill when NeMo Relay is installed or imported but application-side runtime behavior is missing or incorrect, including load failures, inactive scopes, missing events, and plugin or adaptive wiring problems.","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-debug-runtime-integration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: nemo-relay-debug-runtime-integration\ndescription: Use this skill when NeMo Relay is installed or imported but application-side runtime behavior is missing or incorrect, including load failures, inactive scopes, missing events, and plugin or adaptive wiring problems.\nlicense: Apache-2.0\nmetadata:\n  author: NVIDIA Corporation and Affiliates\n---\n\n# Debug Runtime Integration\n\nUse this skill when NeMo Relay is present in the application but something is not\nworking.\nStart by proving which runtime layer is failing before changing configuration.\n\n## First Checks\n\n- Can the binding or native artifact load?\n- Is there an active scope when the failing call runs?\n- Is the work happening on the expected scope stack?\n- Is the subscriber\u002Fexporter\u002Fplugin configuration actually active?\n- Did the app choose the right public API layer: managed execute vs manual\n  lifecycle vs typed wrappers vs adaptive\u002Fplugins?\n\n## Common Failure Classes\n\n- Python native extension missing\n- Go dynamic library not on the loader path\n- Node native addon not built or not loading\n- Execute call outside a scope\n- Missing events because registration never happened\n- Concurrency causing the wrong scope stack to be active\n- Adaptive component never initialized or config validation ignored\n\n## Embedded Troubleshooting Matrix\n\n- **Rust build failure**: run the narrowest core build first, then expand to the\n  affected binding or workspace command.\n- **Python import failure**: rebuild the virtual environment and native\n  extension with `uv sync`, then run a small Python test or import check from\n  the same environment as the application.\n- **Node.js addon failure**: reinstall and rebuild the native addon from the\n  Node binding package before debugging application code.\n- **Go loader failure**: build the release FFI shared library and point both the\n  linker and runtime loader at the release output directory; use the macOS\n  dynamic-library path variable (`DYLD_LIBRARY_PATH`) on macOS.\n- **Scope stack empty**: the work is outside an active scope or crossed a thread,\n  task, goroutine, or worker boundary without the intended stack.\n- **Work leaks across requests**: separate requests are sharing one scope stack;\n  create a fresh stack per independent request or agent.\n- **Middleware missing or ordered incorrectly**: check global vs scope-local\n  registration, active scope ancestry, names, and priority values.\n- **Subscriber missing events**: register before the events are emitted; for\n  scope-local subscribers, ensure the current scope is the owner or descendant.\n- **Event fields missing**: managed helpers populate semantic fields; manual\n  lifecycle calls require explicit params for input, output, model names, and\n  tool call IDs.\n- **ATIF empty or mixed**: register before work starts, use one exporter per run\n  or clear between runs, and separate concurrent agents by root scope.\n- **Provider payload conversion failure**: convert non-JSON provider objects,\n  SDK handles, callbacks, streams, or class instances with explicit codecs.\n- **Plugin validation failure**: validate config independently from runtime\n  registration and check required fields, value types, defaults, and config\n  source.\n- **Adaptive behavior unchanged**: confirm instrumentation emits events, the\n  adaptive component is enabled, policy allows the behavior, and the call path\n  reaches the configured component.\n- **OpenTelemetry or OpenInference export failure**: first identify the Relay\n  version. For 0.6, check the separate exporter, `http_binary` versus `grpc`,\n  endpoint, headers, target support, and an active Tokio runtime for native\n  gRPC. For 0.7, check the typed projection, endpoint, headers, TLS, and target\n  support; the subscriber owns the native gRPC runtime.\n- **Callback succeeded but no lifecycle events appear**: confirm the integration\n  uses managed execute helpers or balanced manual start\u002Fend APIs, not only the\n  underlying business callback.\n\n## Related Skills\n\n- `nemo-relay-get-started`\n- `nemo-relay-instrument-context-isolation`\n- `nemo-relay-plugin-adaptive-tuning`\n- `nemo-relay-plugin-build`\n","# Debug Runtime Integration\n\nUse this skill when NeMo Relay is present in the application but something is not\nworking.\nStart by proving which runtime layer is failing before changing configuration.\n\n## First Checks\n\n- Can the binding or native artifact load?\n- Is there an active scope when the failing call runs?\n- Is the work happening on the expected scope stack?\n- Is the subscriber\u002Fexporter\u002Fplugin configuration actually active?\n- Did the app choose the right public API layer: managed execute vs manual\n  lifecycle vs typed wrappers vs adaptive\u002Fplugins?\n\n## Common Failure Classes\n\n- Python native extension missing\n- Go dynamic library not on the loader path\n- Node native addon not built or not loading\n- Execute call outside a scope\n- Missing events because registration never happened\n- Concurrency causing the wrong scope stack to be active\n- Adaptive component never initialized or config validation ignored\n\n## Embedded Troubleshooting Matrix\n\n- **Rust build failure**: run the narrowest core build first, then expand to the\n  affected binding or workspace command.\n- **Python import failure**: rebuild the virtual environment and native\n  extension with `uv sync`, then run a small Python test or import check from\n  the same environment as the application.\n- **Node.js addon failure**: reinstall and rebuild the native addon from the\n  Node binding package before debugging application code.\n- **Go loader failure**: build the release FFI shared library and point both the\n  linker and runtime loader at the release output directory; use the macOS\n  dynamic-library path variable (`DYLD_LIBRARY_PATH`) on macOS.\n- **Scope stack empty**: the work is outside an active scope or crossed a thread,\n  task, goroutine, or worker boundary without the intended stack.\n- **Work leaks across requests**: separate requests are sharing one scope stack;\n  create a fresh stack per independent request or agent.\n- **Middleware missing or ordered incorrectly**: check global vs scope-local\n  registration, active scope ancestry, names, and priority values.\n- **Subscriber missing events**: register before the events are emitted; for\n  scope-local subscribers, ensure the current scope is the owner or descendant.\n- **Event fields missing**: managed helpers populate semantic fields; manual\n  lifecycle calls require explicit params for input, output, model names, and\n  tool call IDs.\n- **ATIF empty or mixed**: register before work starts, use one exporter per run\n  or clear between runs, and separate concurrent agents by root scope.\n- **Provider payload conversion failure**: convert non-JSON provider objects,\n  SDK handles, callbacks, streams, or class instances with explicit codecs.\n- **Plugin validation failure**: validate config independently from runtime\n  registration and check required fields, value types, defaults, and config\n  source.\n- **Adaptive behavior unchanged**: confirm instrumentation emits events, the\n  adaptive component is enabled, policy allows the behavior, and the call path\n  reaches the configured component.\n- **OpenTelemetry or OpenInference export failure**: first identify the Relay\n  version. For 0.6, check the separate exporter, `http_binary` versus `grpc`,\n  endpoint, headers, target support, and an active Tokio runtime for native\n  gRPC. For 0.7, check the typed projection, endpoint, headers, TLS, and target\n  support; the subscriber owns the native gRPC runtime.\n- **Callback succeeded but no lifecycle events appear**: confirm the integration\n  uses managed execute helpers or balanced manual start\u002Fend APIs, not only the\n  underlying business callback.\n\n## Related Skills\n\n- `nemo-relay-get-started`\n- `nemo-relay-instrument-context-isolation`\n- `nemo-relay-plugin-adaptive-tuning`\n- `nemo-relay-plugin-build`\n",{"name":5,"license":14,"metadata":23,"description":7},{"author":24},"NVIDIA Corporation and Affiliates","main","13944d7d2b1a4bc9aa91fa061bed6fe63fad7979","skills\u002Fnemo-relay-debug-runtime-integration","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-debug-runtime-integration",{"tool":37,"command":38},"bunx","bunx skills add dawsonblock\u002FNEMO --skill nemo-relay-debug-runtime-integration",{"tool":40,"command":41},"pnpm","pnpm dlx skills add dawsonblock\u002FNEMO --skill nemo-relay-debug-runtime-integration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-debug-runtime-integration\u002FSKILL.md",true,[45,51,55,59],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"BENCHMARK.md","REFERENCE","参考文档",4811,"https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-debug-runtime-integration\u002FBENCHMARK.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"evals\u002Fevals.json",5085,"https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-debug-runtime-integration\u002Fevals\u002Fevals.json",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"skill-card.md",4110,"https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-debug-runtime-integration\u002Fskill-card.md",{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"skill.oms.sig","OTHER","其他",4613,"https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-debug-runtime-integration\u002Fskill.oms.sig",[66,73,80,87,94,101],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"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",[],[]]