New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Write clear, plain-English patient communications for any

Patient Communication Skill

by mohitagw15856 · MIT license · ★ 1,395 on GitHub · updated Sep 23

Patient Communication Skill cover

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)
Claude Codenpx skills add mohitagw15856/pm-claude-skills --skill patient-communication -g -a claude-code
Claude Code (manual)mkdir -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-communication
Windows (PowerShell)New-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" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md4.0 KB
Read the files here
mohitagw15856/f6ca7931 file
SKILL.md
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---
2name: patient-communication
3description: "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 
8Writes patient-facing healthcare communications in plain, accessible language — targeting UK Grade 6 / US Grade 8 reading level.
9 
10WARNING: 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 
26Dear [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:**
39Contact us at [phone] between [hours] or email [address].
40 
41If you feel unwell before your appointment, please [specific instruction].
42 
43Yours 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 
View all files on GitHub →

Details

Updated
Sep 23, 2026
License
MIT
Stars on the repo
★ 1,395
Checked
Source
mohitagw15856/pm-claude-skills ↗
Creator
mohitagw15856 · 193 listings
View creator

Made with patient-communication

Patient Communication Skill — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)
Patient Communication Skill — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856

Patient Communication Skill — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)
Patient Communication Skill — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856

Similar skills

See all →
SkillReverse engineer native, managed, Electron/JavaScriptREAmorluto/rea · by morlutoReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.★ 316k GitHub starsSkillBrainstorms ideas into designs before any creative workBrainstorming Ideas Into Designsobra/superpowers · by obraYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.★ 290k GitHub starsSkillRequires technical rigor and verificationCode Review Receptionobra/superpowers · by obraUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation★ 290k GitHub starsSkillDiagnosis loop for hard bugs and performance regressionsDiagnosing bugsmattpocock/skills · by mattpocockDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.★ 267k GitHub starsSkillImplement the result of /to-spec and /to-tickets in codeImplement specmattpocock/skills · by mattpocockImplement the result of /to-spec and /to-tickets in code.★ 267k GitHub starsSkillWriting a PR bodymattpocock/skills · by mattpocockUse when writing a PR body.★ 267k GitHub stars

More from mohitagw15856

SkillDesign a 360-degree feedback survey or write a structured360-Degree Feedback Template Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.★ 1.4k GitHub starsSkillDesign statistically rigorous A/B tests for product featuresA/B Test Planner Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.★ 1.4k GitHub starsSkillGenerate a WCAG 2.2 accessibility audit checklistAccessibility Audit Skillmohitagw15856/pm-claude-skills · by mohitagw15856Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.★ 1.4k GitHub starsSkillBuild a structured account plan for any key customerAccount Plan Skillmohitagw15856/pm-claude-skills · by mohitagw15856Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.★ 1.4k GitHub starsSkillOptimize an article for Answer Engine Optimization so AIAEO Optimizer Skillmohitagw15856/pm-claude-skills · by mohitagw15856Optimize an article for Answer Engine Optimization (AEO) so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines. Produces an AEO-optimised rewrite with question headings, 50–80 word answer capsules, a paragraph-length audit, and flagged trust signals.★ 1.4k GitHub starsSkillConduct a structured ethical review of an AI or ML featureAI Ethics Review Skillmohitagw15856/pm-claude-skills · by mohitagw15856Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.★ 1.4k GitHub stars