booking-meetings
Skill0 starsChanged 9 days agoMITView on GitHub
Books a meeting in Caly on one of the user's event types: finds a free slot, collects the attendee's details and the event type's required booking questions, confirms with the user, then creates the booking so Caly sends the invites. Use when the user asks 'book a call with Sam on Tuesday at 3', 'schedule a 30 minute intro with alex@example.com', 'put a meeting on my calendar with this client', or picks a slot found earlier. Writes data and emails the attendee, so it always confirms first.
In this repository66 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adding-uptime-monitorsSkill
- analyzing-page-performanceSkill
- 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-bookingsSkill
- 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
10 rules. About 0 are common, 2 are distinctive, and 8 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.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Create one booking in Caly, with the right event type, time, time zone and attendee.
- 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:create_booking.
- Very specific: line 33
Call caly:whoami and caly:list_event_types.
- Very specific: line 35
Call caly:get_event_type and read bookingFields.
- Very specific: line 36
Call caly:find_available_slots for the requested day.
- Very specific: line 38
After the yes, call caly:create_booking once with the slot's UTC start and the collected details.
- Very specific: line 43
Never call caly:create_booking without the user's explicit confirmation of the summary in step 5.
- Very specific: line 44
Never retry a failed caly:create_booking blindly.
- Distinctive: line 45
Never invent an attendee email.
≈ “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/booking-meetings/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->Caly: booking meetings
Create one booking in Caly, with the right event type, time, time zone and attendee.
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:create_booking. - Only
caly:search_toolsandcaly:execute_typescriptlisted (Code Mode, the default): callcaly:search_toolsfirst, then call each tool insidecaly:execute_typescriptasexternal_<tool>(for exampleexternal_create_booking); 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 VALIDATION_FAILED:.
Tools you will use
caly:whoami: the account this connection acts as, with its time zone.caly:list_event_types: the user's event types with id, title, length and allowed lengths.caly:get_event_type: one event type in full, includingbookingFields(the booking questions an attendee must answer).caly:find_available_slots: free start times for an event type between two dates, each with a UTCstartand a localstartLocal.caly:create_booking: books the meeting (eventTypeId,startas UTC ISO 8601,attendeewithname,timeZoneand usuallyemail, optionalphoneNumber,language,guests,lengthInMinutes,bookingFieldsResponses). Caly sends the confirmation emails and calendar invites.caly:list_bookings: only to check whether an earlier attempt already created the booking (see Rules).
Workflow
- Call
caly:whoamiandcaly:list_event_types. Pick the event type from the user's words; ask if it is ambiguous. - Collect the attendee: name, email, and their time zone (IANA, for example
America/New_York). If the user does not know the attendee's time zone, ask; do not assume it is the user's. - Call
caly:get_event_typeand readbookingFields. Ask the user for any required answer you do not have yet. - Call
caly:find_available_slotsfor the requested day. Use only a start time that appears in the result. If the requested time is not free, say so and offer the nearest free slots instead. - Show a summary and wait for an explicit yes: event type, date and time in both the user's and the attendee's time zone, length, attendee name and email, guests, and that Caly will email the invite.
- After the yes, call
caly:create_bookingonce with the slot's UTCstartand the collected details. - Report the result: the booking's title, time (from
startLocal, with the zone), status (some event types need the host to confirm, so it may be unconfirmed), meeting URL or location, and itsuid, which reschedules and cancellations need.
Rules
- Never call
caly:create_bookingwithout the user's explicit confirmation of the summary in step 5. - Never retry a failed
caly:create_bookingblindly. Read the error, fix the input, and confirm again if anything changed. After aTIMEOUTorUPSTREAM_ERROR, checkcaly:list_bookingsfor that attendee and time before trying again, so the attendee is not booked twice. - Never invent an attendee email. Book only with details the user gave.
- To move or cancel an existing meeting, use the
managing-bookingsskill instead of creating a second booking.
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.

