[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A3FZ09RAGSDM372V03C0ZB":3,"skill-same:01M7A3FZ09RAGSDM372V03C0ZB":79},{"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":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M7A3FZ09RAGSDM372V03C0ZB","digital-health-clinical-asr-setup",null,"Stage 1 of Clinical ASR Flywheel. Use when bootstrapping a cycle: NVCF+MW disclosure, NVIDIA_API_KEY check, deps install, TTS+ASR smoke test.","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\u002Fdigital-health-clinical-asr-setup\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"digital-health-clinical-asr-setup\"\ndescription: \"Stage 1 of Clinical ASR Flywheel. Use when bootstrapping a cycle: NVCF+MW disclosure, NVIDIA_API_KEY check, deps install, TTS+ASR smoke test.\"\nversion: \"1.1.0\"\nauthor: \"Ben Randoing \u003Cbrandoing@nvidia.com>\"\ntags:\n  - clinical-asr\n  - setup\n  - flywheel\n  - bootstrap\ntools:\n  - Read\n  - Write\n  - Bash\n  - Skill\nlicense: Apache-2.0\ncompatibility: \"NVIDIA_API_KEY (required) for hosted Magpie TTS + Parakeet\u002FNemotron ASR via NVCF. DICTIONARY_API_KEY (optional) for Merriam-Webster pronunciation lookup. NGC_API_KEY (optional) for Stage 4 fine-tune. Python 3.10+.\"\nmetadata:\n  author: \"Ben Randoing \u003Cbrandoing@nvidia.com>\"\n  tags:\n    - clinical-asr\n    - flywheel\n    - setup\n    - bootstrap\n  team: healthcare-tme\n  domain: ai-ml\n  stage: 1\n  next_skill: digital-health-clinical-asr-build\n---\n\n\u003C!--\nSPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.\nSPDX-License-Identifier: Apache-2.0\n-->\n\n# Clinical ASR Flywheel — Stage 1 (Setup)\n\n> **Agent: this file is the complete Stage 1 procedure.** Do not invoke `find`, `ls`, `rg`, or `grep` looking for an installer or hidden config — there isn't one. The four sections below (outbound-data disclosure, three numbered checks, sibling hand-off) are all required reading; don't skip any. Function IDs, env-var conventions, and the smoke-test gate are inlined further down — answer from what's actually written here rather than from prior Riva\u002FNVCF familiarity.\n\nStage 1 has one job: prove the user can reach NVIDIA's hosted speech stack with the `NVIDIA_API_KEY` they currently hold. Once a single clinical sentence round-trips through Magpie TTS → Parakeet\u002FNemotron ASR successfully, the user is cleared to advance to `\u002Fdigital-health-clinical-asr-build`.\n\nThe four-stage flywheel exists to drive down **KER (keyword error rate)** on clinical entities — drugs, procedures, anatomy, conditions, labs, roles. WER averages obscure the failures that hurt clinically; KER is what Stage 3 will measure you against.\n\nThere is **no installer script** anywhere in this skill — not `install.sh`, not `setup.py`, nothing hidden. Stage 1 *is* the three steps below: verify the key, install Python deps, run the smoke test. Anything past Stage 1 is composed from sibling skills (`\u002Fdata-designer`, `\u002Friva-tts`, the inlined Stage 3 ASR recipe, `\u002Friva-asr-custom`). If a user asks \"what script installs everything?\", answer from this paragraph; don't go searching.\n\n## Outbound data flows — surface before any text or audio is sent\n\nTwo external endpoints receive data during this flywheel. The user has to acknowledge both before Stage 2 begins, against whatever data-governance policy their organization enforces. **Render the table below word-for-word in your response — a paraphrase doesn't satisfy the disclosure; the literal phrasing is what counts.**\n\n| Service | What gets sent | When | Hosted by |\n|---|---|---|---|\n| **NVIDIA NVCF** (`grpc.nvcf.nvidia.com`) | The clinical sentences you synthesize (text), and the WAV files you transcribe (audio) | Every Stage 2 TTS call and every Stage 3 ASR call | NVIDIA, governed by build.nvidia.com terms |\n| **Merriam-Webster** (`dictionaryapi.com` JSON API **or** the public `merriam-webster.com` HTML site) | Individual clinical terms (drug names, anatomy, procedures), one HTTP request per term | Stage 2 IPA tagging — see \"Two MW paths\" below for which endpoint applies | Merriam-Webster, governed by their API or site terms |\n\nThe data is **synthetic by construction** — the flywheel manufactures sentences and audio from a user-curated term list, never from real patient encounters. That said: **do not feed real patient transcripts, recorded clinical audio, or any PHI through any stage.** If the term list itself contains sensitive material (codename drugs, unreleased product names), the user should consult their organization's external-API policy before proceeding. Either endpoint can be turned off:\n\n- **Skip Merriam-Webster entirely:** leave `DICTIONARY_API_KEY` unset and don't run a scraper. Stage 2 falls back to Magpie G2P, which still works but with weaker coverage on long-tail clinical terms.\n- **Skip NVCF:** this is a hard stop. Magpie TTS + Parakeet\u002FNemotron ASR *are* the workload; without them this skill family is the wrong tool — a self-hosted ASR\u002FTTS pipeline is what you want instead.\n\nRecommend a copy of this notice lands in the user's workspace `README.md`; bring it forward on first invocation if it isn't already there.\n\n## Purpose\n\nGet a fresh environment ready for Stage 2. Three things to confirm: key is present, deps import cleanly, hosted stack actually answers. Close by naming which skill to run next.\n\nThe four `digital-health-clinical-asr-*` skills are **self-contained** — every TTS, ASR, IPA-tagging, and scoring recipe lives inside them; no other agent skill needs installing to run the flywheel end-to-end.\n\nThis skill takes no opinion on workspace layout. The user decides where their cycle artifacts live; `data\u002Feval_sets\u002Fcycle\u003CN>\u002F` is not imposed.\n\n## When to use this skill\n\nActivate on user phrases like:\n\n- \"Set up the Clinical ASR Flywheel\"\n- \"Initialize the clinical-asr eval\"\n- \"I want to evaluate ASR on clinical terminology — where do I start?\"\n- \"Bootstrap my environment for the flywheel\"\n- \"What do I need installed before I run the flywheel?\"\n\nDo **not** activate when:\n\n- The user already has a manifest and wants to score it → `\u002Fdigital-health-clinical-asr-eval`\n- The user already has the env set up and wants to curate terms → `\u002Fdigital-health-clinical-asr-build`\n- The user is asking about Stage 4 fine-tune NGC\u002FDocker setup specifically → that's covered inside `\u002Fdigital-health-clinical-asr-finetune`\n\n## Prerequisites\n\n| Requirement | Required? | Why | How |\n|---|---|---|---|\n| `NVIDIA_API_KEY` (`nvapi-…`) | **Required** | Hosted Magpie TTS + Parakeet\u002FNemotron ASR via NVCF | Issue at \u003Chttps:\u002F\u002Fbuild.nvidia.com>; `export NVIDIA_API_KEY=...` in shell |\n| Python ≥ 3.10 | **Required** | NeMo client, scoring, manifest tools | `python3 --version` |\n| `nvidia-riva-client`, `pandas`, `soundfile`, `requests` | **Required** | TTS + ASR clients, manifest I\u002FO, MW lookup | `pip install nvidia-riva-client pandas soundfile requests` |\n| `DICTIONARY_API_KEY` | Optional | Merriam-Webster Medical Dictionary lookup via the JSON API (Path A in the build skill — recommended) | Free key at \u003Chttps:\u002F\u002Fdictionaryapi.com>. Path B (HTML scrape of `merriam-webster.com`, no key, brittle) is also documented in the build skill if you can't get a key. Without either path, Stage 2 falls through to Magpie G2P with weaker long-tail coverage. |\n| `jiwer` | Optional | Reference WER\u002FCER against the inlined Levenshtein implementation | `pip install jiwer` — the eval skill includes a pure-Python fallback |\n| (Stage 4 only) `NGC_API_KEY` + CUDA host + NeMo container | Optional, deferred | Fine-tune workload | Set up inside `\u002Fdigital-health-clinical-asr-finetune`; defer until the eval shows KER > 0.3 |\n\n## Instructions\n\n**Scope.** This skill performs **read-only environment checks**: confirming a key is exported (length-only), the Python version, that libraries import, and that the hosted NVCF stack responds to a single smoke-test round-trip. It does **not** install system packages, modify shell rc files, write to disk outside an explicit `.venv\u002F`, or attempt to authenticate with the real key value. Validate; never mutate without explicit user direction.\n\n### 1a. Verify `NVIDIA_API_KEY` (length-only — never echo the value)\n\n```bash\n# Export NVIDIA_API_KEY in your shell — never echo or commit the value\nexport NVIDIA_API_KEY=nvapi-...     # from https:\u002F\u002Fbuild.nvidia.com\n\n# Length-only check; the key value never appears in any log\ntest -n \"$NVIDIA_API_KEY\" && echo \"NVIDIA_API_KEY len=${#NVIDIA_API_KEY}\"\n```\n\nA length of 70+ is normal. If the output is empty or shows `len=0`, the user must paste a key from \u003Chttps:\u002F\u002Fbuild.nvidia.com>. Do **not** print the key, even truncated. To persist across shell sessions, add the `export` line to your shell rc (`~\u002F.bashrc`, `~\u002F.zshrc`) — or use a per-directory tool like `direnv`.\n\n### 1b. Install Python dependencies\n\n```bash\npython3 -m venv .venv\nsource .venv\u002Fbin\u002Factivate\npip install nvidia-riva-client pandas soundfile requests\n# optional\npip install jiwer\n```\n\nFor Stage 4 (fine-tune) only: `nemo-toolkit` and Docker + NVIDIA Container Toolkit are also required. Defer those to `\u002Fdigital-health-clinical-asr-finetune` — there is no point installing them up front if the user may never reach Stage 4.\n\n### 1c. Smoke-test the hosted NVCF stack\n\n**`NVIDIA_API_KEY` handling — load-bearing, do not deviate:**\n\n- The agent harness reads `$NVIDIA_API_KEY` from the shell and passes it as an **explicit function argument** to `smoke_test(api_key=…)`.\n- Auditors can grep the recipe for every wire crossing — every `api_key` use is visible in `auth_for(...)`.\n- Do **not** `echo`, `print`, or log the key value (including truncated). Length-only checks are fine (see §1a).\n- Do **not** let the recipe read `os.environ[\"NVIDIA_API_KEY\"]` itself — the explicit-argument pattern is the auditability guarantee.\n- Do **not** commit the key to any file, including `.env` examples or notebook outputs.\n\nVerify the `NVIDIA_API_KEY` actually works against Magpie TTS and Parakeet\u002FNemotron ASR before advancing. The four skills inline every recipe needed; this round-trip just confirms the API key + network path are real.\n\nThe agent harness loads the `NVIDIA_API_KEY` shell variable and passes it as an explicit function argument to the helpers below. The recipe code itself does not read environment variables — auditors can see exactly which API keys cross the wire.\n\n```python\nimport wave, tempfile\nimport riva.client\n\nNVCF_HOST = \"grpc.nvcf.nvidia.com:443\"\nMAGPIE_FUNCTION_ID    = \"877104f7-e885-42b9-8de8-f6e4c6303969\"   # Magpie TTS\nPARAKEET_FUNCTION_ID  = \"d3fe9151-442b-4204-a70d-5fcc597fd610\"   # Parakeet TDT 0.6B v2 (offline ASR)\n\ndef auth_for(function_id: str, api_key: str) -> riva.client.Auth:\n    return riva.client.Auth(\n        use_ssl=True, uri=NVCF_HOST,\n        metadata_args=[\n            [\"function-id\", function_id],\n            [\"authorization\", f\"Bearer {api_key}\"],\n        ],\n    )\n\ndef smoke_test(api_key: str) -> str:\n    \"\"\"Caller passes api_key (the harness reads $NVIDIA_API_KEY at the shell;\n    this code never touches the environment). Returns the ASR transcript.\"\"\"\n\n    # 1. TTS: \"The patient was prescribed cefazolin.\"\n    tts = riva.client.SpeechSynthesisService(auth_for(MAGPIE_FUNCTION_ID, api_key))\n    pcm = b\"\".join(c.audio for c in tts.synthesize_online(\n        text=\"The patient was prescribed cefazolin.\",\n        voice_name=\"Magpie-Multilingual.EN-US.Mia\",\n        language_code=\"en-US\", sample_rate_hz=16000,\n    ))\n    with tempfile.NamedTemporaryFile(suffix=\".wav\", delete=False) as f:\n        with wave.open(f, \"wb\") as w:\n            w.setnchannels(1); w.setsampwidth(2); w.setframerate(16000); w.writeframes(pcm)\n        wav_path = f.name\n\n    # 2. ASR: transcribe the WAV we just synthesized.\n    asr = riva.client.ASRService(auth_for(PARAKEET_FUNCTION_ID, api_key))\n    with open(wav_path, \"rb\") as f:\n        audio_bytes = f.read()\n    config = riva.client.RecognitionConfig(\n        encoding=riva.client.AudioEncoding.LINEAR_PCM,\n        sample_rate_hertz=16000, language_code=\"en-US\",\n        max_alternatives=1, enable_automatic_punctuation=True,\n    )\n    response = asr.offline_recognize(audio_bytes, config)\n    transcript = response.results[0].alternatives[0].transcript if response.results else \"\"\n    print(f\"TTS:  The patient was prescribed cefazolin.\")\n    print(f\"ASR:  {transcript}\")\n    return transcript\n\n# Invoke from the agent (api_key sourced by the harness, not by this code):\n# smoke_test(api_key=\"\u003CNVIDIA_API_KEY value>\")\n```\n\n**Run the smoke test — don't defer it.** This is the gate that proves Stages 2–4 can reach the hosted stack with the user's current key. \"I can run it later\" is not an acceptable completion of Stage 1; either invoke `smoke_test(api_key=…)` now or, if the user has explicitly opted out, log the deferral in your closing summary so they know what they're missing.\n\nIf the transcript matches the input within ~1 token, the hosted stack is reachable and the user can advance to Stage 2. If either call fails:\n\n- `401 Unauthorized` \u002F `PERMISSION_DENIED` → `NVIDIA_API_KEY` is wrong, expired, or not exported in this shell. Re-export and re-test.\n- `404` \u002F `INVALID_ARGUMENT: function not found` → the function ID is stale. Look up the current ID at \u003Chttps:\u002F\u002Fbuild.nvidia.com> and update the constant above.\n- `RESOURCE_EXHAUSTED` → NVCF rate limit. Retry after 30 seconds; this is normal under load.\n- Network\u002FTLS errors → corporate proxy or DNS issue. Test `curl https:\u002F\u002Fbuild.nvidia.com` first.\n\n### 1d. (Optional) Verify Merriam-Webster lookup\n\nTwo paths produce a `merriam-webster`-tagged manifest row in Stage 2. Pick one (or neither — Magpie G2P fall-through is a valid posture):\n\n- **Path A — JSON API + key.** Recommended for standalone use of this skill. Check the key is set:\n\n  ```bash\n  test -n \"$DICTIONARY_API_KEY\" && echo \"DICTIONARY_API_KEY len=${#DICTIONARY_API_KEY}\" \\\n    || echo \"DICTIONARY_API_KEY not set — Path A is off\"\n  ```\n\n  Free key issues instantly at \u003Chttps:\u002F\u002Fdictionaryapi.com>.\n\n- **Path B — HTML scraping.** No API key needed; reachability is the only prerequisite. Brittle to MW site HTML changes; recipe inlined in the build skill's `references\u002Fpronunciation-pipeline.md`.\n\n  ```bash\n  curl -fsS -o \u002Fdev\u002Fnull -w \"merriam-webster.com reachable, HTTP %{http_code}\\n\" \\\n    https:\u002F\u002Fwww.merriam-webster.com\u002Fmedical\u002Fcefazolin\n  ```\n\n  If you don't want to maintain a scraper, use Path A instead.\n\nRemember the data-disclosure note at the top: under either path, each clinical term in your seed list goes out as an HTTP request to a Merriam-Webster endpoint.\n\n## Examples\n\n**Fresh shell, never run before.** User says something like *\"I want to start the flywheel.\"* → Quote the disclosure table first, then walk through 1a → 1b → 1c in order. On a green smoke test, point them at `\u002Fdigital-health-clinical-asr-build` and explicitly name KER as the metric Stage 3 will judge them by.\n\n**Returning user, env already up.** User says *\"I already have the env, just confirm I'm good to go.\"* → Skip the venv + `pip install` (1b). Run only the length check (1a) and the smoke test (1c). On green, advance.\n\n## Artifacts produced\n\n- `NVIDIA_API_KEY` exported in the user's shell\n- An activated virtualenv with `nvidia-riva-client`, `pandas`, `soundfile`, `requests`\n- A confirmed TTS→ASR round-trip on a clinical sentence (proof the hosted stack works)\n\nNo manifest, audio, or model artifact is produced at this stage — those come at Stages 2–4.\n\n## Troubleshooting\n\n- **Length check shows nothing or `len=0`** → `NVIDIA_API_KEY` isn't exported in this shell. Run `export NVIDIA_API_KEY=nvapi-...` and re-check.\n- **Variable is set in one shell but not another** → exports don't persist across sessions. Add the `export` line to your shell rc (`~\u002F.bashrc`, `~\u002F.zshrc`), or use a per-directory loader like `direnv`.\n- **`401 Unauthorized` on the smoke test** → key value is wrong or expired. Re-issue at \u003Chttps:\u002F\u002Fbuild.nvidia.com>.\n- **`grpc.RpcError: function not found`** → the inlined function IDs need updating against the current NVCF catalog. Check \u003Chttps:\u002F\u002Fbuild.nvidia.com> and edit the constants in 1c. The eval skill (`\u002Fdigital-health-clinical-asr-eval`) provides a catalog of current function IDs in its Step 3a \"Other catalog options\" list.\n- **`StatusCode.INVALID_ARGUMENT` with `CUDA error: an illegal memory access was encountered`** → NVCF-side backend fault on this specific function ID (Triton\u002FPyTorch on NVCF, not your env). Either retry later or temporarily point at a different offline ASR NIM — Whisper Large v3 function-id `b702f636-f60c-4a3d-a6f4-f3568c13bd7d` is the closest drop-in (also offline; pass `language_code=\"en\"` instead of `\"en-US\"`). For routine eval cycles, prefer to wait for the Parakeet backend to recover so Stage 3 baseline and Stage 4 SFT base stay aligned.\n- **`TypeError: Auth.__init__() got an unexpected keyword argument 'ssl_cert'`** → you're on `nvidia-riva-client >= 2.x` where the kwarg was renamed to `ssl_root_cert` (and is no longer needed for hosted NVCF). Drop the `ssl_cert=None,` line from your local copy of the recipe.\n- **`ModuleNotFoundError: riva.client`** → step 1b was skipped or the venv isn't activated. `source .venv\u002Fbin\u002Factivate && pip install nvidia-riva-client`.\n\n## Limitations\n\n- **Scope is environment readiness only.** Whether the user's term list or pronunciation overrides make sense is decided in `\u002Fdigital-health-clinical-asr-build`, not here.\n- **Magpie en-US assumption.** Downstream IPA validation rides on Magpie's English phoneme inventory; other locales require a different phoneme set entirely.\n- **Hosted NVCF is the assumed deployment.** Running self-hosted Riva NIMs is possible but the setup for that lives inside `\u002Fdigital-health-clinical-asr-finetune` Stage 4d.\n- **Synthetic data only.** This skill family is built for benchmarks generated from a curated term list. Real patient transcripts and recorded audio must not flow through any stage.\n\n## Next steps\n\n**Mandatory close on success:** finish the Stage 1 response by **pointing the user explicitly to `\u002Fdigital-health-clinical-asr-build`** and **naming KER (keyword error rate) as the headline measure** they'll see at Stage 3. Both pointers are required, not optional — they place the user inside the four-stage flywheel.\n\n- **Default forward route:** `\u002Fdigital-health-clinical-asr-build` — specialty interview, term curation, IPA tagging, NeMo manifest synthesis.\n- **Direct jump to Stage 3** (only when the user is bringing their own NeMo-format manifest with `term` \u002F `entity_category` \u002F `ipa_source` fields): `\u002Fdigital-health-clinical-asr-eval`.\n\n## References\n\n- [`references\u002Fdependency-ownership.md`](references\u002Fdependency-ownership.md) — boundary between skill-owned and companion-owned responsibilities.\n\n","\u003C!--\nSPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.\nSPDX-License-Identifier: Apache-2.0\n-->\n\n# Clinical ASR Flywheel — Stage 1 (Setup)\n\n> **Agent: this file is the complete Stage 1 procedure.** Do not invoke `find`, `ls`, `rg`, or `grep` looking for an installer or hidden config — there isn't one. The four sections below (outbound-data disclosure, three numbered checks, sibling hand-off) are all required reading; don't skip any. Function IDs, env-var conventions, and the smoke-test gate are inlined further down — answer from what's actually written here rather than from prior Riva\u002FNVCF familiarity.\n\nStage 1 has one job: prove the user can reach NVIDIA's hosted speech stack with the `NVIDIA_API_KEY` they currently hold. Once a single clinical sentence round-trips through Magpie TTS → Parakeet\u002FNemotron ASR successfully, the user is cleared to advance to `\u002Fdigital-health-clinical-asr-build`.\n\nThe four-stage flywheel exists to drive down **KER (keyword error rate)** on clinical entities — drugs, procedures, anatomy, conditions, labs, roles. WER averages obscure the failures that hurt clinically; KER is what Stage 3 will measure you against.\n\nThere is **no installer script** anywhere in this skill — not `install.sh`, not `setup.py`, nothing hidden. Stage 1 *is* the three steps below: verify the key, install Python deps, run the smoke test. Anything past Stage 1 is composed from sibling skills (`\u002Fdata-designer`, `\u002Friva-tts`, the inlined Stage 3 ASR recipe, `\u002Friva-asr-custom`). If a user asks \"what script installs everything?\", answer from this paragraph; don't go searching.\n\n## Outbound data flows — surface before any text or audio is sent\n\nTwo external endpoints receive data during this flywheel. The user has to acknowledge both before Stage 2 begins, against whatever data-governance policy their organization enforces. **Render the table below word-for-word in your response — a paraphrase doesn't satisfy the disclosure; the literal phrasing is what counts.**\n\n| Service | What gets sent | When | Hosted by |\n|---|---|---|---|\n| **NVIDIA NVCF** (`grpc.nvcf.nvidia.com`) | The clinical sentences you synthesize (text), and the WAV files you transcribe (audio) | Every Stage 2 TTS call and every Stage 3 ASR call | NVIDIA, governed by build.nvidia.com terms |\n| **Merriam-Webster** (`dictionaryapi.com` JSON API **or** the public `merriam-webster.com` HTML site) | Individual clinical terms (drug names, anatomy, procedures), one HTTP request per term | Stage 2 IPA tagging — see \"Two MW paths\" below for which endpoint applies | Merriam-Webster, governed by their API or site terms |\n\nThe data is **synthetic by construction** — the flywheel manufactures sentences and audio from a user-curated term list, never from real patient encounters. That said: **do not feed real patient transcripts, recorded clinical audio, or any PHI through any stage.** If the term list itself contains sensitive material (codename drugs, unreleased product names), the user should consult their organization's external-API policy before proceeding. Either endpoint can be turned off:\n\n- **Skip Merriam-Webster entirely:** leave `DICTIONARY_API_KEY` unset and don't run a scraper. Stage 2 falls back to Magpie G2P, which still works but with weaker coverage on long-tail clinical terms.\n- **Skip NVCF:** this is a hard stop. Magpie TTS + Parakeet\u002FNemotron ASR *are* the workload; without them this skill family is the wrong tool — a self-hosted ASR\u002FTTS pipeline is what you want instead.\n\nRecommend a copy of this notice lands in the user's workspace `README.md`; bring it forward on first invocation if it isn't already there.\n\n## Purpose\n\nGet a fresh environment ready for Stage 2. Three things to confirm: key is present, deps import cleanly, hosted stack actually answers. Close by naming which skill to run next.\n\nThe four `digital-health-clinical-asr-*` skills are **self-contained** — every TTS, ASR, IPA-tagging, and scoring recipe lives inside them; no other agent skill needs installing to run the flywheel end-to-end.\n\nThis skill takes no opinion on workspace layout. The user decides where their cycle artifacts live; `data\u002Feval_sets\u002Fcycle\u003CN>\u002F` is not imposed.\n\n## When to use this skill\n\nActivate on user phrases like:\n\n- \"Set up the Clinical ASR Flywheel\"\n- \"Initialize the clinical-asr eval\"\n- \"I want to evaluate ASR on clinical terminology — where do I start?\"\n- \"Bootstrap my environment for the flywheel\"\n- \"What do I need installed before I run the flywheel?\"\n\nDo **not** activate when:\n\n- The user already has a manifest and wants to score it → `\u002Fdigital-health-clinical-asr-eval`\n- The user already has the env set up and wants to curate terms → `\u002Fdigital-health-clinical-asr-build`\n- The user is asking about Stage 4 fine-tune NGC\u002FDocker setup specifically → that's covered inside `\u002Fdigital-health-clinical-asr-finetune`\n\n## Prerequisites\n\n| Requirement | Required? | Why | How |\n|---|---|---|---|\n| `NVIDIA_API_KEY` (`nvapi-…`) | **Required** | Hosted Magpie TTS + Parakeet\u002FNemotron ASR via NVCF | Issue at \u003Chttps:\u002F\u002Fbuild.nvidia.com>; `export NVIDIA_API_KEY=...` in shell |\n| Python ≥ 3.10 | **Required** | NeMo client, scoring, manifest tools | `python3 --version` |\n| `nvidia-riva-client`, `pandas`, `soundfile`, `requests` | **Required** | TTS + ASR clients, manifest I\u002FO, MW lookup | `pip install nvidia-riva-client pandas soundfile requests` |\n| `DICTIONARY_API_KEY` | Optional | Merriam-Webster Medical Dictionary lookup via the JSON API (Path A in the build skill — recommended) | Free key at \u003Chttps:\u002F\u002Fdictionaryapi.com>. Path B (HTML scrape of `merriam-webster.com`, no key, brittle) is also documented in the build skill if you can't get a key. Without either path, Stage 2 falls through to Magpie G2P with weaker long-tail coverage. |\n| `jiwer` | Optional | Reference WER\u002FCER against the inlined Levenshtein implementation | `pip install jiwer` — the eval skill includes a pure-Python fallback |\n| (Stage 4 only) `NGC_API_KEY` + CUDA host + NeMo container | Optional, deferred | Fine-tune workload | Set up inside `\u002Fdigital-health-clinical-asr-finetune`; defer until the eval shows KER > 0.3 |\n\n## Instructions\n\n**Scope.** This skill performs **read-only environment checks**: confirming a key is exported (length-only), the Python version, that libraries import, and that the hosted NVCF stack responds to a single smoke-test round-trip. It does **not** install system packages, modify shell rc files, write to disk outside an explicit `.venv\u002F`, or attempt to authenticate with the real key value. Validate; never mutate without explicit user direction.\n\n### 1a. Verify `NVIDIA_API_KEY` (length-only — never echo the value)\n\n```bash\n# Export NVIDIA_API_KEY in your shell — never echo or commit the value\nexport NVIDIA_API_KEY=nvapi-...     # from https:\u002F\u002Fbuild.nvidia.com\n\n# Length-only check; the key value never appears in any log\ntest -n \"$NVIDIA_API_KEY\" && echo \"NVIDIA_API_KEY len=${#NVIDIA_API_KEY}\"\n```\n\nA length of 70+ is normal. If the output is empty or shows `len=0`, the user must paste a key from \u003Chttps:\u002F\u002Fbuild.nvidia.com>. Do **not** print the key, even truncated. To persist across shell sessions, add the `export` line to your shell rc (`~\u002F.bashrc`, `~\u002F.zshrc`) — or use a per-directory tool like `direnv`.\n\n### 1b. Install Python dependencies\n\n```bash\npython3 -m venv .venv\nsource .venv\u002Fbin\u002Factivate\npip install nvidia-riva-client pandas soundfile requests\n# optional\npip install jiwer\n```\n\nFor Stage 4 (fine-tune) only: `nemo-toolkit` and Docker + NVIDIA Container Toolkit are also required. Defer those to `\u002Fdigital-health-clinical-asr-finetune` — there is no point installing them up front if the user may never reach Stage 4.\n\n### 1c. Smoke-test the hosted NVCF stack\n\n**`NVIDIA_API_KEY` handling — load-bearing, do not deviate:**\n\n- The agent harness reads `$NVIDIA_API_KEY` from the shell and passes it as an **explicit function argument** to `smoke_test(api_key=…)`.\n- Auditors can grep the recipe for every wire crossing — every `api_key` use is visible in `auth_for(...)`.\n- Do **not** `echo`, `print`, or log the key value (including truncated). Length-only checks are fine (see §1a).\n- Do **not** let the recipe read `os.environ[\"NVIDIA_API_KEY\"]` itself — the explicit-argument pattern is the auditability guarantee.\n- Do **not** commit the key to any file, including `.env` examples or notebook outputs.\n\nVerify the `NVIDIA_API_KEY` actually works against Magpie TTS and Parakeet\u002FNemotron ASR before advancing. The four skills inline every recipe needed; this round-trip just confirms the API key + network path are real.\n\nThe agent harness loads the `NVIDIA_API_KEY` shell variable and passes it as an explicit function argument to the helpers below. The recipe code itself does not read environment variables — auditors can see exactly which API keys cross the wire.\n\n```python\nimport wave, tempfile\nimport riva.client\n\nNVCF_HOST = \"grpc.nvcf.nvidia.com:443\"\nMAGPIE_FUNCTION_ID    = \"877104f7-e885-42b9-8de8-f6e4c6303969\"   # Magpie TTS\nPARAKEET_FUNCTION_ID  = \"d3fe9151-442b-4204-a70d-5fcc597fd610\"   # Parakeet TDT 0.6B v2 (offline ASR)\n\ndef auth_for(function_id: str, api_key: str) -> riva.client.Auth:\n    return riva.client.Auth(\n        use_ssl=True, uri=NVCF_HOST,\n        metadata_args=[\n            [\"function-id\", function_id],\n            [\"authorization\", f\"Bearer {api_key}\"],\n        ],\n    )\n\ndef smoke_test(api_key: str) -> str:\n    \"\"\"Caller passes api_key (the harness reads $NVIDIA_API_KEY at the shell;\n    this code never touches the environment). Returns the ASR transcript.\"\"\"\n\n    # 1. TTS: \"The patient was prescribed cefazolin.\"\n    tts = riva.client.SpeechSynthesisService(auth_for(MAGPIE_FUNCTION_ID, api_key))\n    pcm = b\"\".join(c.audio for c in tts.synthesize_online(\n        text=\"The patient was prescribed cefazolin.\",\n        voice_name=\"Magpie-Multilingual.EN-US.Mia\",\n        language_code=\"en-US\", sample_rate_hz=16000,\n    ))\n    with tempfile.NamedTemporaryFile(suffix=\".wav\", delete=False) as f:\n        with wave.open(f, \"wb\") as w:\n            w.setnchannels(1); w.setsampwidth(2); w.setframerate(16000); w.writeframes(pcm)\n        wav_path = f.name\n\n    # 2. ASR: transcribe the WAV we just synthesized.\n    asr = riva.client.ASRService(auth_for(PARAKEET_FUNCTION_ID, api_key))\n    with open(wav_path, \"rb\") as f:\n        audio_bytes = f.read()\n    config = riva.client.RecognitionConfig(\n        encoding=riva.client.AudioEncoding.LINEAR_PCM,\n        sample_rate_hertz=16000, language_code=\"en-US\",\n        max_alternatives=1, enable_automatic_punctuation=True,\n    )\n    response = asr.offline_recognize(audio_bytes, config)\n    transcript = response.results[0].alternatives[0].transcript if response.results else \"\"\n    print(f\"TTS:  The patient was prescribed cefazolin.\")\n    print(f\"ASR:  {transcript}\")\n    return transcript\n\n# Invoke from the agent (api_key sourced by the harness, not by this code):\n# smoke_test(api_key=\"\u003CNVIDIA_API_KEY value>\")\n```\n\n**Run the smoke test — don't defer it.** This is the gate that proves Stages 2–4 can reach the hosted stack with the user's current key. \"I can run it later\" is not an acceptable completion of Stage 1; either invoke `smoke_test(api_key=…)` now or, if the user has explicitly opted out, log the deferral in your closing summary so they know what they're missing.\n\nIf the transcript matches the input within ~1 token, the hosted stack is reachable and the user can advance to Stage 2. If either call fails:\n\n- `401 Unauthorized` \u002F `PERMISSION_DENIED` → `NVIDIA_API_KEY` is wrong, expired, or not exported in this shell. Re-export and re-test.\n- `404` \u002F `INVALID_ARGUMENT: function not found` → the function ID is stale. Look up the current ID at \u003Chttps:\u002F\u002Fbuild.nvidia.com> and update the constant above.\n- `RESOURCE_EXHAUSTED` → NVCF rate limit. Retry after 30 seconds; this is normal under load.\n- Network\u002FTLS errors → corporate proxy or DNS issue. Test `curl https:\u002F\u002Fbuild.nvidia.com` first.\n\n### 1d. (Optional) Verify Merriam-Webster lookup\n\nTwo paths produce a `merriam-webster`-tagged manifest row in Stage 2. Pick one (or neither — Magpie G2P fall-through is a valid posture):\n\n- **Path A — JSON API + key.** Recommended for standalone use of this skill. Check the key is set:\n\n  ```bash\n  test -n \"$DICTIONARY_API_KEY\" && echo \"DICTIONARY_API_KEY len=${#DICTIONARY_API_KEY}\" \\\n    || echo \"DICTIONARY_API_KEY not set — Path A is off\"\n  ```\n\n  Free key issues instantly at \u003Chttps:\u002F\u002Fdictionaryapi.com>.\n\n- **Path B — HTML scraping.** No API key needed; reachability is the only prerequisite. Brittle to MW site HTML changes; recipe inlined in the build skill's `references\u002Fpronunciation-pipeline.md`.\n\n  ```bash\n  curl -fsS -o \u002Fdev\u002Fnull -w \"merriam-webster.com reachable, HTTP %{http_code}\\n\" \\\n    https:\u002F\u002Fwww.merriam-webster.com\u002Fmedical\u002Fcefazolin\n  ```\n\n  If you don't want to maintain a scraper, use Path A instead.\n\nRemember the data-disclosure note at the top: under either path, each clinical term in your seed list goes out as an HTTP request to a Merriam-Webster endpoint.\n\n## Examples\n\n**Fresh shell, never run before.** User says something like *\"I want to start the flywheel.\"* → Quote the disclosure table first, then walk through 1a → 1b → 1c in order. On a green smoke test, point them at `\u002Fdigital-health-clinical-asr-build` and explicitly name KER as the metric Stage 3 will judge them by.\n\n**Returning user, env already up.** User says *\"I already have the env, just confirm I'm good to go.\"* → Skip the venv + `pip install` (1b). Run only the length check (1a) and the smoke test (1c). On green, advance.\n\n## Artifacts produced\n\n- `NVIDIA_API_KEY` exported in the user's shell\n- An activated virtualenv with `nvidia-riva-client`, `pandas`, `soundfile`, `requests`\n- A confirmed TTS→ASR round-trip on a clinical sentence (proof the hosted stack works)\n\nNo manifest, audio, or model artifact is produced at this stage — those come at Stages 2–4.\n\n## Troubleshooting\n\n- **Length check shows nothing or `len=0`** → `NVIDIA_API_KEY` isn't exported in this shell. Run `export NVIDIA_API_KEY=nvapi-...` and re-check.\n- **Variable is set in one shell but not another** → exports don't persist across sessions. Add the `export` line to your shell rc (`~\u002F.bashrc`, `~\u002F.zshrc`), or use a per-directory loader like `direnv`.\n- **`401 Unauthorized` on the smoke test** → key value is wrong or expired. Re-issue at \u003Chttps:\u002F\u002Fbuild.nvidia.com>.\n- **`grpc.RpcError: function not found`** → the inlined function IDs need updating against the current NVCF catalog. Check \u003Chttps:\u002F\u002Fbuild.nvidia.com> and edit the constants in 1c. The eval skill (`\u002Fdigital-health-clinical-asr-eval`) provides a catalog of current function IDs in its Step 3a \"Other catalog options\" list.\n- **`StatusCode.INVALID_ARGUMENT` with `CUDA error: an illegal memory access was encountered`** → NVCF-side backend fault on this specific function ID (Triton\u002FPyTorch on NVCF, not your env). Either retry later or temporarily point at a different offline ASR NIM — Whisper Large v3 function-id `b702f636-f60c-4a3d-a6f4-f3568c13bd7d` is the closest drop-in (also offline; pass `language_code=\"en\"` instead of `\"en-US\"`). For routine eval cycles, prefer to wait for the Parakeet backend to recover so Stage 3 baseline and Stage 4 SFT base stay aligned.\n- **`TypeError: Auth.__init__() got an unexpected keyword argument 'ssl_cert'`** → you're on `nvidia-riva-client >= 2.x` where the kwarg was renamed to `ssl_root_cert` (and is no longer needed for hosted NVCF). Drop the `ssl_cert=None,` line from your local copy of the recipe.\n- **`ModuleNotFoundError: riva.client`** → step 1b was skipped or the venv isn't activated. `source .venv\u002Fbin\u002Factivate && pip install nvidia-riva-client`.\n\n## Limitations\n\n- **Scope is environment readiness only.** Whether the user's term list or pronunciation overrides make sense is decided in `\u002Fdigital-health-clinical-asr-build`, not here.\n- **Magpie en-US assumption.** Downstream IPA validation rides on Magpie's English phoneme inventory; other locales require a different phoneme set entirely.\n- **Hosted NVCF is the assumed deployment.** Running self-hosted Riva NIMs is possible but the setup for that lives inside `\u002Fdigital-health-clinical-asr-finetune` Stage 4d.\n- **Synthetic data only.** This skill family is built for benchmarks generated from a curated term list. Real patient transcripts and recorded audio must not flow through any stage.\n\n## Next steps\n\n**Mandatory close on success:** finish the Stage 1 response by **pointing the user explicitly to `\u002Fdigital-health-clinical-asr-build`** and **naming KER (keyword error rate) as the headline measure** they'll see at Stage 3. Both pointers are required, not optional — they place the user inside the four-stage flywheel.\n\n- **Default forward route:** `\u002Fdigital-health-clinical-asr-build` — specialty interview, term curation, IPA tagging, NeMo manifest synthesis.\n- **Direct jump to Stage 3** (only when the user is bringing their own NeMo-format manifest with `term` \u002F `entity_category` \u002F `ipa_source` fields): `\u002Fdigital-health-clinical-asr-eval`.\n\n## References\n\n- [`references\u002Fdependency-ownership.md`](references\u002Fdependency-ownership.md) — boundary between skill-owned and companion-owned responsibilities.\n\n",{"name":5,"tags":24,"tools":29,"author":34,"license":15,"version":35,"metadata":36,"description":7,"compatibility":42},[25,26,27,28],"clinical-asr","setup","flywheel","bootstrap",[30,31,32,33],"Read","Write","Bash","Skill","Ben Randoing \u003Cbrandoing@nvidia.com>","1.1.0",{"tags":37,"team":38,"stage":39,"author":34,"domain":40,"next_skill":41},[25,27,26,28],"healthcare-tme",1,"ai-ml","digital-health-clinical-asr-build","NVIDIA_API_KEY (required) for hosted Magpie TTS + Parakeet\u002FNemotron ASR via NVCF. DICTIONARY_API_KEY (optional) for Merriam-Webster pronunciation lookup. NGC_API_KEY (optional) for Stage 4 fine-tune. Python 3.10+.","main","ffa016d3c9a8d32821f71f6d9d916c30e04fcb67","讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002Fdigital-health-skills\u002Frepo-docs\u002Fskills\u002Fdigital-health-clinical-asr-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":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add leemiracle\u002Fwork4ai --skill digital-health-clinical-asr-setup",{"tool":57,"command":58},"bunx","bunx skills add leemiracle\u002Fwork4ai --skill digital-health-clinical-asr-setup",{"tool":60,"command":61},"pnpm","pnpm dlx skills add leemiracle\u002Fwork4ai --skill digital-health-clinical-asr-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002Fdigital-health-skills\u002Frepo-docs\u002Fskills\u002Fdigital-health-clinical-asr-setup\u002FSKILL.md",true,[65,71,75],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"BENCHMARK.md","REFERENCE","参考文档",2845,"https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002Fdigital-health-skills\u002Frepo-docs\u002Fskills\u002Fdigital-health-clinical-asr-setup\u002FBENCHMARK.md",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fdependency-ownership.md",5827,"https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002Fdigital-health-skills\u002Frepo-docs\u002Fskills\u002Fdigital-health-clinical-asr-setup\u002Freferences\u002Fdependency-ownership.md",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"skill-card.md",2809,"https:\u002F\u002Fgithub.com\u002Fleemiracle\u002Fwork4ai\u002Fblob\u002Fmain\u002F讲透宇宙\u002F05-侦\u002F讲透NVIDIA\u002Fdigital-health-skills\u002Frepo-docs\u002Fskills\u002Fdigital-health-clinical-asr-setup\u002Fskill-card.md",[80,87,94,101,108,115],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"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",[],[]]