finding-meeting-times
Skill0 starsChanged 9 days agoMITView on GitHub
Finds open times to meet in Caly: lists the user's event types, reads their working-hours schedules, and returns the free slots for an event type over a date range, in the right time zone. Use when the user asks 'when am I free', 'find a time for a 30 minute call next week', 'what slots do I have on Thursday', 'which meeting types do I have', 'what are my working hours', 'send me times I can offer a client', or wants options before booking. Read-only.
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
- 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
6 rules. About 0 are common, 0 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
6
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:find_available_slots.
- Very specific: line 32
Call caly:whoami and caly:list_event_types together.
- Very specific: line 35
Call caly:find_available_slots with the event type id, the range and timeZone set to the zone you are reporting in, so the date keys line …
- Very specific: line 37
If there are no slots, call caly:list_schedules and caly:get_event_type and explain why (outside working hours, a date override, minimum …
- Very specific: line 44
Never present a UTC start as local time.
≈ “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/finding-meeting-times/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->Caly: finding meeting times
Answer "when can this meeting happen" from the user's live Caly event types, schedules and availability.
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:find_available_slots. - Only
caly:search_toolsandcaly:execute_typescriptlisted (Code Mode, the default): callcaly:search_toolsfirst, then call each tool insidecaly:execute_typescriptasexternal_<tool>(for exampleexternal_find_available_slots); the program mustreturnits result. Batch independent reads withPromise.all. 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: or NOT_FOUND:.
Tools you will use
caly:whoami: the account this connection acts as, with its time zone, week start and default schedule. Takes no input.caly:list_event_types: the user's event types (the bookable meeting kinds) with id, slug, title, length, allowed lengths (lengthInMinutesOptions) and booking URL, hidden ones included.caly:get_event_type: one event type in full: lengths, locations, booking questions, buffers, minimum notice and schedule.caly:list_schedules: the user's availability schedules: working hours per weekday, date overrides, time zone, and which one is the default.caly:find_available_slots: the free start times for an event type between two dates (eventTypeId,start,end, optionaltimeZoneandduration), grouped by date. Each slot carriesstartin UTC plusstartLocalandendLocalin the user's Caly time zone.
Workflow
- Call
caly:whoamiandcaly:list_event_typestogether. Use the account'stimeZoneunless the user names another one, and say which time zone you are using. - Pick the event type. Match the user's words to a title or length ("30 minute call" → the 30-minute type). If two could fit, or none does, list the event types and ask which one.
- Turn the user's range ("next week", "Thursday afternoon") into concrete
startandendvalues. A bare date (2026-10-01) means the start or end of that day; otherwise pass a UTC ISO 8601 datetime. If no range is given, use the next 7 days. - Call
caly:find_available_slotswith the event type id, the range andtimeZoneset to the zone you are reporting in, so the date keys line up with the user's days. If the user wants a length the event type allows (lengthInMinutesOptions), set it asduration. - Present a short list of options grouped by day, using
startLocal(or the requested zone), not every slot. If the user asked for a part of the day, filter to it. - If there are no slots, call
caly:list_schedulesandcaly:get_event_typeand explain why (outside working hours, a date override, minimum notice, buffers), then offer the nearest day that has free slots. - Offer next steps: book one of the slots with the
booking-meetingsskill, or share the event type'sbookingUrlso the other person picks a time.
Rules
- This skill only reads. Never call
caly:create_booking,caly:reschedule_bookingorcaly:cancel_bookingfrom it. - Report only slots that
caly:find_available_slotsreturned. Never infer free time from the schedule alone; existing bookings and buffers can block it. - Never present a UTC
startas local time. 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.

