Update to Caly

{
  "description": "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.",
  "included_files": [],
  "name": "booking-meetings",
  "skill_md_contents": "---\nname: booking-meetings\ndescription: \"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.\"\n---\n\n# Caly: booking meetings\n\nCreate one confirmed booking in Caly, with the right event type, time, time zone and attendee.\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:create_booking`.\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.\n- `caly:list_event_types`: the user's event types with id, title and length.\n- `caly:get_event_type`: one event type in full, including `bookingFields` (the booking questions an attendee must answer).\n- `caly:find_available_slots`: free start times for an event type between two dates.\n- `caly:create_booking`: books the meeting (`eventTypeId`, `start` as UTC ISO 8601, `attendee` with `name`, `timeZone` and usually `email`, optional `guests`, `lengthInMinutes`, `bookingFieldsResponses`). Caly sends the confirmation emails and calendar invites.\n\n## Workflow\n\n1. Call `caly:whoami` and `caly:list_event_types`. Pick the event type from the user's words; ask if it is ambiguous.\n2. Collect the attendee: name, email, and their time zone. If the user does not know the attendee's time zone, ask; do not assume it is the user's.\n3. Call `caly:get_event_type` and read `bookingFields`. Ask the user for any required answer you do not have yet.\n4. Call `caly:find_available_slots` for 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.\n5. 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.\n6. After the yes, call `caly:create_booking` once with the slot's `start` in UTC and the collected details.\n7. Report the result: the booking's title, time, status (some event types need the host to confirm, so it may be unconfirmed), meeting URL or location, and its `uid`, which reschedules and cancellations need.\n\n## Rules\n\n- Never call `caly:create_booking` without the user's explicit confirmation of the summary in step 5.\n- Never retry a failed `caly:create_booking` blindly; read the error, fix the input, and confirm again if anything changed.\n- Never invent an attendee email. Book only with details the user gave.\n- To move or cancel an existing meeting, use the `managing-bookings` skill instead of creating a second booking.\n"
}