clinical-case-report
Makes your agent create detailed medical reports. It organizes patient information in a clear format for doctors.
What it does
Generates a structured medical report about a patient's case. It can be in SOAP format (Subjective, Objective, Assessment, Plan) or a summary for quick hospital discussions.
When to use it
- ✓To present a case during medical rounds.
- ✓To create a patient summary for conferences.
- ✓To document a clinical case in an organized manner.
Example of what to ask your AI
“Create a SOAP report for a 65-year-old male patient presenting to the ER with chest pain.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
The AI organizes patient information, such as history, exams, and diagnoses, into a standard format used by doctors. It ensures that data, like vital signs, is consistent with the clinical picture.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add nexu-io/open-design --skill clinical-case-reportOr download just the file:
curl -L https://raw.githubusercontent.com/nexu-io/open-design/main/design-templates/clinical-case-report/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
Clinical Case Report Skill
Generate a structured medical case presentation for clinical rounds, conferences, or documentation. The output follows standard medical formatting conventions used in hospital settings worldwide.
What you will produce
A single-page HTML case report (index.html). Content varies by format
(see references/case-formats.md — selected in Step 0):
SOAP / Conference format:
- Patient identification — age, sex, chief complaint
- History of Present Illness (HPI) — chronological narrative with pertinent positives and negatives
- Past Medical History, Medications, Allergies
- Review of Systems
- Physical Examination — systematic findings by system
- Vital Signs — formatted table with reference ranges and flags
- Investigations — laboratory results and imaging findings
- Assessment — primary diagnosis and differential (3–5 items) with clinical reasoning for each
- Management Plan — evidence-based, organised by problem
Brief Rounds format (daily review, ward round, handover, ICU, post-call):
- ID line — age, sex, day of admission, primary problem
- Interval events / current status — what has changed since last review
- Active problems — numbered list
- Plan-by-problem — concise actions for each active problem
- Full HPI and systematic physical examination are not included
Step-by-step workflow
Step 0 — Load reference files
Before starting, read both reference files:
references/case-formats.md— use this to choose the correct output format (SOAP, Conference, or Brief Rounds) based on the user's contextreferences/checklist.md— keep P0 gates in mind throughout; you must pass all P0 items before emitting the final artifact
Step 1 — Parse the brief
Read the user's prompt and extract:
- Patient age and sex
- Chief complaint or presenting problem
- Any vitals, labs, or imaging the user has provided
- Clinical context: ED, ward rounds, conference case, outpatient, etc.
- Specialty context: cardiology, emergency, internal medicine, etc.
If the chief complaint or presenting problem is missing:
- SOAP / Conference: ask one clarifying question before proceeding. Do not proceed without it.
- Brief Rounds: if the admission problem or ID line is already available (e.g. "day-3 ICU review for septic shock"), proceed directly — a separate chief complaint is not required.
Step 2 — Build the clinical narrative
For SOAP / Conference outputs: write the HPI as a continuous prose narrative in standard clinical style:
"This is a [age]-year-old [sex] with a history of [relevant PMH] who presents with [chief complaint]. Symptoms began [timeline] and are characterised by [quality, severity, radiation]. Associated symptoms include [list]. Pertinent negatives include [list]."
The HPI must be chronological. Include timeline markers ("2 hours prior to presentation", "onset yesterday morning").
For Brief Rounds outputs (daily review, ward round, handover, ICU, post-call): skip the full HPI and examination. Instead produce:
- ID line: "[Age][sex], Day [N] of admission, [primary problem]"
- Interval events / current status: what has changed since last review
- Active problems: numbered list
- Plan-by-problem: concise action for each active problem
Step 3 — Generate physiologically consistent clinical data
If the user has not provided specific values, generate values that are internally consistent with the diagnosis:
Consistency checks (typical patterns):
- A patient in shock typically has: HR >100, SBP <90, raised lactate, impaired capillary refill — but medications (beta-blockers), age, or shock type (neurogenic, spinal) can alter this pattern
- Pneumonia typically presents with raised WBC, raised CRP, temperature >38°C — but afebrile pneumonia exists, especially in the elderly or immunocompromised
- A STEMI typically shows ST elevation in contiguous leads and raised high-sensitivity troponin — but early presentations may have initially normal troponin; CK-MB is not universally required
- Sepsis typically shows raised or low WBC, raised lactate >2, temperature abnormality — but compensated early sepsis may present with normal vitals
- Lab units must match convention: creatinine in µmol/L or mg/dL (state which), glucose in mmol/L, haemoglobin in g/dL
Critical rule — preserve user-provided data:
…
FAQ
What's the difference between SOAP format and the brief rounds format?
The SOAP format is more detailed, including a full history and physical exam. The brief rounds format is more concise, focusing on the current status and active problems.
Does the AI invent medical information?
The AI uses the information you provide. If data is missing, it may generate clinically sensible values, but it always preserves the data you've already given.
What does 'physiologically consistent' mean?
It means that the generated data (like heart rate or lab results) is compatible with the described medical condition of the patient.
Details
Original description by the author
Structured medical case presentation for clinical rounds, conferences, and documentation. Generates SOAP-format or narrative case reports with physiologically accurate vitals, labs, and evidence-based plans. Use when the brief mentions "case report", "case presentation", "SOAP note", "clinical case", "ward rounds", "case summary", or "patient presentation".
repo: nexu-io/open-design
Popularity
- GitHub stars
- 101k
- Ranking position
- #406
- License
- Apache-2.0
- Updated
- 10/16/2026
Comments
- …
More skills from this repository
sample-plugin
Makes your agent create a metadata file for tests. It helps ensure code works correctly in different situations.
nexu-io/open-design
aster-atelier
Helps your agent create an artistic website with a classic look. It uses elegant imagery, blue skies, and serif fonts for a cinematic feel.
nexu-io/open-design
audio-jingle
Makes your agent generate audio like jingles and sound effects. It can create music and voices, saving the result as an audio file.
nexu-io/open-design
blog-post
Helps your agent write long articles or blog posts. It includes space for images, quotes, and author information.
nexu-io/open-design
Similar skills
intent-driven-development
Helps your agent turn ideas into clear, testable plans. Defines criteria to ensure changes are made correctly and safely.
affaan-m/ECC
product-capability
Guides your agent in turning product ideas into clear plans. It defines what needs to be done, the limits, and decisions before development.
affaan-m/ECC
article-writing
Writes long-form content like articles, guides, and blog posts with a unique style. It's useful when you need well-written texts with a consistent voice and credibility.
affaan-m/ECC