[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A4DXPY675DPDDTR09W609G":3,"skill-same:01M7A4DXPY675DPDDTR09W609G":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},"01M7A4DXPY675DPDDTR09W609G","simready-foundation-conform-fet-003-newton",null,"Use for repairing exact FET_003_NEWTON SimReady conformance for rigid body physics (newton) conformance. Use when a profile, validation report, or user request names FET_003_NEWTON; default to version `0.1.0` unless a profile or report pins another version.","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-conform-fet-003-newton\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: simready-foundation-conform-fet-003-newton\ndescription: \"Use for repairing exact FET_003_NEWTON SimReady conformance for rigid body physics (newton) conformance. Use when a profile, validation report, or user request names FET_003_NEWTON; default to version `0.1.0` unless a profile or report pins another version.\"\nlicense: Apache-2.0\nmetadata:\n  author: \"Shaad Boochoon \u003Csboochoon@nvidia.com>\"\n  tags:\n    - simready\n    - conformance\n    - newton\n---\n\n# SimReady Conform FET_003_NEWTON\n\n## Purpose\n\nUse this exact feature skill when the selected profile, validation report, or user request names `FET_003_NEWTON`. It repairs or stages rigid body physics (newton) conformance without drifting into another runtime contract.\n\nDefault to `FET_003_NEWTON@0.1.0` when the user asks for this feature without a version. Use an older integer version only when the profile, validation report, or user explicitly pins it. If the report names a different `FET_###_RUNTIME` feature, switch to that feature's matching skill before editing.\n\n## Source of Truth\n\nBefore changing an asset or package, read:\n\n- `nv_core\u002Ftiers\u002Fsimready_foundation_tier_core\u002Fsimready\u002Ffoundation\u002Ftier_core\u002Ffeatures\u002FFET_003_NEWTON-0.1.0.json`\n- `nv_core\u002Ftiers\u002Fsimready_foundation_tier_core\u002Fsimready\u002Ffoundation\u002Ftier_core\u002Ffeatures\u002FFET_003_NEWTON.md`\n\nTreat the selected JSON manifest as authoritative for dependencies and requirement IDs. Use the feature markdown for human-readable contract details, requirement links, samples, benchmarks, and adapters.\n\n## Feature Versions\n\n| Version | Dependencies | Requirements |\n|---|---|---|\n| `0.1.0` | None | `RB.COL.001`, `RB.COL.002`, `RB.COL.003`, `RB.COL.004`, `RB.001`, `RB.003`, `RB.005`, `RB.007`, `RB.009`, `RB.010`, `NEWTON.COL.001`, `NEWTON.COL.002`, `NEWTON.MAS.001`, `NEWTON.MAT.001` |\n\n## Feature Adapter\n\nWhen the input already conforms to the neutral base feature, prefer the deterministic feature adapter to author the runtime-specific data first (via the `workspace upgrade` command; see `nv_core\u002Fsr_specs\u002Fdocs\u002Fguides\u002Ffeature_adapters\u002Ffeature_adapters.md`), then repair only the residual requirements below.\n\n| Adapter module | Adapter | Transition | Authors |\n|---|---|---|---|\n| `nv_core\u002Fcip_specs\u002Fasset_handler_modules\u002Fneutral_to_newton` | `rigid_body_neutral_to_prop_newton` | `FET_003_STANDARD@0.1.0` -> `FET_003_NEWTON@0.1.0` | Mesh extents; `NewtonCollisionAPI` + `NewtonMeshCollisionAPI` on existing colliders; `newton:contactGap = 0`; `NewtonMaterialAPI` + default friction tuning on bound physics materials. Satisfies `NEWTON.COL.001`\u002F`NEWTON.COL.002`\u002F`NEWTON.MAT.001`. |\n\n- The adapter runs on a staged output stage and never creates geometry; it only annotates existing colliders.\n- It authors `NewtonMeshCollisionAPI` (not `NewtonSDFCollisionAPI`). If the collider needs SDF-backed collision, or the base `RB.*` rigid-body data is missing, repair that manually per the Workflow below. Strict Newton isolation: do not author `Mjc*`\u002F`Physx*` data or `physics:approximation = \"sdf\"`.\n\n## Workflow\n\n1. Confirm the input exists and identify the exact selected feature\u002Fversion from the profile TOML, validation report, or user request.\n2. Load the selected `FET_003_NEWTON` manifest and the feature markdown before editing.\n3. Load requirement docs linked from the feature markdown for every reported failing requirement.\n4. Create or use a staged output location unless the user explicitly asks for in-place edits.\n5. Repair only the requirements listed by the selected `FET_003_NEWTON` manifest and its dependencies.\n6. Rerun the same profile gate or the narrowest available feature\u002Fcapability validation gate. If runtime evidence is required and unavailable, report that limitation instead of claiming a pass.\n7. Summarize the selected `FET_003_NEWTON` version, changed files, validation evidence, and the first remaining blocker or next exact feature gate.\n\n## Feature Guidance\n\n- **`NewtonCollisionAPI`** carries the shared contact tuning: `newton:contactMargin`\n  (default `0`, outward surface inflation) and `newton:contactGap` (default `-inf` = engine\n  default; the samples author `0`). Both must be non-negative when authored.\n- **`NewtonMeshCollisionAPI`** is the ordinary mesh path (it inherits `NewtonCollisionAPI`).\n  Newton reads the inherited `physics:approximation`; keep it at the intended value\n  (`convexHull`, `convexDecomposition`, ...). `newton:maxHullVertices` (default `-1` = exact\n  hull, minimum `-1`) only matters when `physics:approximation = \"convexHull\"`.\n- **`NewtonSDFCollisionAPI`** is the SDF\u002Fhydroelastic path. It is mutually exclusive with\n  `NewtonMeshCollisionAPI` on the same prim. When SDF tuning is authored, keep contact\n  distances\u002Fpadding non-negative, `newton:sdfMaxResolution` a positive multiple of 8,\n  `newton:sdfTextureFormat` one of `uint8`\u002F`uint16`\u002F`float32`, and\n  `newton:sdfNarrowBandInner \u003C newton:sdfNarrowBandOuter`. Do not guess SDF tuning values\n  when source data or policy is missing.\n- **Hydroelastic contact** (`newton:hydroelasticEnabled`, bool; `newton:hydroelasticStiffness`,\n  positive) is Newton-only (no PhysX equivalent to port). `newton:hydroelasticStiffness` alone\n  does not enable it. When `newton:hydroelasticEnabled = true`, author an SDF source\n  (`newton:sdfMaxResolution` or `newton:sdfTargetVoxelSize`) on the same prim — Newton requires\n  one at parse time unless the mesh carries an attached `mesh.sdf` (a missing source is a warning,\n  not a hard failure).\n- **`NewtonMassAPI`** (`NEWTON.MAS.001`) is optional and applies on an `Xformable` (rigid body\n  or collision `Gprim`), extending `PhysicsMassAPI`. Author it only to override neutral mass\n  resolution: `newton:inertia` must be empty (no opinion) or exactly 6 finite elements\n  `[Ixx, Iyy, Izz, Ixy, Ixz, Iyz]` with non-negative diagonal; `newton:massModel` is `solid` or\n  `shell`; `newton:shellThickness` (default `-inf` = solver chooses) must be finite and `> 0` when\n  authored, and only matters under the `shell` model. Do not invent inertia values — derive them\n  from source data or leave the attribute empty.\n- **`NewtonMaterialAPI`** (`NEWTON.MAT.001`) applies on the `UsdShade.Material` bound to the\n  collider via `material:binding:physics`, extending `PhysicsMaterialAPI`. Aligned with the\n  `UsdPhysicsMaterialAPI` convention (`PMT.001`), validation checks **placement only**: the\n  schema must sit on a `UsdShade.Material` that also carries `PhysicsMaterialAPI`. The Newton\n  tuning attributes (`newton:torsionalFriction` default `0.005`, `newton:rollingFriction`\n  default `0.0001`, and the `newton:contact*` attributes, default `-inf` = engine default) are\n  trusted, not value-checked — author them as needed, or leave the contact attributes at the\n  `-inf` sentinel (equivalent to omitting them).\n- Strict Newton isolation (RV.011): do not author `Mjc*` \u002F `Physx*` schemas or attributes,\n  and do not set `physics:approximation = \"sdf\"` (use `NewtonSDFCollisionAPI` instead).\n\n## Samples\n\n- `sample_content\u002Fcommon_assets\u002Fprops_general\u002Fobs_orange_a02\u002Frunnables\u002Fphysics\u002Fnewton.usd` -\n  single-mesh prop collider with `NewtonMeshCollisionAPI`, `physics:approximation = \"convexHull\"`,\n  `newton:maxHullVertices = -1`, and `newton:contactGap = 0`; and the bound physics material\n  with `NewtonMaterialAPI` authoring all six Newton material attributes at their defaults.\n\n## Report Fields\n\n| Field | Meaning |\n|---|---|\n| `feature` | Exact feature ID and version, for example `FET_003_NEWTON@0.1.0`. |\n| `input` | Source asset, package root, or package definition inspected. |\n| `output` | Staged output path, or `in-place` only when explicitly requested. |\n| `requirements_repaired` | Requirement IDs repaired in this pass. |\n| `validation` | Command or inspection used to verify this exact feature. |\n| `status` | `passed`, `failed`, `skipped`, or `blocked`. |\n| `next_step` | The next exact feature skill or user\u002Fruntime evidence needed. |\n","# SimReady Conform FET_003_NEWTON\n\n## Purpose\n\nUse this exact feature skill when the selected profile, validation report, or user request names `FET_003_NEWTON`. It repairs or stages rigid body physics (newton) conformance without drifting into another runtime contract.\n\nDefault to `FET_003_NEWTON@0.1.0` when the user asks for this feature without a version. Use an older integer version only when the profile, validation report, or user explicitly pins it. If the report names a different `FET_###_RUNTIME` feature, switch to that feature's matching skill before editing.\n\n## Source of Truth\n\nBefore changing an asset or package, read:\n\n- `nv_core\u002Ftiers\u002Fsimready_foundation_tier_core\u002Fsimready\u002Ffoundation\u002Ftier_core\u002Ffeatures\u002FFET_003_NEWTON-0.1.0.json`\n- `nv_core\u002Ftiers\u002Fsimready_foundation_tier_core\u002Fsimready\u002Ffoundation\u002Ftier_core\u002Ffeatures\u002FFET_003_NEWTON.md`\n\nTreat the selected JSON manifest as authoritative for dependencies and requirement IDs. Use the feature markdown for human-readable contract details, requirement links, samples, benchmarks, and adapters.\n\n## Feature Versions\n\n| Version | Dependencies | Requirements |\n|---|---|---|\n| `0.1.0` | None | `RB.COL.001`, `RB.COL.002`, `RB.COL.003`, `RB.COL.004`, `RB.001`, `RB.003`, `RB.005`, `RB.007`, `RB.009`, `RB.010`, `NEWTON.COL.001`, `NEWTON.COL.002`, `NEWTON.MAS.001`, `NEWTON.MAT.001` |\n\n## Feature Adapter\n\nWhen the input already conforms to the neutral base feature, prefer the deterministic feature adapter to author the runtime-specific data first (via the `workspace upgrade` command; see `nv_core\u002Fsr_specs\u002Fdocs\u002Fguides\u002Ffeature_adapters\u002Ffeature_adapters.md`), then repair only the residual requirements below.\n\n| Adapter module | Adapter | Transition | Authors |\n|---|---|---|---|\n| `nv_core\u002Fcip_specs\u002Fasset_handler_modules\u002Fneutral_to_newton` | `rigid_body_neutral_to_prop_newton` | `FET_003_STANDARD@0.1.0` -> `FET_003_NEWTON@0.1.0` | Mesh extents; `NewtonCollisionAPI` + `NewtonMeshCollisionAPI` on existing colliders; `newton:contactGap = 0`; `NewtonMaterialAPI` + default friction tuning on bound physics materials. Satisfies `NEWTON.COL.001`\u002F`NEWTON.COL.002`\u002F`NEWTON.MAT.001`. |\n\n- The adapter runs on a staged output stage and never creates geometry; it only annotates existing colliders.\n- It authors `NewtonMeshCollisionAPI` (not `NewtonSDFCollisionAPI`). If the collider needs SDF-backed collision, or the base `RB.*` rigid-body data is missing, repair that manually per the Workflow below. Strict Newton isolation: do not author `Mjc*`\u002F`Physx*` data or `physics:approximation = \"sdf\"`.\n\n## Workflow\n\n1. Confirm the input exists and identify the exact selected feature\u002Fversion from the profile TOML, validation report, or user request.\n2. Load the selected `FET_003_NEWTON` manifest and the feature markdown before editing.\n3. Load requirement docs linked from the feature markdown for every reported failing requirement.\n4. Create or use a staged output location unless the user explicitly asks for in-place edits.\n5. Repair only the requirements listed by the selected `FET_003_NEWTON` manifest and its dependencies.\n6. Rerun the same profile gate or the narrowest available feature\u002Fcapability validation gate. If runtime evidence is required and unavailable, report that limitation instead of claiming a pass.\n7. Summarize the selected `FET_003_NEWTON` version, changed files, validation evidence, and the first remaining blocker or next exact feature gate.\n\n## Feature Guidance\n\n- **`NewtonCollisionAPI`** carries the shared contact tuning: `newton:contactMargin`\n  (default `0`, outward surface inflation) and `newton:contactGap` (default `-inf` = engine\n  default; the samples author `0`). Both must be non-negative when authored.\n- **`NewtonMeshCollisionAPI`** is the ordinary mesh path (it inherits `NewtonCollisionAPI`).\n  Newton reads the inherited `physics:approximation`; keep it at the intended value\n  (`convexHull`, `convexDecomposition`, ...). `newton:maxHullVertices` (default `-1` = exact\n  hull, minimum `-1`) only matters when `physics:approximation = \"convexHull\"`.\n- **`NewtonSDFCollisionAPI`** is the SDF\u002Fhydroelastic path. It is mutually exclusive with\n  `NewtonMeshCollisionAPI` on the same prim. When SDF tuning is authored, keep contact\n  distances\u002Fpadding non-negative, `newton:sdfMaxResolution` a positive multiple of 8,\n  `newton:sdfTextureFormat` one of `uint8`\u002F`uint16`\u002F`float32`, and\n  `newton:sdfNarrowBandInner \u003C newton:sdfNarrowBandOuter`. Do not guess SDF tuning values\n  when source data or policy is missing.\n- **Hydroelastic contact** (`newton:hydroelasticEnabled`, bool; `newton:hydroelasticStiffness`,\n  positive) is Newton-only (no PhysX equivalent to port). `newton:hydroelasticStiffness` alone\n  does not enable it. When `newton:hydroelasticEnabled = true`, author an SDF source\n  (`newton:sdfMaxResolution` or `newton:sdfTargetVoxelSize`) on the same prim — Newton requires\n  one at parse time unless the mesh carries an attached `mesh.sdf` (a missing source is a warning,\n  not a hard failure).\n- **`NewtonMassAPI`** (`NEWTON.MAS.001`) is optional and applies on an `Xformable` (rigid body\n  or collision `Gprim`), extending `PhysicsMassAPI`. Author it only to override neutral mass\n  resolution: `newton:inertia` must be empty (no opinion) or exactly 6 finite elements\n  `[Ixx, Iyy, Izz, Ixy, Ixz, Iyz]` with non-negative diagonal; `newton:massModel` is `solid` or\n  `shell`; `newton:shellThickness` (default `-inf` = solver chooses) must be finite and `> 0` when\n  authored, and only matters under the `shell` model. Do not invent inertia values — derive them\n  from source data or leave the attribute empty.\n- **`NewtonMaterialAPI`** (`NEWTON.MAT.001`) applies on the `UsdShade.Material` bound to the\n  collider via `material:binding:physics`, extending `PhysicsMaterialAPI`. Aligned with the\n  `UsdPhysicsMaterialAPI` convention (`PMT.001`), validation checks **placement only**: the\n  schema must sit on a `UsdShade.Material` that also carries `PhysicsMaterialAPI`. The Newton\n  tuning attributes (`newton:torsionalFriction` default `0.005`, `newton:rollingFriction`\n  default `0.0001`, and the `newton:contact*` attributes, default `-inf` = engine default) are\n  trusted, not value-checked — author them as needed, or leave the contact attributes at the\n  `-inf` sentinel (equivalent to omitting them).\n- Strict Newton isolation (RV.011): do not author `Mjc*` \u002F `Physx*` schemas or attributes,\n  and do not set `physics:approximation = \"sdf\"` (use `NewtonSDFCollisionAPI` instead).\n\n## Samples\n\n- `sample_content\u002Fcommon_assets\u002Fprops_general\u002Fobs_orange_a02\u002Frunnables\u002Fphysics\u002Fnewton.usd` -\n  single-mesh prop collider with `NewtonMeshCollisionAPI`, `physics:approximation = \"convexHull\"`,\n  `newton:maxHullVertices = -1`, and `newton:contactGap = 0`; and the bound physics material\n  with `NewtonMaterialAPI` authoring all six Newton material attributes at their defaults.\n\n## Report Fields\n\n| Field | Meaning |\n|---|---|\n| `feature` | Exact feature ID and version, for example `FET_003_NEWTON@0.1.0`. |\n| `input` | Source asset, package root, or package definition inspected. |\n| `output` | Staged output path, or `in-place` only when explicitly requested. |\n| `requirements_repaired` | Requirement IDs repaired in this pass. |\n| `validation` | Command or inspection used to verify this exact feature. |\n| `status` | `passed`, `failed`, `skipped`, or `blocked`. |\n| `next_step` | The next exact feature skill or user\u002Fruntime evidence needed. |\n",{"name":5,"license":15,"metadata":24,"description":7},{"tags":25,"author":29},[26,27,28],"simready","conformance","newton","Shaad Boochoon \u003Csboochoon@nvidia.com>","main","ffa016d3c9a8d32821f71f6d9d916c30e04fcb67","讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002Fsimready-foundation\u002Frepo-docs\u002F.codex\u002Fskills\u002Fsimready-foundation-conform-fet-003-newton",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-conform-fet-003-newton",{"tool":44,"command":45},"bunx","bunx skills add leemiracle\u002Fwork4ai --skill simready-foundation-conform-fet-003-newton",{"tool":47,"command":48},"pnpm","pnpm dlx skills add leemiracle\u002Fwork4ai --skill simready-foundation-conform-fet-003-newton","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002Fsimready-foundation\u002Frepo-docs\u002F.codex\u002Fskills\u002Fsimready-foundation-conform-fet-003-newton\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",[],[]]