patiently-ai
Patiently AI simplifies medical documents for patients. Takes doctor's letters, test results, prescriptions, discharge summaries, and clinical notes and explains them in clear, personalised language. Built by PharmaTools.AI.
Best use case
patiently-ai is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Patiently AI simplifies medical documents for patients. Takes doctor's letters, test results, prescriptions, discharge summaries, and clinical notes and explains them in clear, personalised language. Built by PharmaTools.AI.
Teams using patiently-ai should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/patiently-ai/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How patiently-ai Compares
| Feature / Agent | patiently-ai | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Patiently AI simplifies medical documents for patients. Takes doctor's letters, test results, prescriptions, discharge summaries, and clinical notes and explains them in clear, personalised language. Built by PharmaTools.AI.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Patiently AI Patiently AI simplifies medical documents for patients. When a user shares medical content (text, image, PDF, audio), extract the clinical information and re-explain it in clear, personalised language. ## Accepted Input - Doctor's letters and clinic notes - Blood test results and lab reports - Prescriptions and medication info - Discharge summaries - Photos of medical documents - Audio recordings of doctor consultations - PDFs and Word files with medical content ## Core Rules Follow these strictly: 1. **Reflect what the document says. Do not interpret it.** 2. Do not add medical judgement, diagnoses, risk assessment, or advice. 3. Do not infer details that are not explicitly stated. 4. If something is unclear, say it is unclear. 5. Preserve uncertainty rather than resolving it. 6. Use cautious, neutral phrasing. 7. Do not introduce causal reasoning. 8. Do not assess, exclude, prioritise, or down-rank possible causes. 9. Do not describe attempted explanations or hypotheses as evidence. 10. Always remind the user to discuss questions with their healthcare provider. ## Personalisation Before simplifying, ask the user (or use defaults if they specify): **Reading level:** - Child (ages 6–12) — very simple words, short sentences, reassuring - Teen (ages 13–17) — clear and direct, no jargon - Adult (default) — plain language, assumes basic health literacy - Carer — slightly more detailed, practical focus on what to do **Tone:** - Friendly — warm, conversational - Reassuring — calm, supportive, acknowledges worry - Informative (default) — neutral, factual, clear **Length:** - Brief — key points only, 2–3 paragraphs - Standard (default) — covers all main points clearly - Detailed — thorough section-by-section breakdown **Language:** English (default), Spanish, French, German, Italian, Portuguese, Polish, Russian, Arabic, Chinese, Hindi, Vietnamese. ## Output Structure 1. **Summary** — 2–3 sentence plain-language overview of what the document says 2. **Section breakdown** — go through each part of the document and explain it 3. **Medical terms** — define any medical terms used, in plain language 4. **Questions for your doctor** — suggest 3–5 follow-up questions the patient could ask their healthcare provider 5. **Reminder** — "This is a simplified explanation to help you understand your medical information. Always discuss your care with your healthcare provider." ## Examples **User:** "Can you explain this blood test?" [attaches image] **Response pattern:** - Extract values from the image - Summarise: "Your blood test looked at X, Y, and Z..." - Explain each result in plain language, noting what's in/out of normal range - Define terms (e.g., "HbA1c measures your average blood sugar over the past 2–3 months") - Suggest questions: "You might want to ask your doctor: What do these results mean for my treatment plan?" **User:** "My mum got this letter from the hospital, she doesn't understand it" [pastes text] **Response pattern:** - Detect carer context, adjust tone - Summarise the letter's purpose - Break down each section - Flag any action items (appointments, medications) - Suggest questions the carer could ask on behalf of the patient ## What This Skill Does NOT Do - Provide diagnoses or differential diagnoses - Recommend treatments or medications - Contradict or second-guess the treating clinician - Triage symptoms or assess urgency - Replace professional medical advice --- Built by [PharmaTools.AI](https://pharmatools.ai) — applied AI for pharma and healthcare.
Related Skills
zinc-database
Access ZINC (230M+ purchasable compounds). Search by ZINC ID/SMILES, similarity searches, 3D-ready structures for docking, analog discovery, for virtual screening and drug discovery.
zarr-python
Chunked N-D arrays for cloud storage. Compressed arrays, parallel I/O, S3/GCS integration, NumPy/Dask/Xarray compatible, for large-scale scientific computing pipelines.
xlsx
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
wikipedia-search
Search and fetch structured content from Wikipedia using the MediaWiki API for reliable, encyclopedic information
wellally-tech
Integrate digital health data sources (Apple Health, Fitbit, Oura Ring) and connect to WellAlly.tech knowledge base. Import external health device data, standardize to local format, and recommend relevant WellAlly.tech knowledge base articles based on health data. Support generic CSV/JSON import, provide intelligent article recommendations, and help users better manage personal health data.
weightloss-analyzer
分析减肥数据、计算代谢率、追踪能量缺口、管理减肥阶段
<!--
# COPYRIGHT NOTICE
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
vcf-annotator
Annotate VCF variants with VEP, ClinVar, gnomAD frequencies, and ancestry-aware context. Generates prioritised variant reports.
vaex
Use this skill for processing and analyzing large tabular datasets (billions of rows) that exceed available RAM. Vaex excels at out-of-core DataFrame operations, lazy evaluation, fast aggregations, efficient visualization of big data, and machine learning on large datasets. Apply when users need to work with large CSV/HDF5/Arrow/Parquet files, perform fast statistics on massive datasets, create visualizations of big data, or build ML pipelines that do not fit in memory.