[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A3GP8YF37ZP8FSCY8VG3SG":3,"skill-same:01M7A3GP8YF37ZP8FSCY8VG3SG":68},{"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":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":6,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M7A3GP8YF37ZP8FSCY8VG3SG","riva-nim-setup",null,"Use when getting started with NVIDIA Riva Speech NIMs: NGC access, Docker login for nvcr.io, NVIDIA Container Toolkit, GPU verification, Riva Python client.","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\u002Fdigital-health-skills\u002Frepo-docs\u002Fskills\u002Friva-nim-setup\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"riva-nim-setup\"\nlicense: \"Apache-2.0\"\ndescription: \"Use when getting started with NVIDIA Riva Speech NIMs: NGC access, Docker login for nvcr.io, NVIDIA Container Toolkit, GPU verification, Riva Python client.\"\nmetadata:\n  author: \"Mayank Jain \u003Cmayjain@nvidia.com>\"\n  team: riva\n  tags:\n    - nvidia\n    - riva\n    - nim\n    - setup\n    - ngc\n    - docker\n    - prerequisites\n  domain: ml\n  version: \"1.0.0\"\n---\n\n# Riva NIM Setup\n\n> **Agent:** Announce each step before presenting it: **Step N\u002F7 — Step Title** (e.g., \"**Step 1\u002F7 — Install NVIDIA Drivers**\").\n\n## Purpose\n\nA first-pass machine preparation: bring a Linux x86_64 host up to the point where it can pull and execute Riva Speech NIM containers. The work below is one-time per host.\n\n## Prerequisites\n\nUp-to-date GPU compatibility, minimum driver versions, VRAM thresholds, and supported operating systems are all maintained at https:\u002F\u002Fdocs.nvidia.com\u002Fnim\u002Fspeech\u002Flatest\u002Fget-started\u002Fprerequisites.html — consult that page before installing anything.\n\nA few invariants worth knowing without clicking through:\n- The host CPU must be x86_64; ARM is not supported.\n- Self-hosting Riva NIMs requires an active NVIDIA AI Enterprise license.\n- Install the **driver alone** — the CUDA toolkit ships inside the NIM container, so installing it separately at the host level is redundant (and a common source of version-skew bugs).\n\n## Instructions\n\nThe setup is seven sequential steps. The first three need root or `sudo`; the remaining four can run as your normal user. Knock them off in order; don't try to pull a NIM container before Step 7 is done.\n\n| # | What | Why it's first |\n|---|---|---|\n| 1 | NVIDIA driver (no CUDA toolkit) | The host has to be able to talk to the GPU at all |\n| 2 | Docker Engine | Container runtime |\n| 3 | NVIDIA Container Toolkit | Bridges Docker to the GPU |\n| 4 | NGC API key | Auth artifact for pulling images |\n| 5 | `docker login nvcr.io` | Activates the key against the registry |\n| 6 | `nvidia-riva-client` (pip) | Lets you exercise the running NIM from Python |\n| 7 | (optional) clone client sample repos | Source for the example scripts |\n\n\n## Step 1 — Install NVIDIA Drivers\n\nUse your distro's package manager to install the driver only. Don't add the CUDA toolkit at the host level — the NIM container ships with its own bundled CUDA stack.\n\n```bash\n# Verify installed driver version\nnvidia-smi\n```\n\nCross-check the version `nvidia-smi` prints against the per-model minimum at https:\u002F\u002Fdocs.nvidia.com\u002Fnim\u002Fspeech\u002Flatest\u002Fget-started\u002Fprerequisites.html before continuing. If you do need a fresh install, the [CUDA installation guide for Linux](https:\u002F\u002Fdocs.nvidia.com\u002Fcuda\u002Fcuda-installation-guide-linux) walks through the distro-specific package manager steps (you'll only follow the driver portion, not the toolkit portion).\n\n## Step 2 — Install Docker\n\nPick the Docker Engine flavor for your distribution from the official matrix: https:\u002F\u002Fdocs.docker.com\u002Fengine\u002Finstall\u002F\n\nOnce installed, add your user to the `docker` group so subsequent commands don't need `sudo`:\n\n```bash\nsudo usermod -aG docker $USER\n# Log out and back in for this to take effect\n```\n\n## Step 3 — Install NVIDIA Container Toolkit\n\nThe Container Toolkit lets Docker containers access the host GPU. Full reference: https:\u002F\u002Fdocs.nvidia.com\u002Fdatacenter\u002Fcloud-native\u002Fcontainer-toolkit\u002Flatest\u002Finstall-guide.html\n\n```bash\nsudo apt-get install -y nvidia-container-toolkit\nsudo nvidia-ctk runtime configure --runtime=docker\nsudo systemctl restart docker\n```\n\nSmoke-test that a container can actually see the GPU:\n\n```bash\ndocker run --rm --runtime=nvidia --gpus all ubuntu nvidia-smi\n```\n\nA successful run prints the same driver version and GPU listing you'd see on the host. If you get an error or empty output, something in Steps 1–3 didn't take — revisit before moving on.\n\n## Step 4 — NGC API Key\n\nThree short steps to generate a key and load it into your shell:\n\n1. Navigate to https:\u002F\u002Forg.ngc.nvidia.com\u002Fsetup\u002Fapi-keys in a browser.\n2. Click **Generate API Key** and grant it at least the **NGC Catalog** service scope.\n3. Copy the key value and export it:\n\n```bash\nexport NGC_API_KEY=${your-key-value}\n```\n\nTo persist across sessions:\n\n```bash\n# Bash\necho \"export NGC_API_KEY=${your-key-value}\" >> ~\u002F.bashrc\n\n# Zsh\necho \"export NGC_API_KEY=${your-key-value}\" >> ~\u002F.zshrc\n```\n> **Security note:** Storing credentials in `~\u002F.bashrc` or `~\u002F.zshrc` saves\n> them in plaintext. Any process with read access to those files can extract the\n> key. For production, use a credential manager or a dedicated `.env` file with\n> `chmod 600` permissions and `source` it instead.\n\n\n## Step 5 — Docker Login to nvcr.io\n\n```bash\necho \"$NGC_API_KEY\" | docker login nvcr.io --username '$oauthtoken' --password-stdin\n```\n\nTwo non-obvious points often missed:\n\n- The `--username` argument is the literal four-character string `$oauthtoken`. It is **not** your NGC display name or email — copy it verbatim.\n- The actual credential is the API key from Step 4, piped to stdin.\n\nA successful login unlocks every `docker pull nvcr.io\u002Fnim\u002Fnvidia\u002F\u003Cimage>:\u003Ctag>` invocation.\n\n## Step 6 — Install Riva Python Client\n\nThe example client scripts in `python-clients\u002F` depend on the `nvidia-riva-client` package — install it now:\n\n```bash\npip install nvidia-riva-client\n```\n\nConfirm the install:\n\n```bash\npython3 -c \"import riva.client; print('Riva client OK')\"\n```\n\n## Step 7 — Clone Client Repos (Optional)\n\nOpen-source sample scripts live in three public repos; clone whichever match the protocol you'll exercise:\n\n```bash\n# Python clients and sample scripts\ngit clone https:\u002F\u002Fgithub.com\u002Fnvidia-riva\u002Fpython-clients\n\n# C++ clients (requires Bazel)\ngit clone https:\u002F\u002Fgithub.com\u002Fnvidia-riva\u002Fcpp-clients\n\n# WebSocket bridge (AudioCodes \u002F telephony)\ngit clone https:\u002F\u002Fgithub.com\u002Fnvidia-riva\u002Fwebsocket-bridge\n```\n\n## Examples\n\nThree quick sanity checks anyone can rerun later to confirm the environment hasn't drifted.\n\n**After Step 3 — container-level GPU visibility:**\n```bash\ndocker run --rm --runtime=nvidia --gpus all ubuntu nvidia-smi\n```\n\n**After Step 6 — Python client import test:**\n```bash\npython3 -c \"import riva.client; print('Riva client OK')\"\n```\n\n**Step 5 reproduced — re-authenticate against `nvcr.io` after a key rotation:**\n```bash\necho \"$NGC_API_KEY\" | docker login nvcr.io --username '$oauthtoken' --password-stdin\n```\n\n\n## Troubleshooting\n\n- **`docker login` fails authentication** → the `--username` value must be the literal `$oauthtoken` string. Many users instinctively type their NGC email or display name here; that's the most common cause of 401 on this step.\n- **CUDA library version mismatches at container start** → check that you didn't install the CUDA toolkit at the host level. The NIM container ships its own toolkit; a parallel host install will fight it.\n- **`docker run` still wants sudo after `usermod -aG docker`** → group membership only applies to new login sessions. Log out and back in (or open a new shell with `newgrp docker`) and the membership takes effect.\n- **`nvidia-container-cli` reports `version: GLIBC_X.YY not found`** → host glibc is older than what the NIM expects. Confirm via `ld -v` against the minimum listed at https:\u002F\u002Fdocs.nvidia.com\u002Fnim\u002Fspeech\u002Flatest\u002Fget-started\u002Fprerequisites.html — older Ubuntu LTS releases may need an upgrade.\n- **Running inside WSL2 on Windows** → swap Docker for Podman, ensure your NVIDIA driver is ≥ 570, use Ubuntu 24.04 inside WSL, and note that only specific Parakeet models are currently supported under WSL2.\n\n\n## Limitations\n\n- Host architecture is x86_64 only. WSL2 on Windows is a partially supported path with Podman replacing Docker and a narrower model catalog (Parakeet subset).\n- Self-hosting a Riva NIM is gated behind an active NVIDIA AI Enterprise license.\n- The host should not carry a separate CUDA toolkit install — the NIM container brings the toolkit it expects. Parallel installs at the host level are a frequent source of breakage.\n- Adding a user to the `docker` group requires re-logging in before that user can run Docker commands without `sudo`.\n\n## Next Steps\n\nOnce Steps 1–7 are green, route to the deployment skill that matches the modality you want:\n\n- **Model choice undecided** → `riva-model-selection`\n- **Speech-to-text deployments** → `riva-asr`\n- **Text-to-speech deployments** → `riva-tts`\n- **Translation deployments** → `riva-nmt`\n\n","# Riva NIM Setup\n\n> **Agent:** Announce each step before presenting it: **Step N\u002F7 — Step Title** (e.g., \"**Step 1\u002F7 — Install NVIDIA Drivers**\").\n\n## Purpose\n\nA first-pass machine preparation: bring a Linux x86_64 host up to the point where it can pull and execute Riva Speech NIM containers. The work below is one-time per host.\n\n## Prerequisites\n\nUp-to-date GPU compatibility, minimum driver versions, VRAM thresholds, and supported operating systems are all maintained at https:\u002F\u002Fdocs.nvidia.com\u002Fnim\u002Fspeech\u002Flatest\u002Fget-started\u002Fprerequisites.html — consult that page before installing anything.\n\nA few invariants worth knowing without clicking through:\n- The host CPU must be x86_64; ARM is not supported.\n- Self-hosting Riva NIMs requires an active NVIDIA AI Enterprise license.\n- Install the **driver alone** — the CUDA toolkit ships inside the NIM container, so installing it separately at the host level is redundant (and a common source of version-skew bugs).\n\n## Instructions\n\nThe setup is seven sequential steps. The first three need root or `sudo`; the remaining four can run as your normal user. Knock them off in order; don't try to pull a NIM container before Step 7 is done.\n\n| # | What | Why it's first |\n|---|---|---|\n| 1 | NVIDIA driver (no CUDA toolkit) | The host has to be able to talk to the GPU at all |\n| 2 | Docker Engine | Container runtime |\n| 3 | NVIDIA Container Toolkit | Bridges Docker to the GPU |\n| 4 | NGC API key | Auth artifact for pulling images |\n| 5 | `docker login nvcr.io` | Activates the key against the registry |\n| 6 | `nvidia-riva-client` (pip) | Lets you exercise the running NIM from Python |\n| 7 | (optional) clone client sample repos | Source for the example scripts |\n\n\n## Step 1 — Install NVIDIA Drivers\n\nUse your distro's package manager to install the driver only. Don't add the CUDA toolkit at the host level — the NIM container ships with its own bundled CUDA stack.\n\n```bash\n# Verify installed driver version\nnvidia-smi\n```\n\nCross-check the version `nvidia-smi` prints against the per-model minimum at https:\u002F\u002Fdocs.nvidia.com\u002Fnim\u002Fspeech\u002Flatest\u002Fget-started\u002Fprerequisites.html before continuing. If you do need a fresh install, the [CUDA installation guide for Linux](https:\u002F\u002Fdocs.nvidia.com\u002Fcuda\u002Fcuda-installation-guide-linux) walks through the distro-specific package manager steps (you'll only follow the driver portion, not the toolkit portion).\n\n## Step 2 — Install Docker\n\nPick the Docker Engine flavor for your distribution from the official matrix: https:\u002F\u002Fdocs.docker.com\u002Fengine\u002Finstall\u002F\n\nOnce installed, add your user to the `docker` group so subsequent commands don't need `sudo`:\n\n```bash\nsudo usermod -aG docker $USER\n# Log out and back in for this to take effect\n```\n\n## Step 3 — Install NVIDIA Container Toolkit\n\nThe Container Toolkit lets Docker containers access the host GPU. Full reference: https:\u002F\u002Fdocs.nvidia.com\u002Fdatacenter\u002Fcloud-native\u002Fcontainer-toolkit\u002Flatest\u002Finstall-guide.html\n\n```bash\nsudo apt-get install -y nvidia-container-toolkit\nsudo nvidia-ctk runtime configure --runtime=docker\nsudo systemctl restart docker\n```\n\nSmoke-test that a container can actually see the GPU:\n\n```bash\ndocker run --rm --runtime=nvidia --gpus all ubuntu nvidia-smi\n```\n\nA successful run prints the same driver version and GPU listing you'd see on the host. If you get an error or empty output, something in Steps 1–3 didn't take — revisit before moving on.\n\n## Step 4 — NGC API Key\n\nThree short steps to generate a key and load it into your shell:\n\n1. Navigate to https:\u002F\u002Forg.ngc.nvidia.com\u002Fsetup\u002Fapi-keys in a browser.\n2. Click **Generate API Key** and grant it at least the **NGC Catalog** service scope.\n3. Copy the key value and export it:\n\n```bash\nexport NGC_API_KEY=${your-key-value}\n```\n\nTo persist across sessions:\n\n```bash\n# Bash\necho \"export NGC_API_KEY=${your-key-value}\" >> ~\u002F.bashrc\n\n# Zsh\necho \"export NGC_API_KEY=${your-key-value}\" >> ~\u002F.zshrc\n```\n> **Security note:** Storing credentials in `~\u002F.bashrc` or `~\u002F.zshrc` saves\n> them in plaintext. Any process with read access to those files can extract the\n> key. For production, use a credential manager or a dedicated `.env` file with\n> `chmod 600` permissions and `source` it instead.\n\n\n## Step 5 — Docker Login to nvcr.io\n\n```bash\necho \"$NGC_API_KEY\" | docker login nvcr.io --username '$oauthtoken' --password-stdin\n```\n\nTwo non-obvious points often missed:\n\n- The `--username` argument is the literal four-character string `$oauthtoken`. It is **not** your NGC display name or email — copy it verbatim.\n- The actual credential is the API key from Step 4, piped to stdin.\n\nA successful login unlocks every `docker pull nvcr.io\u002Fnim\u002Fnvidia\u002F\u003Cimage>:\u003Ctag>` invocation.\n\n## Step 6 — Install Riva Python Client\n\nThe example client scripts in `python-clients\u002F` depend on the `nvidia-riva-client` package — install it now:\n\n```bash\npip install nvidia-riva-client\n```\n\nConfirm the install:\n\n```bash\npython3 -c \"import riva.client; print('Riva client OK')\"\n```\n\n## Step 7 — Clone Client Repos (Optional)\n\nOpen-source sample scripts live in three public repos; clone whichever match the protocol you'll exercise:\n\n```bash\n# Python clients and sample scripts\ngit clone https:\u002F\u002Fgithub.com\u002Fnvidia-riva\u002Fpython-clients\n\n# C++ clients (requires Bazel)\ngit clone https:\u002F\u002Fgithub.com\u002Fnvidia-riva\u002Fcpp-clients\n\n# WebSocket bridge (AudioCodes \u002F telephony)\ngit clone https:\u002F\u002Fgithub.com\u002Fnvidia-riva\u002Fwebsocket-bridge\n```\n\n## Examples\n\nThree quick sanity checks anyone can rerun later to confirm the environment hasn't drifted.\n\n**After Step 3 — container-level GPU visibility:**\n```bash\ndocker run --rm --runtime=nvidia --gpus all ubuntu nvidia-smi\n```\n\n**After Step 6 — Python client import test:**\n```bash\npython3 -c \"import riva.client; print('Riva client OK')\"\n```\n\n**Step 5 reproduced — re-authenticate against `nvcr.io` after a key rotation:**\n```bash\necho \"$NGC_API_KEY\" | docker login nvcr.io --username '$oauthtoken' --password-stdin\n```\n\n\n## Troubleshooting\n\n- **`docker login` fails authentication** → the `--username` value must be the literal `$oauthtoken` string. Many users instinctively type their NGC email or display name here; that's the most common cause of 401 on this step.\n- **CUDA library version mismatches at container start** → check that you didn't install the CUDA toolkit at the host level. The NIM container ships its own toolkit; a parallel host install will fight it.\n- **`docker run` still wants sudo after `usermod -aG docker`** → group membership only applies to new login sessions. Log out and back in (or open a new shell with `newgrp docker`) and the membership takes effect.\n- **`nvidia-container-cli` reports `version: GLIBC_X.YY not found`** → host glibc is older than what the NIM expects. Confirm via `ld -v` against the minimum listed at https:\u002F\u002Fdocs.nvidia.com\u002Fnim\u002Fspeech\u002Flatest\u002Fget-started\u002Fprerequisites.html — older Ubuntu LTS releases may need an upgrade.\n- **Running inside WSL2 on Windows** → swap Docker for Podman, ensure your NVIDIA driver is ≥ 570, use Ubuntu 24.04 inside WSL, and note that only specific Parakeet models are currently supported under WSL2.\n\n\n## Limitations\n\n- Host architecture is x86_64 only. WSL2 on Windows is a partially supported path with Podman replacing Docker and a narrower model catalog (Parakeet subset).\n- Self-hosting a Riva NIM is gated behind an active NVIDIA AI Enterprise license.\n- The host should not carry a separate CUDA toolkit install — the NIM container brings the toolkit it expects. Parallel installs at the host level are a frequent source of breakage.\n- Adding a user to the `docker` group requires re-logging in before that user can run Docker commands without `sudo`.\n\n## Next Steps\n\nOnce Steps 1–7 are green, route to the deployment skill that matches the modality you want:\n\n- **Model choice undecided** → `riva-model-selection`\n- **Speech-to-text deployments** → `riva-asr`\n- **Text-to-speech deployments** → `riva-tts`\n- **Translation deployments** → `riva-nmt`\n\n",{"name":5,"license":15,"metadata":24,"description":7},{"tags":25,"team":27,"author":33,"domain":34,"version":35},[26,27,28,29,30,31,32],"nvidia","riva","nim","setup","ngc","docker","prerequisites","Mayank Jain \u003Cmayjain@nvidia.com>","ml","1.0.0","main","ffa016d3c9a8d32821f71f6d9d916c30e04fcb67","讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002Fdigital-health-skills\u002Frepo-docs\u002Fskills\u002Friva-nim-setup",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":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add leemiracle\u002Fwork4ai --skill riva-nim-setup",{"tool":50,"command":51},"bunx","bunx skills add leemiracle\u002Fwork4ai --skill riva-nim-setup",{"tool":53,"command":54},"pnpm","pnpm dlx skills add leemiracle\u002Fwork4ai --skill riva-nim-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002Fdigital-health-skills\u002Frepo-docs\u002Fskills\u002Friva-nim-setup\u002FSKILL.md",true,[58,64],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"BENCHMARK.md","REFERENCE","参考文档",3603,"https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002Fdigital-health-skills\u002Frepo-docs\u002Fskills\u002Friva-nim-setup\u002FBENCHMARK.md",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"skill-card.md",4087,"https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002Fdigital-health-skills\u002Frepo-docs\u002Fskills\u002Friva-nim-setup\u002Fskill-card.md",[69,76,83,90,97,104],{"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},"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":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},"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":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},"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"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",[],[]]