plugins/pm-health/skills/soap-note/SKILL.md
Structure a clinical encounter into a clean SOAP note. Use when asked to write a SOAP note, document a patient encounter, turn visit notes into clinical documentation, or structure subjective/objective/assessment/plan. Produces a well-organised SOAP note — Subjective, Objective, Assessment (with differential), and Plan — from the provided encounter details, in standard clinical-documentation style.
npx skillsauth add mohitagw15856/pm-claude-skills soap-noteInstall 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.
Good clinical documentation is structured so the next clinician can reconstruct the reasoning in seconds: what the patient reported, what was found, what you think, and what you'll do. This skill turns encounter notes into a clean SOAP note that follows that structure and keeps assessment separate from plan.
Clinical-safety note: this is a documentation-formatting aid, not medical advice or a diagnosis. It organises information a qualified clinician provides; all content must be reviewed and verified by the treating clinician before entering the medical record. Do not invent clinical findings, vitals, or results.
Given rough encounter notes, produce the full structured note anyway — organise what's given into the four sections and place each detail correctly. Where a standard field wasn't provided, leave it clearly marked (e.g. "Vitals: not documented") rather than inventing a value. Never fabricate findings, labs, or measurements.
Ask for these only if they aren't already provided (else mark as not documented):
S — Subjective
O — Objective
A — Assessment
P — Plan
End with a note of any fields not documented and a reminder that the treating clinician must verify before filing.
Clinical documentation practice — the SOAP (Subjective, Objective, Assessment, Plan) format for structured, reviewable encounter notes.
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.