mohitagw15856
036511ab3e
Broadens both reach (more tools) and content types (an MCP server), continuing the multi-platform story. Windsurf + Aider: - build-exports.mjs gains two platforms: exports/windsurf/*.md (workspace rules, trigger: model_decision) and exports/aider/*.md (conventions for `aider --read`). Now 5 platforms (ChatGPT, Gemini, Cursor, Windsurf, Aider). - install.sh + bin/cli.mjs install both (windsurf -> .windsurf/rules, aider -> .aider/skills with a --read hint); generated README index is excluded from copies. - One-line windsurf-install.sh / aider-install.sh wrappers for parity. MCP server (new content type): - mcp/server.mjs — zero-dependency stdio MCP server exposing list_skills, search_skills, get_skill. Published as a second bin (pm-claude-skills-mcp). Logs to stderr; reads bundled skills/ at startup. mcp/README.md documents client config. Also: README hero "See it in action" demo placement (ready to swap in a GIF; recording guide in web/docs-assets/README.md), Works-With table + exports + install docs updated, CHANGELOG Unreleased. package.json files/bin updated. Claude-Session: https://claude.ai/code/session_016JWn5jRD5tcEFKrubjQ6Px Co-authored-by: Claude <noreply@anthropic.com>
107 lines
4.0 KiB
Markdown
107 lines
4.0 KiB
Markdown
---
|
|
trigger: model_decision
|
|
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. Targets accessible 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]"
|