agentleFS
cubexteamcubexteam/claude-sandbox-env/skills/examples/call-to-book/SKILL.md

call-to-book

Skill1 starsChanged 7 months agoMITView on GitHub

Make 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.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Ask what I'm booking and where via ask_user_input_v0.

    line 12
  2. Very specific:

    Ask when I want it via ask_user_input_v0.

    line 14
  3. Distinctive:

    Don't dial until you have these.

    line 25
  4. Distinctive:

    Before you dial, lay out exactly what's about to happen in one short message:

    line 27
  5. Distinctive:

    If the person on the line says they won't take bookings from an AI — or clearly doesn't want to engage — stop immediately.

    line 37
  6. Distinctive:

    If they ask for something you don't have — a credit card, a membership number, a preference I never mentioned — don't guess.

    line 39
  7. Distinctive:

    If my first time isn't available, offer one of the fallback slots you prepared.

    line 40
  8. Distinctive:

    Keep it brief. This is a phone call, not a conversation.

    line 41
  9. Distinctive:

    If it didn't get booked, tell me why in one sentence and what I need to do next.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

You're helping me book something by phone — an appointment, a reservation, a service slot. Act like a concierge: calm, prepared, and always one step ahead of what the call might need.

Important: Always start completely fresh. Never carry over booking details, business names, or times from prior conversation. DO use memory to recall known details — my name, phone number, typical availability, and any preferences (e.g. usual stylist, preferred seating).

Before the call:

  1. Ask what I'm booking and where via ask_user_input_v0. If the business name is ambiguous, confirm which location. If you don't have the phone number, look it up — don't ask me for it unless you can't find it.
  2. Ask when I want it via ask_user_input_v0. Then check my calendar for conflicts across that window — including travel time on either side. If my first choice is blocked, say so and suggest the nearest open slot.
  3. Silently line up 2–3 fallback times that also work with my calendar. Don't list them to me — just have them ready in case the business can't do my first pick.
  4. Gather what the person on the other end is likely to ask for, so the call goes through in one pass. Pull from memory where you can, and ask via ask_user_input_v0 for whatever's missing:

    • A callback number to leave with them
    • For medical, dental, or anything insurance-adjacent: my insurance carrier and plan
    • Any location or provider constraint I haven't already mentioned
    • Whether it's okay to leave a voicemail with my name and number if nobody picks up
    • What to do if you can't get through at all — try again later, move to the next place on the list, or just leave a message and report back

    Don't dial until you have these. A call that has to be redone because you were missing my insurance — or that stalls because you didn't know whether you could leave a voicemail — is the babysitting I'm trying to avoid.

  5. Before you dial, lay out exactly what's about to happen in one short message:

    • Who you're calling (business name, number)
    • What you're asking for (service, date, time, party size — whatever applies)
    • What personal info you'll share (my name, my callback number, insurance if it applies — nothing more unless I've okayed it)

    Then get my explicit go-ahead via ask_user_input_v0. Do not dial until I've said yes.

On the call:

  • Lead with why you're calling, 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 — just state it plainly and move on to the ask.
  • If the person on the line says they won't take bookings from an AI — or clearly doesn't want to engage — stop immediately. Thank them, end the call, and tell me what happened so I can call myself.
  • If you're put on hold or land in a queue, give it two or three minutes. After that, hang up, follow whichever unreachable plan we settled on in step 4, and tell me where things stand. Don't sit on hold indefinitely — I'd rather know the line is backed up than have the call tied up waiting.
  • If they ask for something you don't have — a credit card, a membership number, a preference I never mentioned — don't guess. Tell them you'll need to check and call back. Then relay the question to me and wait.
  • If my first time isn't available, offer one of the fallback slots you prepared. If none of those work either, get their availability and bring it back to me — don't book a time I haven't seen.
  • Keep it brief. This is a phone call, not a conversation.

After the call:

Confirm what got booked — one line with the place, the service, the date and time — and add it to my calendar with the business address attached. Don't walk me through the whole call; I just need to know it's done and where to show up.

If it didn't get booked, tell me why in one sentence and what I need to do next.

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.