Write clear, plain-English patient communications for any
Patient Communication Skill

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…
--- name: patient-communication description: "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." --- # Patient Communication Skill 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. ## Required Inputs - **Communication type** (appointment letter / results letter / discharge info / patient leaflet / consent info / health education) - **Clinical context** - **Key messages** (what the patient must understand and do) - **Tone** (reassuring / informative / urgent) - **Specific instructions or next steps** - **Contact details for queries**
Overview
Writes patient-facing healthcare communications in plain, accessible language — targeting UK Grade 6 / US Grade 8 reading level.
Manual install (npx, ZIP)
npx skills add mohitagw15856/pm-claude-skills --skill patient-communication -g -a claude-codemkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/mohitagw15856/pm-claude-skills/tar.gz/f6ca79348c55 \
| tar -xz -C ~/.claude/skills --strip-components=2 pm-claude-skills-f6ca79348c55/skills/patient-communicationNew-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/7c8784531edc8e0e9368/patient-communication.zip" -OutFile "$env:TEMP\patient-communication.zip"; Expand-Archive "$env:TEMP\patient-communication.zip" -DestinationPath "$HOME\.claude\skills" -ForceConnects with Agent Alley MCP · agentalley.io/mcp
Files included
SKILL.md4.0 KB
Read the files here
mohitagw15856/
Show the full text107 lines
Patient Communication Skill
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.
Required Inputs
- Communication type (appointment letter / results letter / discharge info / patient leaflet / consent info / health education)
- Clinical context
- Key messages (what the patient must understand and do)
- Tone (reassuring / informative / urgent)
- Specific instructions or next steps
- Contact details for queries
Output Structure
Type A: Patient Letter
[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:
- [Action 1 — specific with timeframe]
- [Action 2]
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]
Type B: Patient Information Leaflet
[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"]
Type C: Test Results Letter
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.]
Plain Language Rules (apply to all types)
- Maximum 2 syllables per word where possible
- Maximum 20 words per sentence
- Active voice: "We will contact you" not "You will be contacted"
- Spell out all acronyms on first use
- No Latin: "twice daily" not "bd"
- Use "you" and "we" throughout
- Numbers as digits: "2 tablets" not "two tablets"
Quality Checks
- Written at or below Grade 8 reading level (short words, short sentences)
- Active voice used throughout ("We will contact you" not "You will be contacted")
- Results letter states the result in the first sentence
- Next steps are specific and include timeframes
- No Latin or acronyms without explanation
- Disclaimer that clinical review is required before sending
Anti-Patterns
- Do not use medical jargon without a plain-English explanation — write for the patient, not the clinician
- Do not omit a clear "next steps" section — patients must know exactly what to do after reading
- Do not produce final content without flagging that clinical review is required before sending
- Do not write above a Grade 8 reading level without a compelling reason — accessibility is the default
- Do not include Latin abbreviations (e.g. "p.r.n.", "b.d.") without spelling them out — they are not universally understood
Example Trigger Phrases
- "Write a patient letter about [topic]"
- "Create a patient information leaflet for [procedure]"
- "Write a plain English results letter for [test]"
| 1 | |
| 2 | name patient-communication |
| 3 | description "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." |
| 4 | |
| 5 | |
| 6 | # Patient Communication Skill |
| 7 | |
| 8 | Writes patient-facing healthcare communications in plain, accessible language — targeting UK Grade 6 / US Grade 8 reading level. |
| 9 | |
| 10 | WARNING: All patient communications must be reviewed and approved by a qualified healthcare professional before sending. This skill produces drafts only. |
| 11 | |
| 12 | ## Required Inputs |
| 13 | **Communication type** (appointment letter / results letter / discharge info / patient leaflet / consent info / health education) |
| 14 | **Clinical context** |
| 15 | **Key messages** (what the patient must understand and do) |
| 16 | **Tone** (reassuring / informative / urgent) |
| 17 | **Specific instructions or next steps** |
| 18 | **Contact details for queries** |
| 19 | |
| 20 | ## Output Structure |
| 21 | |
| 22 | ### Type A: Patient Letter |
| 23 | |
| 24 | [Date] |
| 25 | |
| 26 | Dear [Patient name], |
| 27 | |
| 28 | **Re: [Clear subject line in bold]** |
| 29 | |
| 30 | [Opening paragraph: State clearly what this letter is about. No preamble.] |
| 31 | |
| 32 | [Main content — short paragraphs, 2-3 sentences each. Bullet points for instructions. Bold anything the patient must do or remember.] |
| 33 | |
| 34 | **What happens next:** |
| 35 | [Action 1 — specific with timeframe] |
| 36 | [Action 2] |
| 37 | |
| 38 | **If you have questions:** |
| 39 | Contact us at [phone] between [hours] or email [address]. |
| 40 | |
| 41 | If you feel unwell before your appointment, please [specific instruction]. |
| 42 | |
| 43 | Yours sincerely, [Name, Title, Department] |
| 44 | |
| 45 | |
| 46 | |
| 47 | ### Type B: Patient Information Leaflet |
| 48 | |
| 49 | **[Plain language title]** |
| 50 | |
| 51 | **What is [topic]?** [2-3 plain English sentences. Explain technical terms immediately.] |
| 52 | |
| 53 | **Why has this been recommended for me?** [Personalised clinical reason in patient terms] |
| 54 | |
| 55 | **What will happen?** [Numbered step by step] |
| 56 | |
| 57 | **What are the benefits?** [Honest statement] |
| 58 | |
| 59 | **What are the risks?** [Common first, then rare but serious. Use frequencies: "About 1 in 10 people..." not "10% incidence"] |
| 60 | |
| 61 | **What should I do to prepare?** [Specific instructions] |
| 62 | |
| 63 | **When should I contact someone?** [Specific signs — not vague. "Temperature above 38C" not "if you feel unwell"] |
| 64 | |
| 65 | |
| 66 | |
| 67 | ### Type C: Test Results Letter |
| 68 | |
| 69 | **Your [test name] results — [Normal / Abnormal] — stated in the FIRST sentence, never paragraph 3.** |
| 70 | |
| 71 | [What this means in plain English] |
| 72 | |
| 73 | **What happens next:** [Clear next steps. If no action, say so explicitly.] |
| 74 | |
| 75 | |
| 76 | |
| 77 | ## Plain Language Rules (apply to all types) |
| 78 | Maximum 2 syllables per word where possible |
| 79 | Maximum 20 words per sentence |
| 80 | Active voice: "We will contact you" not "You will be contacted" |
| 81 | Spell out all acronyms on first use |
| 82 | No Latin: "twice daily" not "bd" |
| 83 | Use "you" and "we" throughout |
| 84 | Numbers as digits: "2 tablets" not "two tablets" |
| 85 | |
| 86 | ## Quality Checks |
| 87 | |
| 88 | [ ] Written at or below Grade 8 reading level (short words, short sentences) |
| 89 | [ ] Active voice used throughout ("We will contact you" not "You will be contacted") |
| 90 | [ ] Results letter states the result in the first sentence |
| 91 | [ ] Next steps are specific and include timeframes |
| 92 | [ ] No Latin or acronyms without explanation |
| 93 | [ ] Disclaimer that clinical review is required before sending |
| 94 | |
| 95 | ## Anti-Patterns |
| 96 | |
| 97 | [ ] Do not use medical jargon without a plain-English explanation — write for the patient, not the clinician |
| 98 | [ ] Do not omit a clear "next steps" section — patients must know exactly what to do after reading |
| 99 | [ ] Do not produce final content without flagging that clinical review is required before sending |
| 100 | [ ] Do not write above a Grade 8 reading level without a compelling reason — accessibility is the default |
| 101 | [ ] Do not include Latin abbreviations (e.g. "p.r.n.", "b.d.") without spelling them out — they are not universally understood |
| 102 | |
| 103 | ## Example Trigger Phrases |
| 104 | "Write a patient letter about [topic]" |
| 105 | "Create a patient information leaflet for [procedure]" |
| 106 | "Write a plain English results letter for [test]" |
| 107 |
Details
- Updated
- Sep 23, 2026
- License
- MIT
- Stars on the repo
- ★ 1,395
- Checked
- Source
- mohitagw15856/pm-claude-skills ↗
- Creator
- mohitagw15856 · 193 listings
Made with patient-communication


Similar skills
See all →
SkillReverse engineer native, managed, Electron/JavaScriptREA
SkillBrainstorms ideas into designs before any creative workBrainstorming Ideas Into Designs
SkillRequires technical rigor and verificationCode Review Reception
SkillDiagnosis loop for hard bugs and performance regressionsDiagnosing bugs
SkillImplement the result of /to-spec and /to-tickets in codeImplement spec
SkillWriting a PR bodyMore from mohitagw15856
SkillDesign a 360-degree feedback survey or write a structured360-Degree Feedback Template Skill
SkillDesign statistically rigorous A/B tests for product featuresA/B Test Planner Skill
SkillGenerate a WCAG 2.2 accessibility audit checklistAccessibility Audit Skill
SkillBuild a structured account plan for any key customerAccount Plan Skill
SkillOptimize an article for Answer Engine Optimization so AIAEO Optimizer Skill
SkillConduct a structured ethical review of an AI or ML featureAI Ethics Review Skill