Mmcp.market

prescription-refill skill

by Razshy·Razshy/Wiggle·91 stars

Refill a prescription at a pharmacy. Works from a medication name, an Rx number, a photo of the bottle, or just "I'm running low." Confirms exactly what's being requested, gathers everything the pharmacy will ask for up front, and handles the refill online or by phone — whichever is fastest.

A100/100content scan

Is the prescription-refill skill safe?

Clean: nothing in its files matched our rules. We read 2 files in the folder on 2026-09-28.

No findings.

Install the prescription-refill skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/Razshy/Wiggle.git /tmp/Wiggle
mkdir -p ~/.claude/skills
cp -r /tmp/Wiggle/mnt-skills/examples/prescription-refill ~/.claude/skills/prescription-refill
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

You're helping me refill a prescription. Act like a concierge — calm, thorough, and one step ahead of what the pharmacy will ask for.

This is a Tier 2 skill (action, reversible). A refill request can be cancelled or left unpicked-up, so it's not destructive — but it does involve my health information and real-world contact. Confirm the plan before you act.

Important: Always start completely fresh. Never carry over medication names, Rx numbers, pharmacy details, or dosage information from prior conversation. DO use memory to recall known identity details — my name, date of birth, phone number, and preferred pharmacy — since the pharmacy will ask for these.

Flow:

  1. Ask what I need refilled via askuserinput_v0. Any of these works equally well — go with whatever I give you:
  • The medication name ("my metformin")
  • The Rx number
  • A photo of the bottle or label
  • "The one I ran out of" — if so, ask which medication

Extract: medication name, strength/dosage if visible, Rx number if visible, and pharmacy name if visible.

  1. Confirm exactly what I'm asking for via askuserinput_v0. This is the critical gate — do not skip it and do not infer. Present the options plainly:
  • Refill the same prescription — same medication, same dose, same quantity
  • Change the dosage — different strength or quantity (this needs the prescriber, not just the pharmacy)
  • A new prescription — a medication I don't currently have an Rx for (also needs the prescriber)

Phrases like "I finished my dose" or "I need more" almost always mean refill the same Rx — but confirm it explicitly before proceeding. If it turns out I want a dosage change or a new Rx, say clearly that the pharmacy can't do that on their own and offer to help me contact my prescriber instead.

  1. Gather everything the pharmacy will ask for before making any contact. Pull from memory where you can, and ask via askuserinput_v0 for anything missing:
  • Full name (as the pharmacy has it on file)
  • Date of birth
  • Phone number on the account
  • Pharmacy name and location (if not already clear from the bottle)
  • Rx number — or if I don't have it, the medication name and strength so they can look it up
  • How I want to get it: pickup, delivery, or mail

Don't contact anyone until you have all of this. A call that has to be repeated because you were missing DOB wastes everyone's time.

  1. Find the fastest refill path. Check in this order:
  • Pharmacy's app or online refill portal (most chains have one — often just needs the Rx number)
  • Automated refill phone line (IVR, no human needed)
  • Call and speak to pharmacy staff
  • Contact the prescriber (if there are no refills remaining and the pharmacy needs a new authorization)

Silently line up a fallback: if this pharmacy can't fill it — out of stock, Rx transferred away, no refills left — know what the next step is before you hit the wall.

  1. Present the plan via askuserinput_v0 in one short message:
  • What you're refilling (medication, strength)
  • Where (pharmacy name, location)
  • How (online / automated line / speaking to staff)
  • What info you'll share (name, DOB, phone, Rx number — nothing more)
  • Pickup or delivery preference

Get my explicit go-ahead. Do not submit or dial until I've said yes.

  1. If online or app: Open the pharmacy's refill portal. Enter the Rx number and my details. Hand the browser to me if it needs login. If the portal says "no refills remaining" or "Rx not found," don't retry — pivot to calling the pharmacy to find out why.
  1. If phone:
  • If it's an automated refill line, navigate the IVR — enter the Rx number and confirm pickup/delivery. Straightforward.
  • If you reach a person, lead with the ask and in the same breath say you're Claude, an AI calling on my behalf. Don't bury it, don't make it a disclaimer — state it plainly and move on: "Hi, I'm Claude, an AI assistant calling for [my name] to request a refill on Rx [number]."
  • If they say they won't take refill requests from an AI — or can't verify without speaking to me directly — stop immediately. Thank them, end the call, and tell me what happened so I can call myself.
  • If they ask for something you don't have — insurance member ID, a secondary phone, the prescriber's name — don't guess. Tell them you'll check and call back, then relay the question to me and wait.
  • Keep it to one call per pharmacy. Gather everything you need from them before hanging up: is it in stock, when will it be ready, any copay, any issue with refills remaining.
  1. If the Rx has moved or has no refills left:
  • Transferred to another pharmacy: Ask them which pharmacy now holds it. Relay that to me and offer to contact the new pharmacy — but confirm with me first before making a second call.
  • No refills remaining: The pharmacy needs a new authorization from my prescriber. Ask whether they'll contact the prescriber for me (many will), or whether I need to. Relay the answer and offer to help with whichever path is needed.
  • Out of stock: Ask when it'll be in, or whether a nearby location has it. Bring the options back to me — don't pick for me.
  1. Show a summary card:
  • Medication and strength
  • Pharmacy and location
  • Status (refill submitted / ready for pickup on [date] / pending prescriber authorization)
  • Pickup or delivery details
  • Copay amount if they mentioned it
  • Anything I need to do (bring ID, call prescriber, etc.)
  1. If any step fails — portal down, line busy, pharmacy closed — immediately offer the next-best path without stalling.

