Individual skill
clinical-summary
Produces structured, faithful clinical summaries - either a patient-record summary with strict chronology, medication reconciliation, and expanded abbreviations, or a clinical-study summary with effect sizes, absolute risks, harms, and limitations. Use when someone asks "summarize this patient chart", "turn these notes into a discharge-style summary", "summarize this RCT for journal club", or "what did this trial actually show". This is clinical documentation support, not medical advice or diagnosis. Do NOT use for explaining lab results to a patient - use bloodwork-explainer instead; for synthesizing many studies into one evidence review, use systematic-review.
skills/clinical-summary/SKILL.md
Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 24
- Repository last updated
- Oct 13, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude Repository topic
- claude-skills Repository topic
- skill-me Repository topic
- docs Derived category
- productivity Derived category
- productivity-notes Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Clinical Summary
A clinical summary gets acted on by people who trust it, so the costly failure is not vagueness - it is confident distortion: a scrambled timeline, a dropped medication, an overstated trial result. Faithfulness to the source is paramount; never state more certainty than the documents support, and never fill a gap with a plausible guess. This skill produces two artifact types with one discipline: patient-record summaries and clinical-study summaries.
**Boundary, stated up front:** this is clinical documentation support - organizing and restating what the source material says. It is not medical advice, not diagnosis, and not treatment recommendation. Never suggest a diagnosis the records do not contain, never recommend starting, stopping, or dosing a medication, and always defer care decisions to the treating clinician.
## Inputs to collect
1. **Mode** - patient-record summary or study summary. If the source is a chart, notes, or discharge paperwork, it is Path A; if a paper or trial report, Path B.
2. **Audience** - clinician, care coordinator, reviewer, or the patient's own file. Default: clinician-facing.
3. **Source documents** - everything available. Note explicitly which document types are missing (no med list, no imaging reports), because gaps change the summary's reliability.
4. **Purpose** - handoff, chart review, journal club, appraisal. Purpose sets length and emphasis.
Label every inference as an inference ("dose change appears to follow the elevated creatinine on [date], though no note states the reason").