plugins/pm-research/skills/patient-communication/SKILL.md
Write clear, plain-English patient communications for any healthcare context. Use when asked to write a patient letter, patient information leaflet, appointment letter, test-results letter, discharge summary for patients, or health education content. Produces an accessible patient communication at an appropriate reading level with clear next steps.
npx skillsauth add mohitagw15856/pm-claude-skills patient-communicationInstall 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.
Writes patient-facing healthcare communications in plain, accessible language — targeting UK Grade 6 / US Grade 8 reading level.
WARNING: All patient communications must be reviewed and approved by a qualified healthcare professional before sending. This skill produces drafts only.
[Date]
Dear [Patient name],
Re: [Clear subject line in bold]
[Opening paragraph: State clearly what this letter is about. No preamble.]
[Main content — short paragraphs, 2-3 sentences each. Bullet points for instructions. Bold anything the patient must do or remember.]
What happens next:
If you have questions: Contact us at [phone] between [hours] or email [address].
If you feel unwell before your appointment, please [specific instruction].
Yours sincerely, [Name, Title, Department]
[Plain language title]
What is [topic]? [2-3 plain English sentences. Explain technical terms immediately.]
Why has this been recommended for me? [Personalised clinical reason in patient terms]
What will happen? [Numbered step by step]
What are the benefits? [Honest statement]
What are the risks? [Common first, then rare but serious. Use frequencies: "About 1 in 10 people..." not "10% incidence"]
What should I do to prepare? [Specific instructions]
When should I contact someone? [Specific signs — not vague. "Temperature above 38C" not "if you feel unwell"]
Your [test name] results — [Normal / Abnormal] — stated in the FIRST sentence, never paragraph 3.
[What this means in plain English]
What happens next: [Clear next steps. If no action, say so explicitly.]
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.