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.
In this repository66 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adding-uptime-monitorsSkill
- analyzing-page-performanceSkill
- booking-meetingsSkill
- building-onboarding-workflowsSkill
- building-study-guidesSkill
- capturing-tasksSkill
- capturing-web-pagesSkill
- chasing-unpaid-invoicesSkill
- checking-domain-connectionsSkill
- checking-email-deliverabilitySkill
- checking-notification-deliverySkill
- checking-uptime-statusSkill
- cleaning-up-bookkeepingSkill
- connecting-customer-domainsSkill
- discussing-buildsSkill
- drafting-invoicesSkill
- drafting-social-postsSkill
- editing-demosSkill
- editing-page-draftsSkill
- extracting-document-textSkill
- finding-meeting-timesSkill
- handling-flaky-changesSkill
- investigating-tasksSkill
- making-demo-videosSkill
- managing-content-calendarSkill
- managing-demosSkill
- managing-voice-librarySkill
- planning-revisionSkill
- preflighting-domainsSkill
- publishing-pagesSkill
- reading-financial-reportsSkill
- reading-text-aloudSkill
- reading-web-pagesSkill
- reporting-snapvisor-usageSkill
- researching-course-materialSkill
- researching-summary-librarySkill
- responding-to-incidentsSkill
- reviewing-email-performanceSkill
- reviewing-notification-workflowsSkill
- reviewing-social-performanceSkill
- reviewing-visual-buildsSkill
- reviewing-workloadSkill
- searching-getitdone-api-docsSkill
- sending-email-campaignsSkill
- sending-notificationsSkill
- setup-bioflowSkill
- setup-calySkill
- setup-demofySkill
- setup-dodomainSkill
- setup-getitdoneSkill
- setup-notiflySkill
- setup-postifySkill
- setup-sendlySkill
- setup-shortySkill
- setup-snapvisorSkill
- setup-superbooksSkill
- setup-unotesSkill
- setup-upapiSkill
- setup-uptimelySkill
- The first 60 shown.
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
- Very specific: line 13
Every tool in this skill comes from the caly MCP server, the Caly connector, and is written here as caly:<tool>.
- Very specific: line 15
Tools listed by name: call them directly, for example caly:list_bookings.
- Very specific: line 37
Call caly:whoami for the time zone, then caly:list_bookings with the filters that match the question ("tomorrow" → status: ["upcoming"] …
- Very specific: line 38
Follow pagination.hasNextPage with skip until the window is covered, or tell the user how many more there are.
- Very specific: line 44
Call caly:find_available_slots for its event type and the new day, with bookingUidToReschedule set to the booking's uid.
- Very specific: line 46
Call caly:reschedule_booking once.
- Very specific: line 51
Call caly:cancel_booking with the bookingUid (and cancellationReason).
- Very specific: line 53
Call caly:cancel_booking again with the SAME arguments plus the confirmToken, in a new call.
- Distinctive: line 57
Never reschedule or cancel without the user's explicit yes to a summary that names the booking.
- Very specific: line 58
Never pass a confirmToken before the user has seen the booking it cancels, and never reuse one for a different booking or different …
- Distinctive: line 60
Always state the time zone next to every time you show.
≈ “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.
Files
<!-- 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_toolsandcaly:execute_typescriptlisted (Code Mode, the default): callcaly:search_toolsfirst, then call each tool insidecaly:execute_typescriptasexternal_<tool>(for exampleexternal_list_bookings); the program mustreturnits 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
calytools at all: Caly is not connected yet. Follow thesetup-calyskill.
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 bystatus(upcoming, past, cancelled, unconfirmed, recurring),attendeeEmail,attendeeName,eventTypeId, or a window (afterStart,beforeEnd, UTC ISO 8601). Paginated withtake(up to 100) andskip; checkpagination.hasNextPage.caly:get_booking: one booking bybookingUid, with attendees, hosts, location and any cancellation or rescheduling details.caly:find_available_slots: free start times; setbookingUidToReschedulewhen moving a booking so its own slot counts as free.caly:reschedule_booking: moves a booking to a newstart(UTC ISO 8601), with an optionalreschedulingReason. Caly creates a new booking with a newuidand 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
- Call
caly:whoamifor the time zone, thencaly:list_bookingswith the filters that match the question ("tomorrow" →status: ["upcoming"]plus a window; "with Sam" →attendeeNameorattendeeEmail; "who cancelled" →status: ["cancelled"]). - Follow
pagination.hasNextPagewithskipuntil the window is covered, or tell the user how many more there are. - List each booking with its local time and zone, title, attendees and status. Call
caly:get_bookingonly when the user wants one booking's details.
Rescheduling
- Identify exactly one booking and its
uid. If several match, list them and ask which one. - Call
caly:find_available_slotsfor its event type and the new day, withbookingUidToRescheduleset to the booking'suid. Use only a start time from the result. - 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.
- Call
caly:reschedule_bookingonce. Report the new time and the newuid.
Cancelling
- Identify exactly one booking and its
uid, and ask for a reason if the user has one. - Call
caly:cancel_bookingwith thebookingUid(andcancellationReason). The first call does not cancel: it returnsCONFIRMATION_REQUIREDwith aconfirmToken(in Code Mode, a thrown Error whose message ends with that JSON). End that program there. - Show the user which booking will be cancelled (title, time, attendees) and that the attendees will be emailed. Wait for an explicit yes.
- Call
caly:cancel_bookingagain with the SAME arguments plus theconfirmToken, 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
confirmTokenbefore the user has seen the booking it cancels, and never reuse one for a different booking or different arguments. - Set
cancelSubsequentBookingsonly when the user clearly asks to cancel the rest of a recurring series. - Always state the time zone next to every time you show.
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
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.

