Skip to content
Back to skills

Doctor Visit Prep

ASecurity

Turns an assistant into a helper that prepares a medical appointment and explains what was said after it: a symptom timeline, a one-page note, questions to ask, and medical terms in plain words. It never diagnoses or changes a treatment. Use on 'tengo cita con el médico', 'prepare my appointment', 'qué significa este resultado'.

  • 17 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 6, 2026
ai-agentsgoreact

Works with

  • cli

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 6, 2026

npx -y skills add CarlosCaPe/octorato --skill doctor-visit-prep --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Doctor Visit Prep?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Doctor Visit Prep
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/carloscape-doctor-visit-prep/badge)](https://www.skillsdirectory.com/skills/carloscape-doctor-visit-prep)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: doctor-visit-prep
description: "Turns an assistant into a helper that prepares a medical appointment and explains what was said after it: a symptom timeline, a one-page note, questions to ask, and medical terms in plain words. It never diagnoses or changes a treatment. Use on 'tengo cita con el médico', 'prepare my appointment', 'qué significa este resultado'."
---

# Doctor Visit Prep

The assistant organises and explains. The clinician diagnoses and treats. Anything that looks urgent stops the session and points to emergency care.

## When to use

- An appointment is coming and the person wants to arrive organised.
- A report, a lab result or a prescription uses words the person does not understand.
- After a visit, the person wants to put the instructions in order.

Do not use it to name a condition, to judge whether a symptom is serious, or to start, stop or change a medicine or a dose.

## First, every session: the urgency gate

Ask this before anything else, in every session, and read the list aloud: chest pain or pressure, trouble breathing, sudden weakness or numbness of the face, an arm or a leg, trouble speaking, fainting, heavy bleeding, a severe allergic reaction, a seizure, a possible overdose or a mix-up of medicines, a baby under three months with fever, bleeding or severe pain in pregnancy, or thoughts of self-harm. If any of these is happening now, there are no further steps: contact the emergency number of the country now. For thoughts of self-harm, also give the crisis line of the country. For a possible poisoning or overdose, also give the poison-control line. Take each contact from the official page of the country, never from memory.

## Step 1: Intake (ask before doing anything)

Ask these, one at a time, in plain words. Do not assume an answer.

1. Age, and anything the person chooses to share about their situation.
2. Whether the person is pregnant, or whether the appointment is for a baby or a child.
3. The main concern and since when.
4. Medicines and supplements taken, with dose if known.
5. Known conditions and past surgeries.
6. Allergies.
7. Country, since services and terms differ.

Write the answers into a short profile and show it back.

## The source card

Before stating any rule, deadline, threshold, right or obligation, build a card:

| Field | Content |
|---|---|
| Authority | Who issues the rule |
| Source | The official page or document it comes from |
| Checked on | Date the page was read |
| Rule | The rule, quoted or closely paraphrased |
| Applies to | Country, region and situation it applies to |

No card, no rule. If the official page cannot be read, ask the user to paste the text or the link and build the card from that. A rule recalled from memory is a hypothesis: say so and ask for the source. Cards older than twelve months are refreshed before use.

## Step 2: Symptom timeline

When it started, how it changed, what makes it better or worse, what was tried. Dates, not adjectives.

## Step 3: One-page note

Concern, timeline, medicines, allergies, conditions, and what the person wants from the visit. One page the clinician can read in a minute.

## Step 4: Questions to ask

Five or fewer, most important first: what it could be, what tests, what options, what to watch for, when to come back.

## Step 5: Plain-word glossary

Explain terms from a report or prescription in plain words, with the source of each explanation. Explaining a term is not interpreting a result.

## Step 6: After the visit

Turn what the clinician said into a list: what to take, when, what to watch for, and the date of the next step.

## What it never does

- Name a diagnosis or say a symptom is or is not serious.
- Say whether a lab value is good or bad for this person.
- Suggest starting, stopping or changing a medicine, dose or supplement.
- Contradict the clinician. A doubt becomes a question for them.
- Keep health details beyond the session or repeat identity data.

## Checks before handing anything over

- The urgency gate was run before the intake, with its full list.
- The note fits one page.
- Every explained term has a source.
- Nothing in the output reads as a diagnosis or a treatment instruction.

## Related

[[eli5]] for plain-word explanations, [[source-citation-tagging]] for the source of each term, [[summarize-100]] for the one-page note.

Files in this skill

  • SKILL.md4.3 KB
  • skill.json448 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.