Update to Caly

{
  "description": "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', or wants options to offer someone before booking. Read-only.",
  "included_files": [],
  "name": "finding-meeting-times",
  "skill_md_contents": "---\nname: finding-meeting-times\ndescription: \"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', or wants options to offer someone before booking. Read-only.\"\n---\n\n# Caly: finding meeting times\n\nAnswer \"when can this meeting happen\" from the user's live Caly event types, schedules and availability.\n\n## Connecting and calling the tools\n\nEvery tool in this skill comes from the `caly` MCP server, the Caly connector, and is written here as `caly:<tool>`.\n\n- Call each tool directly by name, for example `caly:find_available_slots`.\n- **No `caly` tools at all:** Caly is not connected yet. Add the server as shown in https://github.com/DevinoSolutions/mcp-servers/tree/main/caly#install; it signs in with OAuth on first use.\n\nA refused call throws an Error whose message starts with its code, for example `INVALID_INPUT:`.\n\n## Tools you will use\n\n- `caly:whoami`: the account this connection acts as, with its time zone, week start and default schedule. Takes no input.\n- `caly:list_event_types`: the user's event types (the bookable meeting kinds) with id, slug, title, length and booking URL, hidden ones included.\n- `caly:get_event_type`: one event type in full: lengths, locations, booking questions, buffers, minimum notice and schedule.\n- `caly:list_schedules`: the user's availability schedules: working hours per weekday, date overrides, time zone, and which one is the default.\n- `caly:find_available_slots`: the free start times for an event type between two dates (`eventTypeId`, `start`, `end`, optional `timeZone` and `duration`), grouped by date.\n\n## Workflow\n\n1. Call `caly:whoami` and `caly:list_event_types` together. Use the account's `timeZone` unless the user names another one, and say which time zone you are using.\n2. 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.\n3. Turn the user's range (\"next week\", \"Thursday afternoon\") into concrete `start` and `end` dates in that time zone. If no range is given, use the next 7 days.\n4. Call `caly:find_available_slots` with the event type id, the range and the time zone. If the user wants a length the event type allows (`lengthInMinutesOptions`), pass it as `duration`.\n5. Present a short list of options grouped by day, in the user's time zone, not every slot. If the user asked for a part of the day, filter to it.\n6. If there are no slots, call `caly:list_schedules` and explain why (outside working hours, a date override, minimum notice from `caly:get_event_type`), then offer the nearest free day.\n7. Offer next steps: book one of the slots with the `booking-meetings` skill, or share the event type's `bookingUrl` so the other person picks a time.\n\n## Rules\n\n- This skill only reads. Never call `caly:create_booking`, `caly:reschedule_booking` or `caly:cancel_booking` from it.\n- Report only slots that `caly:find_available_slots` returned. Never infer free time from the schedule alone; bookings and buffers can block it.\n- Always state the time zone next to every time you show.\n"
}