Agent skill · NVIDIA
digital-health-clinical-asr-build
Stage 2 of the Clinical ASR Flywheel. Use when curating clinical terms, tagging IPA, and synthesizing a NeMo manifest. NOT for scoring (use /digital-health-clinical-asr-eval).
What it needs
About 11k tokens when loaded.
What this skill does
<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. SPDX-License-Identifier: Apache-2.0 --> Clinical ASR Flywheel — Stage 2 (Build the benchmark) ⚠ Agent: read this entire SKILL.md before answering. This stage is conversational and gated. Specifically: ask the user 1–2 specialty-aware clarifying questions before proposing terms (Step 2a), walk them through the two-tier IPA pipeline (override → merriam-webster → magpieg2p) in Step 2c, hit the explicit QA-mode audition gate in Step 2d before full Cartesian synthesis, and name KER as the headline metric they'll see in Stage 3. Skipping any of these defeats the methodology. You are the curate-and-synthesize stage. The user arrives from /digital-health-clinical-asr-setup and leaves with a NeMo-format manifest.jsonl plus the audio it references — both ready for scoring at /digital-health-clinical-asr-eval. Be conversational. This is the warmest, most domain-aware step in the flywheel: you're asking a clinician (or someone who works with them) which terms hurt today and shaping a benchmark around their reality. Ask short, focused questions. Show the user what's being added. Don't lecture. Data leaves your environment — disclose this to the user before any term is sent This stage transmits user-curated content to two external services. Surface this to the user before invoking either call: Service What gets sent When --- --- --- Merriam-Webster (dictionaryapi.com API or merriam-webster.com public site) One HTTP request per term in the seed list — term goes in URL path Step 2c — see MW path bullets below NVIDIA NVCF Magpie TTS (grpc.nvcf.nvidia.com) Each generated clinical sentence (text, plus any SSML IPA wrappers) Steps 2d and 2e, every synthesis call Both endpoints expect non-PHI synthetic content — the term list you curate, the sentences /data-designer (or your fallback templates) generates from it. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills NVIDIA/digital-health-clinical-asr-build