[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A4C819MXMCS96VRFX32XE8":3,"skill-same:01M7A4C819MXMCS96VRFX32XE8":52},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M7A4C819MXMCS96VRFX32XE8","simready-foundation-add-feature-adapter",null,"Use for adding SimReady feature adapters that mutate USD assets between exact feature or profile versions.","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\u002Fsimready-foundation\u002Frepo-docs\u002F.codex\u002Fskills\u002Fsimready-foundation-add-feature-adapter\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: simready-foundation-add-feature-adapter\ndescription: \"Use for adding SimReady feature adapters that mutate USD assets between exact feature or profile versions.\"\nlicense: Apache-2.0\nmetadata:\n  author: \"Shaad Boochoon \u003Csboochoon@nvidia.com>\"\n  tags:\n    - simready\n    - adapter\n    - usd\n---\n\n\n# SimReady Add Feature Adapter\n\n## Purpose\nUse this skill to add a direct asset mutation path between exact `FET_###_\u003CRUNTIME>` feature names with integer feature versions, or between profile feature bundles. Feature adapters live under `nv_core\u002Fcip_specs\u002Fasset_handler_modules\u002F` and modify an output USD stage so an asset can move from an input feature\u002Fprofile contract to a target one.\n\nUse this after feature\u002Fprofile differences are known. If no USD mutation is needed, document that no adapter is required.\n\n## Prerequisites\nBefore editing, read:\n\n- `AGENTS.md`\n- `nv_core\u002Fsr_specs\u002Fdocs\u002Fguides\u002Ffeature_adapters\u002Ffeature_adapters.md`\n- source and target feature manifests\n- source and target profile versions, if this is profile-driven\n- existing adapters in the relevant asset handler module\n\n## Inputs\n\nCollect or infer:\n\n| Input | Requirement |\n|---|---|\n| `input_feature_name` | Source feature name \u002F manifest `id`, such as `FET_003_STANDARD`. |\n| `input_feature_version` | Source integer feature version. |\n| `output_feature_name` | Target feature name \u002F manifest `id`, such as `FET_003_PHYSX`. |\n| `output_feature_version` | Target integer feature version. |\n| `profile_path` | Optional source\u002Ftarget profile upgrade path. |\n| `mutation` | Exact USD data changes required. |\n| `module_path` | Asset handler module directory. |\n| `test_assets` | Assets that pass input and should pass output after mutation. |\n\n## Instructions\n\nUse this checklist when changing the repository:\n\n1. Compare source and target manifests. Confirm names use `FET_###_\u003CRUNTIME>` and versions are exact integers, then identify only the requirements that differ.\n2. Decide whether a direct adapter is necessary. For profile transformations, every feature difference must have a direct adapter path or a documented blocker. If target requirements are documentation-only or already satisfied by source assets, document no-op behavior.\n3. Choose or create the asset handler module path.\n4. Add a Python adapter file with `@feature_adapter` metadata using exact feature names and integer versions.\n5. Implement `modify_stage(input_stage, output_stage)`:\n   - read source stage only when needed\n   - mutate output stage deterministically\n   - preserve unrelated authored data\n   - save output stage when complete\n6. Use native USD schemas and existing helper patterns from neighboring adapters.\n7. Add focused tests or manual validation notes:\n   - input validates against source feature\u002Fprofile\n   - output validates against target feature\u002Fprofile\n   - mutation is idempotent or safely repeatable where practical\n8. Update adapter indexes, imports, or registration files if the repo requires them.\n9. If the adapter is needed for a new profile version, update the profile docs or migration notes.\n\n## Examples\n\nExample request:\n\n```text\nAdd a feature adapter that mutates assets from one exact SimReady feature\u002Fprofile version to another.\n```\n\nExpected result summary:\n\n```text\nchanged_files: new docs, manifests, indexes, or validation scaffolding\nvalidation: focused static checks and any relevant docs\u002Fbuild checks\nremaining_gaps: requirement, validator, adapter, profile, or runtime-test follow-up\n```\n\n## Policies\n\n- Do not use adapters to hide invalid source assets; adapters should bridge defined feature differences.\n- Do not mutate source stages in place.\n- Do not invent property values that need user intent or prediction unless the adapter contract explicitly defines defaults.\n- Keep profile upgrade paths direct: every changed feature needs a clear adapter path or a documented blocker.\n\n## Limitations\n\n- Do not mutate published feature or profile versions in place.\n- Do not invent requirement IDs or validator behavior when the contract is ambiguous; record the question.\n- Do not skip index, manifest, validation, or downstream follow-up notes.\n\n## Troubleshooting\n\n- Error: the new concept overlaps an existing artifact. Solution: update the existing capability, requirement, feature, profile, or adapter instead.\n- Error: names or IDs conflict. Solution: re-check naming conventions and nearby indexes before editing further.\n- Error: validation strategy is unclear. Solution: document deferred validation and the exact follow-up skill.\n\n## Resources\n\n- `assets\u002Fopenai.yaml` preserves optional UI metadata for clients that read skill display hints. It is not required for the workflow.\n\n## Summary Format\n\nReport:\n\n| Field | Meaning |\n|---|---|\n| `adapter_name` | Adapter identifier. |\n| `adapter_path` | Python file path. |\n| `input_feature` | Source feature name and integer version. |\n| `output_feature` | Target feature name and integer version. |\n| `mutation_summary` | USD opinions changed. |\n| `profile_upgrade` | Profile path supported, if any. |\n| `validation` | Tests\u002Fassets run and remaining gaps. |\n","# SimReady Add Feature Adapter\n\n## Purpose\nUse this skill to add a direct asset mutation path between exact `FET_###_\u003CRUNTIME>` feature names with integer feature versions, or between profile feature bundles. Feature adapters live under `nv_core\u002Fcip_specs\u002Fasset_handler_modules\u002F` and modify an output USD stage so an asset can move from an input feature\u002Fprofile contract to a target one.\n\nUse this after feature\u002Fprofile differences are known. If no USD mutation is needed, document that no adapter is required.\n\n## Prerequisites\nBefore editing, read:\n\n- `AGENTS.md`\n- `nv_core\u002Fsr_specs\u002Fdocs\u002Fguides\u002Ffeature_adapters\u002Ffeature_adapters.md`\n- source and target feature manifests\n- source and target profile versions, if this is profile-driven\n- existing adapters in the relevant asset handler module\n\n## Inputs\n\nCollect or infer:\n\n| Input | Requirement |\n|---|---|\n| `input_feature_name` | Source feature name \u002F manifest `id`, such as `FET_003_STANDARD`. |\n| `input_feature_version` | Source integer feature version. |\n| `output_feature_name` | Target feature name \u002F manifest `id`, such as `FET_003_PHYSX`. |\n| `output_feature_version` | Target integer feature version. |\n| `profile_path` | Optional source\u002Ftarget profile upgrade path. |\n| `mutation` | Exact USD data changes required. |\n| `module_path` | Asset handler module directory. |\n| `test_assets` | Assets that pass input and should pass output after mutation. |\n\n## Instructions\n\nUse this checklist when changing the repository:\n\n1. Compare source and target manifests. Confirm names use `FET_###_\u003CRUNTIME>` and versions are exact integers, then identify only the requirements that differ.\n2. Decide whether a direct adapter is necessary. For profile transformations, every feature difference must have a direct adapter path or a documented blocker. If target requirements are documentation-only or already satisfied by source assets, document no-op behavior.\n3. Choose or create the asset handler module path.\n4. Add a Python adapter file with `@feature_adapter` metadata using exact feature names and integer versions.\n5. Implement `modify_stage(input_stage, output_stage)`:\n   - read source stage only when needed\n   - mutate output stage deterministically\n   - preserve unrelated authored data\n   - save output stage when complete\n6. Use native USD schemas and existing helper patterns from neighboring adapters.\n7. Add focused tests or manual validation notes:\n   - input validates against source feature\u002Fprofile\n   - output validates against target feature\u002Fprofile\n   - mutation is idempotent or safely repeatable where practical\n8. Update adapter indexes, imports, or registration files if the repo requires them.\n9. If the adapter is needed for a new profile version, update the profile docs or migration notes.\n\n## Examples\n\nExample request:\n\n```text\nAdd a feature adapter that mutates assets from one exact SimReady feature\u002Fprofile version to another.\n```\n\nExpected result summary:\n\n```text\nchanged_files: new docs, manifests, indexes, or validation scaffolding\nvalidation: focused static checks and any relevant docs\u002Fbuild checks\nremaining_gaps: requirement, validator, adapter, profile, or runtime-test follow-up\n```\n\n## Policies\n\n- Do not use adapters to hide invalid source assets; adapters should bridge defined feature differences.\n- Do not mutate source stages in place.\n- Do not invent property values that need user intent or prediction unless the adapter contract explicitly defines defaults.\n- Keep profile upgrade paths direct: every changed feature needs a clear adapter path or a documented blocker.\n\n## Limitations\n\n- Do not mutate published feature or profile versions in place.\n- Do not invent requirement IDs or validator behavior when the contract is ambiguous; record the question.\n- Do not skip index, manifest, validation, or downstream follow-up notes.\n\n## Troubleshooting\n\n- Error: the new concept overlaps an existing artifact. Solution: update the existing capability, requirement, feature, profile, or adapter instead.\n- Error: names or IDs conflict. Solution: re-check naming conventions and nearby indexes before editing further.\n- Error: validation strategy is unclear. Solution: document deferred validation and the exact follow-up skill.\n\n## Resources\n\n- `assets\u002Fopenai.yaml` preserves optional UI metadata for clients that read skill display hints. It is not required for the workflow.\n\n## Summary Format\n\nReport:\n\n| Field | Meaning |\n|---|---|\n| `adapter_name` | Adapter identifier. |\n| `adapter_path` | Python file path. |\n| `input_feature` | Source feature name and integer version. |\n| `output_feature` | Target feature name and integer version. |\n| `mutation_summary` | USD opinions changed. |\n| `profile_upgrade` | Profile path supported, if any. |\n| `validation` | Tests\u002Fassets run and remaining gaps. |\n",{"name":5,"license":15,"metadata":24,"description":7},{"tags":25,"author":29},[26,27,28],"simready","adapter","usd","Shaad Boochoon \u003Csboochoon@nvidia.com>","main","ffa016d3c9a8d32821f71f6d9d916c30e04fcb67","讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002Fsimready-foundation\u002Frepo-docs\u002F.codex\u002Fskills\u002Fsimready-foundation-add-feature-adapter",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":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add leemiracle\u002Fwork4ai --skill simready-foundation-add-feature-adapter",{"tool":44,"command":45},"bunx","bunx skills add leemiracle\u002Fwork4ai --skill simready-foundation-add-feature-adapter",{"tool":47,"command":48},"pnpm","pnpm dlx skills add leemiracle\u002Fwork4ai --skill simready-foundation-add-feature-adapter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002Fsimready-foundation\u002Frepo-docs\u002F.codex\u002Fskills\u002Fsimready-foundation-add-feature-adapter\u002FSKILL.md",true,[],[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"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":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"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":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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",[],[]]