- name
|
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nexu-io/open-design --skill clinical-case-report -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nexu-io/open-design --skill clinical-case-report -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nexu-io/open-design --skill clinical-case-report -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nexu-io/open-design --skill clinical-case-report -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/nexu-io/open-design/tree/HEAD/design-templates/clinical-case-reportFrom the publisher
Generate a structured medical case presentation for clinical rounds, conferences, or documentation. The output follows standard medical formatting conventions used in hospital settings worldwide.
A single-page HTML case report (index.html). Content varies by format
(see references/case-formats.md — selected in Step 0):
SOAP / Conference format:
Brief Rounds format (daily review, ward round, handover, ICU, post-call):
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 artifactRead the user's prompt and extract:
If the chief complaint or presenting problem is missing:
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:
If the user has not provided specific values, generate values that are internally consistent with the diagnosis:
Consistency checks (typical patterns):
Critical rule — preserve user-provided data:
The assessment section must contain:
The plan must be:
If you are uncertain about a specific dose, write "[drug name] — dose per local formulary/protocol" rather than inventing a dose.
Generated plans must:
index.htmlRequirements for the HTML output:
<table> elementsdata-od-id for comment-mode targeting:<section data-od-id="hpi">...</section>
<section data-od-id="vitals">...</section>
<section data-od-id="pmh">...</section>
<section data-od-id="examination">...</section>
<section data-od-id="investigations">...</section>
<section data-od-id="assessment">...</section>
<section data-od-id="plan">...</section>
references/checklist.mdBefore emitting <artifact>, run every P0 item in references/checklist.md.
All P0 items must pass. Fix any failures before emitting.
© 2026 Skills Rack.
---name: clinical-case-reportdescription: |---# design-templates/clinical-case-report/SKILL.mdFAQ
Download design-templates/clinical-case-report/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/nexu-io/open-design.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.