Throughout: be warm and precise. Medication details are not a place for approximation — if you're not certain about a name, a dose, or a number, ask. One accurate call beats five sloppy ones.

More skills from Razshy/Wiggle

  • Aalgorithmic-artCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
  • Abenepass-reimbursementSubmit expense reimbursements through Benepass (app.getbenepass.com). For users whose employer uses Benepass as their benefits platform. Handles login, benefit selection, form filling, receipt upload, and submission. Requires browser/computer-use capabilities.
  • Abrand-guidelinesApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
  • Abuilt-in-browserRead this skill before the first step that uses the built-in browser, the browser pane inside the Claude desktop app (also called the in-app browser, the browser pane, Claude's browser, or \"your own browser\"), whose tools are named mcp__Claude_Browser__* when the session runs in the desktop app and mcp__remote-devices__Claude_Browser__* when a cloud session is linked to the person's computer; before those tools are turned on there may be a single enable__mcp__remote-devices__Claude_Browser tool instead. It covers the pane's persistent sign-ins, tabs and preview_start, reading pages as text, site approvals, what the pane cannot open, and what to do when it cannot be reached. It is not for Claude in Chrome (mcp__claude-in-chrome__* tools), which has its own skill, and it does not decide which browser to use.
  • Acall-to-bookMake a phone call to book an appointment or reservation. Checks calendar first, gets explicit consent before dialing, discloses AI identity on the call, and adds the booking to calendar when done.
  • Acancel-unsubscribeCancel a subscription or unsubscribe from a service. Works from a description, a pasted charge line, a URL, or a photo/screenshot. Can also audit a full statement for recurring charges and cancel several at once. Finds the right contact method and handles the cancellation — including phone calls.
  • Acanvas-designCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
  • Achrome-browserRead this skill before the first step that uses Claude in Chrome, the browser extension whose tools are named mcp__claude-in-chrome__* (also called Chrome, the browser extension, or the external browser) and which acts in the person's real Chrome with their own sign-ins; before those tools are turned on there may be a single enable__mcp__claude-in-chrome tool instead. It covers loading the tools in one ToolSearch call, checking the person's open tabs and working in a new tab, site permissions, GIF recordings, console logs, dialogs to avoid, and when to stop and ask. It is not for the built-in browser (mcp__Claude_Browser__* or mcp__remote-devices__Claude_Browser__* tools), which has its own skill, and it does not decide which browser to use.
  • Acomputer-useRead this skill before the first step of any request to do something in an app on the person's own computer (Notes, Finder, System Settings, any desktop app), to look at their screen, or for \"computer use\". Computer use (desktop control) lets Claude take screenshots of the person's desktop and control it with clicks, typing and scrolling through the Claude desktop app; its tools are named mcp__computer-use__* when the session runs in the desktop app and mcp__remote-devices__computer_* when a cloud session is linked to the person's computer; before a conversation is linked there may be no such tools, only an enable__mcp__remote-devices__Claude_Browser tool, which links it. It covers getting linked, picking the right tool, the access flow, and what to do when computer use is off or out of reach. It is not for websites, which go through Claude in Chrome or the built-in browser and their own skills.
  • Adeep-researchUse this skill when the user's prompt requires (1) researching a topic across multiple sources, comparing options or alternatives, analyzing trends or history, understanding markets or industries, or reviewing literature or studies and (2) synthesizing that research into a comprehensive, narrative report. If you're planning to search the web or internal knowledge bases, consider using this skill. This skill coordinates research subagents, so use it only when you have a tool for spawning subagents (the Agent or Task tool); otherwise, research the question directly.
  • Adoc-coauthoringGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
  • AdocxUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx) or Word templates (.dotx). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file (to download, email or print), use this skill. However, if they ask for a document, page, report, memo, or notes WITHOUT naming a file format and the session offers a dedicated document or page skill or connector, use that instead. Do NOT use for PDFs, spreadsheets, Google Docs, or coding unrelated to document generation.

All agent skills → · MCP servers