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. Targets accessible 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.]
development
Analyse competitor moves and translate them into strategic implications for your product roadmap. Use when a competitor announces a new feature, pricing change, partnership, or strategic shift, or when producing a periodic competitive intelligence report. Produces a categorised signal analysis with reactive-vs-proactive assessment, threat ratings, specific roadmap implications, and recommended responses with owners.
development
Build a community management playbook for a brand's social media channels. Use when asked to create guidelines for managing comments, DMs, and community interactions, define a moderation policy, or build response frameworks for social media community managers. Produces a complete playbook with response templates, escalation paths, moderation rules, and tone guidelines.
development
Activate a 4-stage coding discipline framework that forces Claude to plan before coding, isolate changes on a branch, write tests first, and self-review output twice before presenting it. Use when starting a complex coding task, when past Claude sessions produced broken first drafts, or when you want to prevent rework cycles. Produces a confirmed written plan, isolated feature branch, test-first implementation, and a double-reviewed output with a correctness and code-quality checklist.
development
Optimize 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.