[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BGYRQ1PTFVVC8KGA8ZE4MN":3,"skill-same:01M7BGYRQ1PTFVVC8KGA8ZE4MN":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},"01M7BGYRQ1PTFVVC8KGA8ZE4MN","nemo-relay-instrument-typed-wrappers",null,"Use this skill when adding NeMo Relay typed wrappers, domain types, or provider codecs while preserving JSON middleware semantics and caller-visible behavior.","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-instrument-typed-wrappers\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: nemo-relay-instrument-typed-wrappers\ndescription: Use this skill when adding NeMo Relay typed wrappers, domain types, or provider codecs while preserving JSON middleware semantics and caller-visible behavior.\nlicense: Apache-2.0\nmetadata:\n  author: NVIDIA Corporation and Affiliates\n---\n\n# Use Typed Wrappers And Codecs\n\nUse this skill when an application wants stronger domain types than raw JSON for\ntool or LLM integration.\nKeep typed boundaries explicit so middleware still sees predictable JSON.\n\n## Default Guidance\n\n- Prefer plain JSON first for initial adoption.\n- Reach for typed wrappers when the application already has stable domain models.\n- Keep in mind that middleware still operates on JSON, not typed objects.\n\n## Embedded Codec Model\n\n- A typed value codec is a pure boundary translator. It converts\n  application-facing values to JSON before NeMo Relay emits events or runs\n  middleware, then converts JSON back into the framework callback or caller type.\n- Python exposes `JsonPassthrough`, `DataclassCodec`, `PydanticCodec`, and\n  `BestEffortAnyCodec`. Node.js exposes `JsonPassthrough` plus custom\n  `Codec\u003CT>` implementations.\n- Use `BestEffortAnyCodec` only at boundaries where strict schemas are not\n  available. Prefer dataclass, Pydantic, or explicit Node.js codecs when the\n  framework owns a stable schema.\n- Provider codecs are different from typed value codecs: they normalize\n  provider-specific LLM requests and responses so middleware and subscribers can\n  inspect messages, tools, model names, generation parameters, and response\n  annotations.\n- Built-in provider codecs include `OpenAIChatCodec`, `OpenAIResponsesCodec`,\n  and `AnthropicMessagesCodec` in Python, Node.js, and Rust. Choose the\n  codec that matches the actual provider payload shape.\n- Response codecs annotate LLM end events with fields such as `id`, `model`,\n  `message`, `tool_calls`, `finish_reason`, `usage`, provider-specific data, and\n  extra unmodeled fields. They do not rewrite the caller-visible response.\n- Request codecs run before LLM request intercepts. Intercepts receive both the\n  raw `LLMRequest` and optional annotated request; `encode` merges annotated\n  edits back before execution intercepts and the provider callback run.\n- Built-in request codecs guarantee JSON-value identity for an unchanged\n  annotation. They compare edits with a decoded baseline and patch only changed\n  fields, preserving native representation details and unknown fields.\n- Use `instructions`, portable messages and components, and the tagged\n  `api_specific` request surface for normalized edits. Provider-only union\n  members use explicit `{ provider, kind, value }` native components. Reserve\n  top-level `extra` for unknown future fields.\n- The `nemo-relay` gateway always supplies matching request codecs on Anthropic\n  Messages, OpenAI Chat Completions, and OpenAI Responses generation routes.\n  On those routes, treat raw `request.content` as read-only and return body\n  edits through the annotated request. Header edits still use the raw request.\n\n## Key Rules\n\n- Typed wrappers are currently a first-class path for Python and Node.js; Rust\n  uses codec traits directly\n- Request\u002Fresponse conversion belongs in codecs\n- Intercepts and guardrails see JSON values after encoding\n- Changes made by middleware survive into the decode step\n\n## Choose A Codec\n\n- `JsonPassthrough` for JSON-native values\n- `DataclassCodec` or `PydanticCodec` in Python when the models already exist\n- Custom codecs for domain-specific wire shapes\n- `BestEffortAnyCodec` only when broad flexibility is worth the looser contract\n- Provider codecs for LLM provider payloads, not application domain objects\n  conversion\n\n## Validation Checklist\n\n- [ ] Codec output is JSON-compatible\n- [ ] Required fields survive `toJson`\u002F`fromJson` or `decode`\u002F`encode`\n- [ ] Middleware sees the expected serialized shape\n- [ ] Provider codecs preserve fields they do not understand\n- [ ] Response codec failures do not break the underlying LLM call\n- [ ] Request codec `encode` preserves original provider fields unless an\n  intercept intentionally changes them\n- [ ] Provider-native components belong to the codec's provider surface\n- [ ] Gateway generation intercepts do not mutate raw `request.content`\n\n## Related Skills\n\n- `nemo-relay-instrument-calls`\n- `nemo-relay-plugin-observability`\n- `nemo-relay-debug-runtime-integration`\n","# Use Typed Wrappers And Codecs\n\nUse this skill when an application wants stronger domain types than raw JSON for\ntool or LLM integration.\nKeep typed boundaries explicit so middleware still sees predictable JSON.\n\n## Default Guidance\n\n- Prefer plain JSON first for initial adoption.\n- Reach for typed wrappers when the application already has stable domain models.\n- Keep in mind that middleware still operates on JSON, not typed objects.\n\n## Embedded Codec Model\n\n- A typed value codec is a pure boundary translator. It converts\n  application-facing values to JSON before NeMo Relay emits events or runs\n  middleware, then converts JSON back into the framework callback or caller type.\n- Python exposes `JsonPassthrough`, `DataclassCodec`, `PydanticCodec`, and\n  `BestEffortAnyCodec`. Node.js exposes `JsonPassthrough` plus custom\n  `Codec\u003CT>` implementations.\n- Use `BestEffortAnyCodec` only at boundaries where strict schemas are not\n  available. Prefer dataclass, Pydantic, or explicit Node.js codecs when the\n  framework owns a stable schema.\n- Provider codecs are different from typed value codecs: they normalize\n  provider-specific LLM requests and responses so middleware and subscribers can\n  inspect messages, tools, model names, generation parameters, and response\n  annotations.\n- Built-in provider codecs include `OpenAIChatCodec`, `OpenAIResponsesCodec`,\n  and `AnthropicMessagesCodec` in Python, Node.js, and Rust. Choose the\n  codec that matches the actual provider payload shape.\n- Response codecs annotate LLM end events with fields such as `id`, `model`,\n  `message`, `tool_calls`, `finish_reason`, `usage`, provider-specific data, and\n  extra unmodeled fields. They do not rewrite the caller-visible response.\n- Request codecs run before LLM request intercepts. Intercepts receive both the\n  raw `LLMRequest` and optional annotated request; `encode` merges annotated\n  edits back before execution intercepts and the provider callback run.\n- Built-in request codecs guarantee JSON-value identity for an unchanged\n  annotation. They compare edits with a decoded baseline and patch only changed\n  fields, preserving native representation details and unknown fields.\n- Use `instructions`, portable messages and components, and the tagged\n  `api_specific` request surface for normalized edits. Provider-only union\n  members use explicit `{ provider, kind, value }` native components. Reserve\n  top-level `extra` for unknown future fields.\n- The `nemo-relay` gateway always supplies matching request codecs on Anthropic\n  Messages, OpenAI Chat Completions, and OpenAI Responses generation routes.\n  On those routes, treat raw `request.content` as read-only and return body\n  edits through the annotated request. Header edits still use the raw request.\n\n## Key Rules\n\n- Typed wrappers are currently a first-class path for Python and Node.js; Rust\n  uses codec traits directly\n- Request\u002Fresponse conversion belongs in codecs\n- Intercepts and guardrails see JSON values after encoding\n- Changes made by middleware survive into the decode step\n\n## Choose A Codec\n\n- `JsonPassthrough` for JSON-native values\n- `DataclassCodec` or `PydanticCodec` in Python when the models already exist\n- Custom codecs for domain-specific wire shapes\n- `BestEffortAnyCodec` only when broad flexibility is worth the looser contract\n- Provider codecs for LLM provider payloads, not application domain objects\n  conversion\n\n## Validation Checklist\n\n- [ ] Codec output is JSON-compatible\n- [ ] Required fields survive `toJson`\u002F`fromJson` or `decode`\u002F`encode`\n- [ ] Middleware sees the expected serialized shape\n- [ ] Provider codecs preserve fields they do not understand\n- [ ] Response codec failures do not break the underlying LLM call\n- [ ] Request codec `encode` preserves original provider fields unless an\n  intercept intentionally changes them\n- [ ] Provider-native components belong to the codec's provider surface\n- [ ] Gateway generation intercepts do not mutate raw `request.content`\n\n## Related Skills\n\n- `nemo-relay-instrument-calls`\n- `nemo-relay-plugin-observability`\n- `nemo-relay-debug-runtime-integration`\n",{"name":5,"license":14,"metadata":23,"description":7},{"author":24},"NVIDIA Corporation and Affiliates","main","13944d7d2b1a4bc9aa91fa061bed6fe63fad7979","skills\u002Fnemo-relay-instrument-typed-wrappers","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-instrument-typed-wrappers",{"tool":37,"command":38},"bunx","bunx skills add dawsonblock\u002FNEMO --skill nemo-relay-instrument-typed-wrappers",{"tool":40,"command":41},"pnpm","pnpm dlx skills add dawsonblock\u002FNEMO --skill nemo-relay-instrument-typed-wrappers","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-instrument-typed-wrappers\u002FSKILL.md",true,[45,51,55,59],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"BENCHMARK.md","REFERENCE","参考文档",3909,"https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-instrument-typed-wrappers\u002FBENCHMARK.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"evals\u002Fevals.json",5158,"https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-instrument-typed-wrappers\u002Fevals\u002Fevals.json",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"skill-card.md",3967,"https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-instrument-typed-wrappers\u002Fskill-card.md",{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"skill.oms.sig","OTHER","其他",4617,"https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-instrument-typed-wrappers\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},"01M7BGYMR22V7RZZA8VFJ4852B","nemo-relay-instrument-context-isolation","Use this skill when concurrent requests, async tasks, threads, workers, goroutines, or agents need independent NeMo Relay scope stacks and correct ancestry propagation.","https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002Fskills\u002Fnemo-relay-instrument-context-isolation\u002FSKILL.md",[],[]]