How do I install the Fhir Project Doctor skill?

Run npx skillmds@latest add sigistry/fhir-project-doctor in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Fhir Project Doctor safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Fhir Project Doctor?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Fhir Project Doctor free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Fhir Project Doctor?

sigistry (@sigistry) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Fhir Project Doctor by sigistry — Agent Skill

Name: Fhir Project Doctor
Author: sigistry

Fhir Project Doctor

Inspect an HL7 FHIR, FSH/SUSHI, or Implementation Guide project for validator runtimes, FHIR package dependencies, cache state, version signals, privacy gates, and setup blockers. Use when FHIR validation cannot start, profiles or packages are missing, IG Publisher/Firely/HAPI/Records availability is unclear, or the user asks to diagnose or prepare a FHIR conformance project.

sigistry Updated Sep 17, 2026

File contents

FHIR Project Doctor

Diagnose the project before changing resources or installing tooling. Do not validate or repair clinical content unless the user separately asks for $fhir-validation.

Bundled paths

Resolve <skill-root> to the directory containing this SKILL.md and <plugin-root> two directories above it. Shared deterministic tools live under <plugin-root>/skills/fhir-validation/scripts. Never resolve them relative to the user's workspace.

Workflow

Run the detector, runtime planner, and package doctor:

node "<plugin-root>/skills/fhir-validation/scripts/detect-fhir-project.mjs" <target>
node "<plugin-root>/skills/fhir-validation/scripts/plan-runtime.mjs" <target>
node "<plugin-root>/skills/fhir-validation/scripts/doctor-packages.mjs" <target>

Separate findings into project signals, runtime availability, FHIR-version compatibility, missing packages, and actions requiring consent.
Prefer already configured local tools. Do not install tools, download packages, contact terminology services, or access FHIR URLs without explicit consent.
Treat missing declared packages and mixed/unsupported FHIR versions as blockers for claims of profile-aware validation.
Recommend the smallest next action. Do not claim that structural fallback proves profile, invariant, terminology, canonical, or cross-document-reference conformance.

Output

Report the selected runtime, privacy boundary, detected FHIR version(s), validation depth available, package blockers, and ordered next actions. Preserve the tools' schemaVersion, tool, mode, capabilities, warnings, and nextActions fields when summarizing.

---name: fhir-project-doctordescription: Inspect an HL7 FHIR, FSH/SUSHI, or Implementation Guide project for validator runtimes, FHIR package dependencies, cache state, version signals, privacy gates, and setup blockers. Use when FHIR validation cannot start, profiles or packages are missing, IG Publisher/Firely/HAPI/Records availability is unclear, or the user asks to diagnose or prepare a FHIR conformance project.---# FHIR Project DoctorDiagnose the project before changing resources or installing tooling. Do not validate or repair clinical content unless the user separately asks for `$fhir-validation`.## Bundled pathsResolve `<skill-root>` to the directory containing this `SKILL.md` and `<plugin-root>` two directories above it. Shared deterministic tools live under `<plugin-root>/skills/fhir-validation/scripts`. Never resolve them relative to the user's workspace.## Workflow1. Run the detector, runtime planner, and package doctor: ```bash node "<plugin-root>/skills/fhir-validation/scripts/detect-fhir-project.mjs" <target> node "<plugin-root>/skills/fhir-validation/scripts/plan-runtime.mjs" <target> node "<plugin-root>/skills/fhir-validation/scripts/doctor-packages.mjs" <target> ```2. Separate findings into project signals, runtime availability, FHIR-version compatibility, missing packages, and actions requiring consent.3. Prefer already configured local tools. Do not install tools, download packages, contact terminology services, or access FHIR URLs without explicit consent.4. Treat missing declared packages and mixed/unsupported FHIR versions as blockers for claims of profile-aware validation.5. Recommend the smallest next action. Do not claim that structural fallback proves profile, invariant, terminology, canonical, or cross-document-reference conformance.## OutputReport the selected runtime, privacy boundary, detected FHIR version(s), validation depth available, package blockers, and ordered next actions. Preserve the tools' `schemaVersion`, `tool`, `mode`, `capabilities`, `warnings`, and `nextActions` fields when summarizing.

Frequently asked questions