plugins/pm-health/skills/discharge-summary/SKILL.md
Turn a hospital stay into a complete, well-structured discharge summary. Use when asked to write a discharge summary, a hospital discharge note, or to document a patient's admission-to-discharge course for handoff. Produces a standard discharge summary — admission reason, hospital course, diagnoses, procedures, discharge medications, condition, and follow-up/return precautions — from the provided details.
npx skillsauth add mohitagw15856/pm-claude-skills discharge-summaryInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
The discharge summary is the handoff that the next clinician (and the patient) actually relies on: why they were admitted, what happened, what changed, and what to do next. This skill structures the stay into a complete, scannable summary so nothing critical — a new medication, a pending result, a follow-up — falls through the gap.
Clinical-safety note: this is a documentation-formatting aid, not medical advice. It organises information a qualified clinician provides; the treating clinician must review and verify every detail (especially the medication list and follow-up) before it is finalised. Do not invent diagnoses, medications, doses, or results.
Given the admission notes and course, produce the full summary anyway — organise what's provided into every standard section. Where a section's detail wasn't given, mark it clearly (e.g. "Pending results: none reported") rather than inventing it. Never fabricate medications, doses, or diagnoses.
Ask for these only if they aren't already provided (else mark as not documented):
Close with fields not documented and a clinician-review reminder.
Clinical handoff/documentation practice — structured discharge summaries with medication reconciliation, explicit follow-up, and return precautions.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.