[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A3CRCJB5MTF86JPCQHHPBS":3,"skill-same:01M7A3CRCJB5MTF86JPCQHHPBS":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7A3CRCJB5MTF86JPCQHHPBS","validate-change",null,"Choose and run the right NeMo Fabric validation matrix for a change instead of using one fixed test list","leemiracle\u002Fwork4ai","leemiracle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10385913?v=4","01M79YCHARF56CHMGGTECMZN8Z","lee","01M79YCHBY9VH2CJW4P65D3DHR",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002FNeMo-Fabric\u002Frepo-docs\u002F.agents\u002Fskills\u002Fvalidate-change\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: validate-change\ndescription: Choose and run the right NeMo Fabric validation matrix for a change instead of using one fixed test list\nauthor: NVIDIA Corporation and Affiliates\nlicense: Apache-2.0\n---\n\n\n# Validate a Change\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 to choose the smallest validation set that still covers the\nsurfaces touched by a change.\n\n## Mandatory Rules\n\n- Format changed files with the language-native formatter before the final\n  test pass.\n- If Rust code changed, run `cargo fmt --all -- --check` and `just test-rust`.\n- If Python code or a Python-facing adapter changed, run `just test-python`.\n- If the TypeScript adapter contract or one of its source schemas changed, run\n  `just test-typescript`.\n- If `crates\u002Ffabric-core` changed in a way exposed through Python, run both the\n  Rust and Python suites.\n- If the PyO3 bridge or package metadata changed, run `just build-python` and\n  `cargo check -p fabric-python --locked`.\n- If public configuration types changed, confirm the schema snapshot tests in\n  `just test-rust` pass and review generated schema diffs.\n- If an adapter or integration changed, run its focused tests.\n- If a Cargo or Python manifest or lockfile changed, run\n  `uv run --no-project python scripts\u002Flicensing\u002Flicense_diff.py --base-ref origin\u002Fmain`,\n  review the transitive license changes, then run the `attributions-rust` and\n  `attributions-python` pre-commit hooks.\n- If the TypeScript manifest or npm lockfile changed, inspect the complete npm\n  dependency tree and license fields, confirm the package still has zero\n  production dependencies, run the `attributions-node` pre-commit hook, and run\n  its package and audit checks.\n- If documentation or examples changed, run `just docs` when practical and\n  verify documented commands against the current repository.\n- If code changes alter APIs, commands, paths, packaging behavior, telemetry\n  semantics, or documented best practices, update dependent maintainer skills in\n  the same branch. Because the consumer skills under `skills\u002F` restate SDK guide,\n  Pydantic model, and Rust type details, update them in parity whenever those\n  surfaces change.\n\n## Start With the Change Shape\n\n- **Rust core, CLI, or shared runtime semantics changed**\n  Run Rust formatting and tests. Add Python tests when the behavior is exposed through the SDK, and run relevant tests for CLI behavior.\n- **Python SDK or PyO3 binding changed**\n  Use `python-tests`, run focused pytest tests first, then run\n  `just test-python`. Rebuild with `just build-python` when native code or\n  packaging changed.\n- **Adapter behavior changed**\n  Run the focused adapter tests under `tests\u002Fadapters`, then `just test-python`.\n- **Harbor integration changed**\n  Run `tests\u002Fintegrations\u002Ftest_harbor_runner.py` and\n  `tests\u002Fpython\u002Ftest_adapter_capabilities.py`, then `just test-python`.\n  For host admission changes, verify metadata inspection without harness SDKs\n  or task discovery, selected telemetry claims, and task-side descriptor drift\n  rejection before startup.\n- **Schema or public contract changed**\n  Run the Rust, Python, and TypeScript suites and review changes under\n  `schemas\u002F`, the checked-in Python adapter-contract representations, generated\n  TypeScript sources, and generated API references.\n- **Documentation-only change**\n  Use `contribute-docs` and `review-doc-style`. Run `just docs` for docs-site or\n  generated-reference changes.\n- **CI or packaging changed**\n  Use `maintain-ci` or `maintain-packaging`, then run the recipes and checks\n  whose behavior changed.\n\n## Core Validation Matrix\n\n```bash\njust test-rust\njust test-python\njust test-typescript\n```\n\n## Common Targeted Commands\n\n```bash\n# Rust\njust build-rust\njust test-rust\ncargo fmt --all -- --check\ncargo check -p fabric-python --locked\n\n# Python and native extension\njust build-python\njust test-python\nuv run --no-sync pytest -k \"\u003Cpattern>\"\n\n# TypeScript adapter contract\njust build-typescript\njust test-typescript\njust pack-typescript\n\n# Documentation\njust docs\n\n# Dependency licenses\nuv run --no-project python scripts\u002Flicensing\u002Flicense_diff.py --base-ref origin\u002Fmain\nuv run pre-commit run --all-files attributions-rust\nuv run pre-commit run --all-files attributions-python\nuv run pre-commit run --all-files attributions-node\n\n# Justfile and patch hygiene\njust --fmt --check\ngit diff --check\n```\n\n## Hygiene Checks\n\nBefore review or handoff:\n\n- Verify README and docs entry points still match current package names and\n  paths.\n- Verify examples use current `just` recipes and public commands.\n- Call out checks that were not run and why.\n- Run `git diff --check`.\n\n## References\n\n- Python test guidance: `python-tests`\n- Build and test recipes: `justfile`\n- Python CI: `.github\u002Fworkflows\u002Fci_python.yml`\n- Rust CI: `.github\u002Fworkflows\u002Fci_rust.yml`\n- TypeScript CI: `.github\u002Fworkflows\u002Fci_typescript.yml`\n- Documentation CI: `.github\u002Fworkflows\u002Ffern-docs.yml`\n- Public Python contract: `docs\u002Fpython-sdk-contract.md`\n- Public adapter contract: `schemas\u002FSCHEMA.md`\n","# Validate a Change\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 to choose the smallest validation set that still covers the\nsurfaces touched by a change.\n\n## Mandatory Rules\n\n- Format changed files with the language-native formatter before the final\n  test pass.\n- If Rust code changed, run `cargo fmt --all -- --check` and `just test-rust`.\n- If Python code or a Python-facing adapter changed, run `just test-python`.\n- If the TypeScript adapter contract or one of its source schemas changed, run\n  `just test-typescript`.\n- If `crates\u002Ffabric-core` changed in a way exposed through Python, run both the\n  Rust and Python suites.\n- If the PyO3 bridge or package metadata changed, run `just build-python` and\n  `cargo check -p fabric-python --locked`.\n- If public configuration types changed, confirm the schema snapshot tests in\n  `just test-rust` pass and review generated schema diffs.\n- If an adapter or integration changed, run its focused tests.\n- If a Cargo or Python manifest or lockfile changed, run\n  `uv run --no-project python scripts\u002Flicensing\u002Flicense_diff.py --base-ref origin\u002Fmain`,\n  review the transitive license changes, then run the `attributions-rust` and\n  `attributions-python` pre-commit hooks.\n- If the TypeScript manifest or npm lockfile changed, inspect the complete npm\n  dependency tree and license fields, confirm the package still has zero\n  production dependencies, run the `attributions-node` pre-commit hook, and run\n  its package and audit checks.\n- If documentation or examples changed, run `just docs` when practical and\n  verify documented commands against the current repository.\n- If code changes alter APIs, commands, paths, packaging behavior, telemetry\n  semantics, or documented best practices, update dependent maintainer skills in\n  the same branch. Because the consumer skills under `skills\u002F` restate SDK guide,\n  Pydantic model, and Rust type details, update them in parity whenever those\n  surfaces change.\n\n## Start With the Change Shape\n\n- **Rust core, CLI, or shared runtime semantics changed**\n  Run Rust formatting and tests. Add Python tests when the behavior is exposed through the SDK, and run relevant tests for CLI behavior.\n- **Python SDK or PyO3 binding changed**\n  Use `python-tests`, run focused pytest tests first, then run\n  `just test-python`. Rebuild with `just build-python` when native code or\n  packaging changed.\n- **Adapter behavior changed**\n  Run the focused adapter tests under `tests\u002Fadapters`, then `just test-python`.\n- **Harbor integration changed**\n  Run `tests\u002Fintegrations\u002Ftest_harbor_runner.py` and\n  `tests\u002Fpython\u002Ftest_adapter_capabilities.py`, then `just test-python`.\n  For host admission changes, verify metadata inspection without harness SDKs\n  or task discovery, selected telemetry claims, and task-side descriptor drift\n  rejection before startup.\n- **Schema or public contract changed**\n  Run the Rust, Python, and TypeScript suites and review changes under\n  `schemas\u002F`, the checked-in Python adapter-contract representations, generated\n  TypeScript sources, and generated API references.\n- **Documentation-only change**\n  Use `contribute-docs` and `review-doc-style`. Run `just docs` for docs-site or\n  generated-reference changes.\n- **CI or packaging changed**\n  Use `maintain-ci` or `maintain-packaging`, then run the recipes and checks\n  whose behavior changed.\n\n## Core Validation Matrix\n\n```bash\njust test-rust\njust test-python\njust test-typescript\n```\n\n## Common Targeted Commands\n\n```bash\n# Rust\njust build-rust\njust test-rust\ncargo fmt --all -- --check\ncargo check -p fabric-python --locked\n\n# Python and native extension\njust build-python\njust test-python\nuv run --no-sync pytest -k \"\u003Cpattern>\"\n\n# TypeScript adapter contract\njust build-typescript\njust test-typescript\njust pack-typescript\n\n# Documentation\njust docs\n\n# Dependency licenses\nuv run --no-project python scripts\u002Flicensing\u002Flicense_diff.py --base-ref origin\u002Fmain\nuv run pre-commit run --all-files attributions-rust\nuv run pre-commit run --all-files attributions-python\nuv run pre-commit run --all-files attributions-node\n\n# Justfile and patch hygiene\njust --fmt --check\ngit diff --check\n```\n\n## Hygiene Checks\n\nBefore review or handoff:\n\n- Verify README and docs entry points still match current package names and\n  paths.\n- Verify examples use current `just` recipes and public commands.\n- Call out checks that were not run and why.\n- Run `git diff --check`.\n\n## References\n\n- Python test guidance: `python-tests`\n- Build and test recipes: `justfile`\n- Python CI: `.github\u002Fworkflows\u002Fci_python.yml`\n- Rust CI: `.github\u002Fworkflows\u002Fci_rust.yml`\n- TypeScript CI: `.github\u002Fworkflows\u002Fci_typescript.yml`\n- Documentation CI: `.github\u002Fworkflows\u002Ffern-docs.yml`\n- Public Python contract: `docs\u002Fpython-sdk-contract.md`\n- Public adapter contract: `schemas\u002FSCHEMA.md`\n",{"name":5,"author":24,"license":15,"description":7},"NVIDIA Corporation and Affiliates","main","ffa016d3c9a8d32821f71f6d9d916c30e04fcb67","讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002FNeMo-Fabric\u002Frepo-docs\u002F.agents\u002Fskills\u002Fvalidate-change",0,"https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai","https:\u002F\u002Fgithub.com\u002Fleemiracle","i have some experience that make me better, so i want more. follow and star me would be a good choice.","2026-11-12 17:16:40",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add leemiracle\u002Fwork4ai --skill validate-change",{"tool":39,"command":40},"bunx","bunx skills add leemiracle\u002Fwork4ai --skill validate-change",{"tool":42,"command":43},"pnpm","pnpm dlx skills add leemiracle\u002Fwork4ai --skill validate-change","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002FNeMo-Fabric\u002Frepo-docs\u002F.agents\u002Fskills\u002Fvalidate-change\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7A57J4E78QJZS8MA72P82DV","agentic-ecology-ui","Guidelines and templates for creating a generic web UI to visualize, rank, filter, and annotate vector databases. The UI has a hierarchical structure covering database selection, label selection\u002Fdefinition, ranking\u002Ffiltering configuration, and row visualization\u002Fannotation. Use when building, serving, or adapting an interactive web UI for Hoplite vector databases.","https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透google-deepmind\u002Fagentic_ecology\u002Frepo-docs\u002Fskills\u002Fagentic-ecology-ui\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7A57C4RGS1A7VM6CNPNQDBH","agentic-ecology-init","Initializes a local uv-managed project directory for agentic ecology workloads. Sets up Python dependencies using reference pyproject.toml and uv.lock, configures workspace rules, and ensures Agentic Ecology skills are discoverable. Use when initializing a new project workspace or bootstrapping a clean environment.","https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透google-deepmind\u002Fagentic_ecology\u002Frepo-docs\u002Fskills\u002Fagentic-ecology-init\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7A576Q1GYF5GAQCWGPPDQWZ","agentic-ecology-camera-traps","Provides capabilities to run SpeciesNet detector and classifier on camera trap images, extract crop-level feature embeddings, and populate a Hoplite vector database for downstream search and agile modeling. Use when ingesting camera trap images, classifying wildlife photos, or indexing camera trap data.","https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透google-deepmind\u002Fagentic_ecology\u002Frepo-docs\u002Fskills\u002Fagentic-ecology-camera-traps\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7A5708M54MMTKXQARDCJQMW","agentic-ecology-bioacoustics","Provides bioacoustic analysis capabilities for ecologists and researchers using the perch-hoplite Python package. A typical use case is to use agile modeling to bootstrap the creation and deployment of a bespoke detector for targeted species on an existing collection of passive acoustic monitoring recordings. Use when processing and annotating audio recordings for bioacoustic applications.","https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透google-deepmind\u002Fagentic_ecology\u002Frepo-docs\u002Fskills\u002Fagentic-ecology-bioacoustics\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7A53GYCZY3AT9C2FR44TC35","sample-skill","Sample skill used by agent-env integration tests. Exercises SKILL.md parsing plus supporting scripts and references.","https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透browser-use\u002Fagentenv-framework\u002Frepo-docs\u002Ftst\u002Fdata\u002Fskills\u002Fsample_skill\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7A4KD50DHSNH1SCNKP1J6S1","simready-foundation-validate-foundation-change","Use for auditing SimReady requirement, validator, feature, profile, adapter, test, and skill consistency.","https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002Fsimready-foundation\u002Frepo-docs\u002F.codex\u002Fskills\u002Fsimready-foundation-validate-foundation-change\u002FSKILL.md",[],[]]