Agent Skillsmohitagw15856/pm-claude-skills › patient-communication

patient-communication

GitHub

生成通俗易懂的患者沟通文档(如信件、手册、结果通知),确保符合8年级阅读水平,强调清晰下一步和医疗审核。

plugins/pm-research/skills/patient-communication/SKILL.md mohitagw15856/pm-claude-skills

Trigger Scenarios

撰写患者信件或预约通知 制作健康信息手册或出院总结 编写检查报告解读 生成健康教育内容

Install

npx skills add mohitagw15856/pm-claude-skills --skill patient-communication -g -y
More Options

Non-standard path

npx skills add https://github.com/mohitagw15856/pm-claude-skills/tree/main/plugins/pm-research/skills/patient-communication -g -y

Use without installing

npx skills use mohitagw15856/pm-claude-skills@patient-communication

指定 Agent (Claude Code)

npx skills add mohitagw15856/pm-claude-skills --skill patient-communication -a claude-code -g -y

安装 repo 全部 skill

npx skills add mohitagw15856/pm-claude-skills --all -g -y

预览 repo 内 skill

npx skills add mohitagw15856/pm-claude-skills --list

SKILL.md

Frontmatter
{
    "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

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]"

Version History

  • a38bc30 Current 2026-07-05 11:26

Same Skill Collection

exports/openclaw/360-feedback-template/SKILL.md
exports/openclaw/401k-plan-decoder/SKILL.md
exports/openclaw/ab-test-planner/SKILL.md
exports/openclaw/ab-test-readout/SKILL.md
exports/openclaw/accessibility-audit/SKILL.md
exports/openclaw/account-plan/SKILL.md
exports/openclaw/acquirer-red-team/SKILL.md
exports/openclaw/ad-copy/SKILL.md
exports/openclaw/aeo-optimizer/SKILL.md
exports/openclaw/agenda-or-cancel/SKILL.md
exports/openclaw/agent-design-review/SKILL.md
exports/openclaw/agent-observability-spec/SKILL.md
exports/openclaw/agent-spec/SKILL.md
exports/openclaw/ai-ethics-review/SKILL.md
exports/openclaw/ai-eval-plan/SKILL.md
exports/openclaw/ai-feature-prd/SKILL.md
exports/openclaw/ai-product-canvas/SKILL.md
exports/openclaw/air-quality/SKILL.md
exports/openclaw/altitude-shifter/SKILL.md
exports/openclaw/ambiguity-resolver/SKILL.md
exports/openclaw/analyst-relations-brief/SKILL.md
exports/openclaw/announcement-card/SKILL.md
exports/openclaw/api-docs-writer/SKILL.md
exports/openclaw/api-test-plan/SKILL.md
exports/openclaw/api-versioning-strategy/SKILL.md
exports/openclaw/apology-letter/SKILL.md
exports/openclaw/architecture-decision-record/SKILL.md
exports/openclaw/architecture-diagram/SKILL.md
exports/openclaw/archive-strategy/SKILL.md
exports/openclaw/assumption-bounty/SKILL.md
exports/openclaw/assumption-mapper/SKILL.md
exports/openclaw/async-update-format/SKILL.md
exports/openclaw/auto-repair-estimate-decoder/SKILL.md
exports/openclaw/autopilot-charter/SKILL.md
exports/openclaw/benefits-decoder/SKILL.md
exports/openclaw/bid-tender-review/SKILL.md
exports/openclaw/board-deck-narrative/SKILL.md
exports/openclaw/board-minutes/SKILL.md
exports/openclaw/board-pre-read/SKILL.md
exports/openclaw/bom-cost-review/SKILL.md
exports/openclaw/bookkeeping-categorization/SKILL.md
exports/openclaw/boolean-search-builder/SKILL.md
exports/openclaw/brag-doc/SKILL.md
exports/openclaw/brainstorming/SKILL.md
exports/openclaw/brief-builder/SKILL.md
exports/openclaw/briefing-note/SKILL.md
exports/openclaw/budget-builder/SKILL.md
exports/openclaw/budget-variance-analysis/SKILL.md
exports/openclaw/bug-diagnosis/SKILL.md
exports/openclaw/bug-report/SKILL.md

Metadata

Files
0
Version
471c606
Hash
81593a86
Indexed
2026-07-05 11:26

- 위키
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-07-29 12:39
浙ICP备14020137号-1 $방문자$