agentleFS
DevinoSolutionsDevinoSolutions/claude-plugins/skills/managing-bookings/SKILL.md

managing-bookings

Skill0 starsChanged 9 days agoMITView on GitHub

Reviews and changes the user's Caly bookings: lists upcoming, past, cancelled or unconfirmed meetings, looks one up by attendee or time, reschedules it to a free slot, or cancels it through Caly's two-step confirmation. Use when the user asks 'what meetings do I have tomorrow', 'show my bookings with Sam', 'move my call with Alex to Friday', 'reschedule the 3pm', 'cancel my meeting with this client', or 'who cancelled this week'. Reads freely; reschedule and cancel notify attendees, so they are confirmed first.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 9

    Very specific

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

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

    Every tool in this skill comes from the caly MCP server, the Caly connector, and is written here as caly:<tool>.

    line 13
  2. Very specific:

    Tools listed by name: call them directly, for example caly:list_bookings.

    line 15
  3. Very specific:

    Call caly:whoami for the time zone, then caly:list_bookings with the filters that match the question ("tomorrow" → status: ["upcoming"] …

    line 37
  4. Very specific:

    Follow pagination.hasNextPage with skip until the window is covered, or tell the user how many more there are.

    line 38
  5. Very specific:

    Call caly:find_available_slots for its event type and the new day, with bookingUidToReschedule set to the booking's uid.

    line 44
  6. Very specific:

    Call caly:reschedule_booking once.

    line 46
  7. Very specific:

    Call caly:cancel_booking with the bookingUid (and cancellationReason).

    line 51
  8. Very specific:

    Call caly:cancel_booking again with the SAME arguments plus the confirmToken, in a new call.

    line 53
  9. Distinctive:

    Never reschedule or cancel without the user's explicit yes to a summary that names the booking.

    line 57
  10. Very specific:

    Never pass a confirmToken before the user has seen the booking it cancels, and never reuse one for a different booking or different …

    line 58
  11. Distinctive:

    Always state the time zone next to every time you show.

    line 60

≈ “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
<!-- Generated from plugins/caly/skills/managing-bookings/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->

Caly: managing bookings

Find the right booking, then read, move or cancel it without surprising anyone.

Connecting and calling the tools

Every tool in this skill comes from the caly MCP server, the Caly connector, and is written here as caly:<tool>.

  • Tools listed by name: call them directly, for example caly:list_bookings.
  • Only caly:search_tools and caly:execute_typescript listed (Code Mode, the default): call caly:search_tools first, then call each tool inside caly:execute_typescript as external_<tool> (for example external_list_bookings); the program must return its result. Validation and confirmation are identical on both surfaces.
  • "Tool not found": switch to the Code Mode route instead of retrying the direct call.
  • No caly tools at all: Caly is not connected yet. Follow the setup-caly skill.

A refused call throws an Error whose message starts with its code, for example NOT_FOUND: or CONFIRMATION_REQUIRED:.

Tools you will use

  • caly:whoami: the account and its time zone.
  • caly:list_bookings: the user's bookings, filtered by status (upcoming, past, cancelled, unconfirmed, recurring), attendeeEmail, attendeeName, eventTypeId, or a window (afterStart, beforeEnd, UTC ISO 8601). Paginated with take (up to 100) and skip; check pagination.hasNextPage.
  • caly:get_booking: one booking by bookingUid, with attendees, hosts, location and any cancellation or rescheduling details.
  • caly:find_available_slots: free start times; set bookingUidToReschedule when moving a booking so its own slot counts as free.
  • caly:reschedule_booking: moves a booking to a new start (UTC ISO 8601), with an optional reschedulingReason. Caly creates a new booking with a new uid and notifies the attendees.
  • caly:cancel_booking: cancels a booking and notifies its attendees. It cannot be undone and takes two calls (see the workflow).

Booking results carry the UTC start and end plus startLocal and endLocal in the user's Caly time zone.

Workflow

Reviewing bookings

  1. Call caly:whoami for the time zone, then caly:list_bookings with the filters that match the question ("tomorrow" → status: ["upcoming"] plus a window; "with Sam" → attendeeName or attendeeEmail; "who cancelled" → status: ["cancelled"]).
  2. Follow pagination.hasNextPage with skip until the window is covered, or tell the user how many more there are.
  3. List each booking with its local time and zone, title, attendees and status. Call caly:get_booking only when the user wants one booking's details.

Rescheduling

  1. Identify exactly one booking and its uid. If several match, list them and ask which one.
  2. Call caly:find_available_slots for its event type and the new day, with bookingUidToReschedule set to the booking's uid. Use only a start time from the result.
  3. Confirm with the user: the booking, the old time, the new time (in the user's and the attendee's time zone), and that Caly will notify the attendees. Wait for an explicit yes.
  4. Call caly:reschedule_booking once. Report the new time and the new uid.

Cancelling

  1. Identify exactly one booking and its uid, and ask for a reason if the user has one.
  2. Call caly:cancel_booking with the bookingUid (and cancellationReason). The first call does not cancel: it returns CONFIRMATION_REQUIRED with a confirmToken (in Code Mode, a thrown Error whose message ends with that JSON). End that program there.
  3. Show the user which booking will be cancelled (title, time, attendees) and that the attendees will be emailed. Wait for an explicit yes.
  4. Call caly:cancel_booking again with the SAME arguments plus the confirmToken, in a new call. The token lasts 10 minutes; if it expired, start again at step 2. Report that the booking is cancelled.

Rules

  • Never reschedule or cancel without the user's explicit yes to a summary that names the booking.
  • Never pass a confirmToken before the user has seen the booking it cancels, and never reuse one for a different booking or different arguments.
  • Set cancelSubsequentBookings only when the user clearly asks to cancel the rest of a recurring series.
  • Always state the time zone next to every time you show.

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.