clinical-case-summary
$
npx mdskill add mohitagw15856/pm-claude-skills/clinical-case-summaryProduces structured clinical case summaries for educational, documentation, and handover purposes.
SKILL.md
.github/skills/clinical-case-summaryView on GitHub ↗
--- name: clinical-case-summary description: "Write a structured clinical case summary or case presentation. Use when asked to write a clinical case summary, case presentation, patient case report, or clinical handover. Produces a structured summary using SBAR or SOAP format. For educational and documentation purposes only — not a substitute for clinical judgement." --- # Clinical Case Summary Skill Produces structured clinical case summaries for educational, documentation, and handover purposes. WARNING: For documentation and educational purposes only. All clinical content must be reviewed by a qualified healthcare professional. This is not clinical advice. ## Required Inputs - **Purpose** (case presentation / handover / case report / educational / MDT summary) - **Patient details** (anonymised — age, sex, relevant background) - **Presenting complaint and history** - **Examination findings** - **Investigations and results** - **Diagnosis or differential diagnoses** - **Management and treatment** - **Outcome** (if known) - **Format preference** (SBAR / SOAP / Standard clinical / Narrative) --- ## Format A: SBAR (Handover / Referral) **S — Situation** [Patient identifier anonymised, location, reason for contact in one sentence] **B — Background** - Age / sex / relevant past medical history - Current admission details - Relevant medications and allergies - Brief relevant social history **A — Assessment** - Current clinical status - Vital signs if relevant - Key examination findings - Working diagnosis or differential - Recent investigations and results **R — Recommendation** - What you need from the recipient - Urgency level - Immediate actions already taken - Questions or concerns --- ## Format B: SOAP Note **S — Subjective** [Presenting complaint in patient words. Symptom history: onset, duration, character, severity, associated symptoms, relieving/aggravating factors] **O — Objective** - Vital signs: [BP, HR, RR, Temp, O2 sats] - Examination: [Systematic findings] - Investigations: [Results with reference ranges] **A — Assessment** - Primary diagnosis: [With brief rationale] - Differential diagnoses: [Ranked with reasoning] **P — Plan** - Immediate management - Investigations ordered - Treatments initiated with dose, route, frequency - Referrals - Safety netting: what to watch for, when to escalate - Follow-up plan ## Quality Checks - Patient details fully anonymised - Allergies and medications included in handover formats - Safety netting included in SOAP plan - Disclaimer included ## Example Trigger Phrases - "Write a clinical handover using SBAR for this patient" - "Summarise this case in SOAP format" - "Write a case report for [clinical scenario]" - "Prepare an MDT summary for this patient"
More from mohitagw15856/pm-claude-skills
- 360-feedback-templateDesign a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
- ab-test-plannerDesign statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
- accessibility-auditGenerate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
- account-planBuild a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.
- aeo-optimizerOptimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.
- ai-ethics-reviewConduct an ethical review of an AI or ML feature, model, or product. Use when asked to run an AI ethics review, assess AI risks, audit a model for bias, or produce an AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with prioritised mitigations.
- ai-product-canvasStructure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
- ambiguity-resolverStructure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.
- api-docs-writerWrite clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.
- api-versioning-strategyWrite an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.