Agent skill

Patient Communication

by mohitagw15856 in mohitagw15856/pm-claude-skills

Write clear, plain-English patient communications for any healthcare context.

MITAuto-check passedWriting & Content

Install Patient Communication

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill patient-communication -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills patient-communication --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/patient-communication .claude/skills/patient-communication && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
patient-communication
GitHub stars
1.4k
Token cost
~1k tokens
SKILL.md length
511 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Write clear, plain-English patient communications for any healthcare context.

  • Asked to write a patient letter
  • SKILL.md covers Required Inputs, Output Structure, Plain Language Rules (apply to… and Quality Checks, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Patient information leaflet

What it does

Patient Communication is an agent skill from mohitagw15856/pm-claude-skills. 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.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Writing & Content, covering Plain language and style rules. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked to write a patient letter
  • Patient information leaflet
  • Appointment letter
  • Test-results letter

Example prompts

  • “/patient-communication”

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Patient Communication loads about 1k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 511 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~93
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 511 words, ~1,025 tokens.

Download SKILL.mdSave it as .claude/skills/patient-communication/SKILL.md (or your agent's skills folder).
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.]


Show full SKILL.md (219 more words)Show less

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

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/patient-communication of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Patient Communication next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Patient Communication compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Patient Communication this skillmohitagw15856/pm-claude-skills1.4k—~1kAutomated safety check: PassMIT
Asd Ste100danyuchn/asd-ste100-skill4.3k—~4.1kAutomated safety check: PassMIT
Technical Writing Standardcursor/plugins11k10 repos~2.3kAutomated safety check: PassNone
Ponytail AuditDietrichGebert/ponytail160k—~1.4kAutomated safety check: PassMIT
Natural Japanese Business Writingcoji/natural-japanese1.9k—~2.1kAutomated safety check: PassMIT
PgjevrealZachi/pg-jev1.1k—~2.9kAutomated safety check: PassCustom licence

Similar skills

  • Asd Ste100

    danyuchn/asd-ste100-skill

    A skill your agent uses when English text must be parsed without a human to resolve ambiguity — tool descriptions, error messages, inter-agent instructions, system prompts, status reports — and…

    4.3k GitHub stars~4.1k tokensUpdated 7 days ago
    Writing & ContentAuto-check passed
  • Official

    Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.

    11k GitHub starsUsed in 10 repos~2.3k tokens
    Writing & ContentAuto-check passed
  • Ponytail Audit

    DietrichGebert/ponytail

    Quality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split.

    160k GitHub stars~1.4k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Writes and edits Japanese business documents so they read clearly and naturally, removes AI-sounding phrasing and can score how AI-like a text reads.

    1.9k GitHub stars~2.1k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed
  • Pgjev

    realZachi/pg-jev

    Install, configure, query and explain pgjev (the jev PostgreSQL extension that filters, ranks and classifies rows with plain-language conditions via TypeSafe's Jev model).

    1.1k GitHub stars~2.9k tokensUpdated 4 days ago
    Writing & ContentAuto-check passed
  • Defensive Writing Editor

    lennney/stop-that-shit

    Cuts defensive disclaimers, stacked hedging and self-protective narration from proposals and summaries, keeping only limits that affect the reader's decision.

    2.5k GitHub starsUsed in 1 repo~1.2k tokens
    Writing & ContentAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo
  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated 2 days ago
    Auto-check passed
  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed
  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated 2 days ago
    Auto-check passed

Questions about Patient Communication

What does Patient Communication do?

Write clear, plain-English patient communications for any healthcare context. Patient Communication is an agent skill from mohitagw15856/pm-claude-skills. Write clear, plain-English patient communications for any healthcare context.

When should I use Patient Communication?

Patient Communication fits situations like: asked to write a patient letter; patient information leaflet; appointment letter; test-results letter.

How do I install Patient Communication in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill patient-communication -a claude-code`. Or copy the skill folder (skills/patient-communication in mohitagw15856/pm-claude-skills) into .claude/skills/patient-communication in your project. Claude Code loads it when a task matches its description.

How do I install Patient Communication in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill patient-communication -a codex`. Or copy the skill folder (skills/patient-communication in mohitagw15856/pm-claude-skills) into .agents/skills/patient-communication in your project. Codex loads it when a task matches its description.

Can I use Patient Communication in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill patient-communication -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/patient-communication, .gemini/skills/patient-communication, .github/skills/patient-communication and .opencode/skills/patient-communication in your project.

What does Patient Communication need to run?

SKILL.md names no scripts, command-line tools or credentials: Patient Communication is instructions for the agent only.

Does Patient Communication access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Patient Communication safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Patient Communication use?

Patient Communication is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Patient Communication use?

About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Patient Communication?

Skills that share tags, products or a category with Patient Communication: Asd Ste100 (danyuchn/asd-ste100-skill, 4.3k stars), Technical Writing Standard (cursor/plugins, 11k stars), Ponytail Audit (DietrichGebert/ponytail, 160k stars) and Natural Japanese Business Writing (coji/natural-japanese, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Patient Communication?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.