agentleFS
NVIDIAKnown publisherNVIDIA/dgx-spark-playbooks/nvidia/station-healthcare-agent/assets/skills/clinical-delegation/SKILL.md

clinical-delegation

Skill1.5k starsChanged 2 months agoApache-2.0View on GitHub

How to delegate clinical tasks to specialist agents. Always use sub-agent runtime with explicit agentId — never ACP. Never call FHIR via web_fetch.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 48 mentionsNov 2026: 2 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the NVIDIA/dgx-spark-playbooks repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about NVIDIA/dgx-spark-playbooks

The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 50

Talked about on GitHub (50 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When you delegate work to specialist agents, you must use the sub-agent runtime, not ACP.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Clinical delegation (sessions_spawn)

When you delegate work to specialist agents, you must use the sub-agent runtime, not ACP.

Do not call FHIR yourself

Do not use web_fetch or any HTTP tool to call FHIR APIs from the coordinator. The coordinator does not have the correct FHIR base URL in context when it invents URLs. Specialist agents (patient-data, labs-vitals, medications, analyst) have the configured FHIR endpoint and write Python that runs on the server.

  • For "find patient", "first patient", "list conditions", "demographics" → sessions_spawn with agentId: "patient-data"
  • For labs, vitals, BP, observations → agentId: "labs-vitals"
  • For medications → agentId: "medications"
  • For analysis, care gaps, charts → agentId: "analyst"

The only FHIR server in use is https://r4.smarthealthit.org. Never use placeholder domains like fhir.example.com.

Rule

Use sessions_spawn with:

  • agentId — set to the specialist agent id: patient-data, labs-vitals, medications, analyst, or molecular
  • task — clear description of the task
  • Do not set runtime: "acp". Omit runtime or use runtime: "subagent" so the request goes to the correct clinical agent.

Correct examples

{ "agentId": "patient-data", "task": "Find the first patient and return demographics and active conditions.", "mode": "run" }
{ "agentId": "labs-vitals", "task": "Get latest HbA1c and eGFR for patient abc123", "mode": "run" }
{ "agentId": "analyst", "task": "Run care gap analysis for diabetic patients with A1c > 9%", "mode": "run" }

Wrong

  • Using web_fetch to call FHIR (e.g. https://fhir.example.com/Patient) — coordinator must delegate instead; fhir.example.com is not a real server and will fail.
  • "runtime": "acp" without agentId — causes "ACP target agent is not configured"
  • Omitting agentId when delegating — the system will not know which specialist to run

Specialist agents

agentIdUse for
patient-dataFind patients, get demographics, list conditions
labs-vitalsLabs, vitals, BP, observations
medicationsActive medications, drug classes
analystPython analysis, care gaps, charts
molecularDrug molecular structure, OpenFold3 NIM 3D visualization

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.