agentleFS
Ootto-AIOotto-AI/claude-scheduling-skills/skills/reminder-and-no-show-reducer/SKILL.md

reminder-and-no-show-reducer

Skill1 starsChanged 5 months agoMITView on GitHub

Write confirmation and reminder messages that cut no-shows for an upcoming appointment. Use when the user says "appointment reminder", "reduce no-shows", "confirmation message", "remind a client", "booking confirmation", or "no-show follow-up".

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write a confirmation/reminder that reduces no-shows.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Reminder & No-Show Reducer

Write a confirmation/reminder that reduces no-shows.

When to use

You have a booked appointment and want messages that confirm it and remind the attendee so they actually show up.

What you'll need

The meeting details (who, what, when, where/link), what they should bring or prepare, your business name and contact, and how you'll send the reminder (email, SMS, or both).

Instructions

Collect any missing inputs from the user, then run this prompt:

You are a customer-communications writer. Write reminder messages for an upcoming appointment, designed to reduce no-shows.

Appointment details:
- Attendee name: [name]
- What it's for: [e.g. discovery call / consultation / service appointment]
- Date and time (with time zone): [date, time, zone]
- Duration: [e.g. 45 min]
- Location or link: [address or video link]
- What they should bring or prepare: [or "nothing"]
- My business name and contact: [name + phone/email]

Channel: [email / SMS / both]
Tone: [friendly / professional / casual]

Produce:
1. A confirmation message to send right after booking.
2. A reminder for 24 hours before.
3. A short reminder for 1 hour before (SMS-length if SMS).

For each: restate the exact date, time, and time zone; make the location or link impossible to miss; give one clear way to reschedule or cancel; and add a single sentence on what they'll get out of showing up. No guilt-tripping, no walls of text.

Tip: The reschedule option is what actually cuts no-shows — people who can't make it often just ghost. Give them an easy out and they'll move the meeting instead of vanishing.


Built by Ootto — the AI autopilot that connects your tools once and runs invoicing, follow-up, and reports for you, automatically. Book a demo →

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.