How to use the Clinical Case Report Writer agent skill

What is an agent skill, and what does this one do?

An agent skill is a folder containing a SKILL.md file and supporting reference files. When installed, the agent reads these instructions and follows them for matching requests. This skill is named clinical-case-report and is licensed under Apache-2.0.

Once loaded, the agent picks an output format based on your context. The SOAP / Conference format includes patient identification, history of present illness, past history, medications and allergies, review of systems, examination, a vital signs table, investigations, an assessment with a differential of 3 to 5 items, and a management plan organised by problem. The Brief Rounds format is shorter and covers an ID line, interval events, active problems and a plan for each problem.

• Output is a single-page HTML file named index.html, designed to print on white paper.
• If the chief complaint is missing in SOAP or Conference format, the agent asks one clarifying question before continuing.
• If you do not supply vitals or labs, the agent generates values that fit the diagnosis.
• Values you provide are kept as written, and atypical findings are noted in the assessment.

How do you install the clinical-case-report skill?

Download the ZIP file from this page and unzip it. You can install it in one of two places. For a personal install available across projects, unzip it into ~/.claude/skills/. For a single project, unzip it into that project's .claude/skills/ folder.

In the Claude apps, you can instead upload the skill under Settings → Capabilities → Skills.

• Personal install: ~/.claude/skills/
• Project install: .claude/skills/ inside your project folder
• Claude apps: Settings → Capabilities → Skills, then upload the skill

What files are in the skill?

The skill contains five files. SKILL.md holds the main instructions and workflow. The references folder holds case-formats.md, which describes the SOAP, Conference and Brief Rounds formats, and checklist.md, a quality checklist the agent works through before it finishes. Two examples show the expected output: example.html and examples/example-stemi.html, which is a STEMI case.

• SKILL.md: main instructions
• references/case-formats.md: output format choices
• references/checklist.md: quality checklist
• example.html: sample output
• examples/example-stemi.html: sample STEMI case

How do you trigger the skill with a natural request?

You do not need special syntax. Describe the patient and use the kind of wording a clinician or educator would use. The skill responds to phrases such as case report, case presentation, SOAP note, clinical case, ward rounds, patient presentation, case summary and medical case.

Give the agent the age, sex, main complaint and any findings you already have. The more specific you are, the less the agent has to fill in. The skill's own example prompt is a 58-year-old male with 2 hours of substernal chest pain radiating to the left arm, diaphoresis, and ST elevation in leads II, III, aVF, asking for a full emergency cardiology case presentation.

• "Write a SOAP note for a 58-year-old man with 2 hours of chest pain radiating to the left arm and ST elevation in II, III and aVF."
• "Make a ward-round summary for day 3 of ICU admission for septic shock."
• "Create a teaching case presentation on community-acquired pneumonia in an elderly patient for my students."

What do you need before you start?

The source lists no required software or packages. The skill does not run scripts and does not use the network. A brief with a patient age, sex and chief complaint gives the best result. For SOAP and Conference outputs, the chief complaint or presenting problem is needed. Brief Rounds outputs can proceed from an admission problem alone.

• Requires: nothing listed in the source
• Runs scripts: no
• Uses network: no

What safety limits should you know about?

The output looks like hospital documentation, but it is generated text and is not a real patient record. Vitals, labs and drug doses are not checked against real data. The skill tells the agent to write specific doses, so any dose must be verified against current local formularies before anyone relies on it. The skill also has no privacy or de-identification safeguards, so do not enter real patient identifiers.

The skill asks the agent to mark each output as educational or simulated and to include a disclaimer footer. Treat it as a teaching and prototyping tool, not clinical decision support.

• Do not use output for real patient care or real documentation.
• Do not use it to look up actual drug dosing.
• Do not enter real patient identifiers.
• Check every drug dose against your local formulary or protocol.

What tips help you get better output?

Provide the values you already know, because the agent keeps user-supplied data rather than replacing it. State the setting (ED, ward, conference, clinic) so the right format is chosen. Name the specialty, such as cardiology or internal medicine. Ask for a specific format if you need one, for example Brief Rounds for a handover.

• State any known vitals and labs; they are preserved.
• Name the setting and specialty.
• Say "Brief Rounds" or "Conference" if you want a particular format.
• Review the disclaimer footer before sharing any output.