[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BGXKNJD8FX8FCSWG7X7PZ8":3,"skill-same:01M7BGXKNJD8FX8FCSWG7X7PZ8":44},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7BGXKNJD8FX8FCSWG7X7PZ8","test-python-binding",null,"Build and test the NeMo Relay Python binding and worker plugin SDK; use for python\u002Fnemo_relay, python\u002Fplugin, or crates\u002Fpython changes","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\u002F.agents\u002Fskills\u002Ftest-python-binding\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: test-python-binding\ndescription: Build and test the NeMo Relay Python binding and worker plugin SDK; use for python\u002Fnemo_relay, python\u002Fplugin, or crates\u002Fpython changes\nauthor: NVIDIA Corporation and Affiliates\nlicense: Apache-2.0\n---\n\n\n# Build And Test Python Binding\n\n## Companion Guidance\n\nUse `karpathy-guidelines` alongside this skill for implementation or review\nwork. Keep changes scoped, surface assumptions, and define focused validation\nbefore editing.\n\nUse this skill when the change is primarily in `python\u002Fnemo_relay`,\n`python\u002Fplugin`, `python\u002Ftests`, `crates\u002Fpython`, or Python-facing\ndocs\u002Fexamples.\n\n## Default Path\n\n1. Format changed Python wrapper and test files with `uv run ruff format python python\u002Fplugin`.\n2. Run focused `pytest` first when you know the affected area.\n3. Run `just test-python-plugin` when the Python worker SDK changed.\n4. Run the full Python suite with `just test-python` before review.\n5. If any Rust files changed as part of the Python work, also run\n   `cargo fmt --all`, `just test-rust`, and\n   `cargo clippy --workspace --all-targets -- -D warnings`.\n6. Use `just build-python` when you want an explicit build-only pass.\n7. Use `just build-python-plugin` when the Python worker SDK changed.\n8. If the native Rust bridge changed, add the Rust crate tests for\n   `nemo-relay-python`.\n\n## Python Test Style\n\n- Pytest is used to run tests.\n- Do not add `@pytest.mark.asyncio` to any test. Async tests are automatically detected and run by the async runner; the decorator is unnecessary clutter.\n- Do not add a `-> None` return type annotation to test functions. This is not a common convention in pytest and adds unnecessary verbosity.\n- When mocking a class, do not define a new class. Use `unittest.mock.MagicMock` or `unittest.mock.AsyncMock`, with the `spec` constructor argument when necessary.\n- The name of the mocked class should be prefixed with `mock`, not `fake`.\n- Prefer pytest fixtures over helper methods.\n- Do not repeat fixtures, if a fixture is needed in multiple test files, place it in a `conftest.py` file.\n- When creating a fixture follow this pattern:\n  ```python\n  @pytest.fixture(name=\"\u003Cfixture_name>\"[, scope=\"\u003Cscope>\"])\n  def \u003Cfixture_name>_fixture() -> \u003Creturn_type>:\n      ...\n  ```\n  Only specify the scope argument when the value is something other than \"function\".\n- Prefer `pytest.mark.parametrize` over creating individual tests for\n  different input types.\n\n## Common Commands\n\n```bash\n# Focused test loop\nuv run pytest -k \"\u003Cpattern>\"\n\n# Required first for focused dynamic-plugin host tests\njust build-test-plugin-fixtures\nuv run pytest python\u002Ftests\u002Ftest_dynamic_plugin_host.py\n\n# Focused Python worker plugin SDK suite\njust test-python-plugin\n\n# Format Python files\nuv run ruff format python python\u002Fplugin\n\n# Full Python suite\njust test-python\n\n# Required when the Python change also touched Rust code\ncargo fmt --all\njust test-rust\ncargo clippy --workspace --all-targets -- -D warnings\n\n# Rebuild the editable package plus native extension\njust build-python\n\n# Rebuild\u002Finstall the Python worker plugin SDK\njust build-python-plugin\n\n# Native extension crate when crates\u002Fpython changed\ncargo test -p nemo-relay-python\n```\n\n## When To Escalate\n\n- If `crates\u002Fcore`, `crates\u002Fadaptive`, or shared runtime semantics changed,\n  also use `validate-change`.\n- If `python\u002Fplugin` or worker protocol behavior changed, also use\n  `maintain-dynamic-plugins`.\n- If the change is actually about docs only, prefer `contribute-docs`\n  plus targeted command checks.\n\n## References\n\n- `pyproject.toml`\n- `crates\u002Fpython\u002FCargo.toml`\n- `crates\u002Fpython\u002FREADME.md`\n- `python\u002Fnemo_relay\u002FREADME.md`\n- `python\u002Fplugin\u002Fpyproject.toml`\n- `python\u002Fplugin\u002Fsrc\u002Fnemo_relay_plugin`\n- `python\u002Ftests\u002Fplugin`\n- `docs\u002Fgetting-started\u002Fquick-start\u002Fpython.mdx`\n- `docs\u002Fcontribute\u002Ftesting-and-docs.mdx`\n- `validate-change`\n","# Build And Test Python Binding\n\n## Companion Guidance\n\nUse `karpathy-guidelines` alongside this skill for implementation or review\nwork. Keep changes scoped, surface assumptions, and define focused validation\nbefore editing.\n\nUse this skill when the change is primarily in `python\u002Fnemo_relay`,\n`python\u002Fplugin`, `python\u002Ftests`, `crates\u002Fpython`, or Python-facing\ndocs\u002Fexamples.\n\n## Default Path\n\n1. Format changed Python wrapper and test files with `uv run ruff format python python\u002Fplugin`.\n2. Run focused `pytest` first when you know the affected area.\n3. Run `just test-python-plugin` when the Python worker SDK changed.\n4. Run the full Python suite with `just test-python` before review.\n5. If any Rust files changed as part of the Python work, also run\n   `cargo fmt --all`, `just test-rust`, and\n   `cargo clippy --workspace --all-targets -- -D warnings`.\n6. Use `just build-python` when you want an explicit build-only pass.\n7. Use `just build-python-plugin` when the Python worker SDK changed.\n8. If the native Rust bridge changed, add the Rust crate tests for\n   `nemo-relay-python`.\n\n## Python Test Style\n\n- Pytest is used to run tests.\n- Do not add `@pytest.mark.asyncio` to any test. Async tests are automatically detected and run by the async runner; the decorator is unnecessary clutter.\n- Do not add a `-> None` return type annotation to test functions. This is not a common convention in pytest and adds unnecessary verbosity.\n- When mocking a class, do not define a new class. Use `unittest.mock.MagicMock` or `unittest.mock.AsyncMock`, with the `spec` constructor argument when necessary.\n- The name of the mocked class should be prefixed with `mock`, not `fake`.\n- Prefer pytest fixtures over helper methods.\n- Do not repeat fixtures, if a fixture is needed in multiple test files, place it in a `conftest.py` file.\n- When creating a fixture follow this pattern:\n  ```python\n  @pytest.fixture(name=\"\u003Cfixture_name>\"[, scope=\"\u003Cscope>\"])\n  def \u003Cfixture_name>_fixture() -> \u003Creturn_type>:\n      ...\n  ```\n  Only specify the scope argument when the value is something other than \"function\".\n- Prefer `pytest.mark.parametrize` over creating individual tests for\n  different input types.\n\n## Common Commands\n\n```bash\n# Focused test loop\nuv run pytest -k \"\u003Cpattern>\"\n\n# Required first for focused dynamic-plugin host tests\njust build-test-plugin-fixtures\nuv run pytest python\u002Ftests\u002Ftest_dynamic_plugin_host.py\n\n# Focused Python worker plugin SDK suite\njust test-python-plugin\n\n# Format Python files\nuv run ruff format python python\u002Fplugin\n\n# Full Python suite\njust test-python\n\n# Required when the Python change also touched Rust code\ncargo fmt --all\njust test-rust\ncargo clippy --workspace --all-targets -- -D warnings\n\n# Rebuild the editable package plus native extension\njust build-python\n\n# Rebuild\u002Finstall the Python worker plugin SDK\njust build-python-plugin\n\n# Native extension crate when crates\u002Fpython changed\ncargo test -p nemo-relay-python\n```\n\n## When To Escalate\n\n- If `crates\u002Fcore`, `crates\u002Fadaptive`, or shared runtime semantics changed,\n  also use `validate-change`.\n- If `python\u002Fplugin` or worker protocol behavior changed, also use\n  `maintain-dynamic-plugins`.\n- If the change is actually about docs only, prefer `contribute-docs`\n  plus targeted command checks.\n\n## References\n\n- `pyproject.toml`\n- `crates\u002Fpython\u002FCargo.toml`\n- `crates\u002Fpython\u002FREADME.md`\n- `python\u002Fnemo_relay\u002FREADME.md`\n- `python\u002Fplugin\u002Fpyproject.toml`\n- `python\u002Fplugin\u002Fsrc\u002Fnemo_relay_plugin`\n- `python\u002Ftests\u002Fplugin`\n- `docs\u002Fgetting-started\u002Fquick-start\u002Fpython.mdx`\n- `docs\u002Fcontribute\u002Ftesting-and-docs.mdx`\n- `validate-change`\n",{"name":5,"author":23,"license":14,"description":7},"NVIDIA Corporation and Affiliates","main","13944d7d2b1a4bc9aa91fa061bed6fe63fad7979",".agents\u002Fskills\u002Ftest-python-binding","https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO","https:\u002F\u002Fgithub.com\u002Fdawsonblock","2026-09-30 06:03:35",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add dawsonblock\u002FNEMO --skill test-python-binding",{"tool":36,"command":37},"bunx","bunx skills add dawsonblock\u002FNEMO --skill test-python-binding",{"tool":39,"command":40},"pnpm","pnpm dlx skills add dawsonblock\u002FNEMO --skill test-python-binding","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdawsonblock\u002FNEMO\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftest-python-binding\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"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":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"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":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"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":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},"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":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},"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":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},"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",[],[]]