agentleFS
DevinoSolutionsDevinoSolutions/claude-plugins/skills/booking-meetings/SKILL.md

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.

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
  1. Distinctive:

    Create one booking in Caly, with the right event type, time, time zone and attendee.

    line 9
  2. Very specific:

    Every tool in this skill comes from the caly MCP server, the Caly connector, and is written here as caly:<tool>.

    line 13
  3. Very specific:

    Tools listed by name: call them directly, for example caly:create_booking.

    line 15
  4. Very specific:

    Call caly:whoami and caly:list_event_types.

    line 33
  5. Very specific:

    Call caly:get_event_type and read bookingFields.

    line 35
  6. Very specific:

    Call caly:find_available_slots for the requested day.

    line 36
  7. Very specific:

    After the yes, call caly:create_booking once with the slot's UTC start and the collected details.

    line 38
  8. Very specific:

    Never call caly:create_booking without the user's explicit confirmation of the summary in step 5.

    line 43
  9. Very specific:

    Never retry a failed caly:create_booking blindly.

    line 44
  10. Distinctive:

    Never invent an attendee email.

    line 45

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- 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_tools and caly:execute_typescript listed (Code Mode, the default): call caly:search_tools first, then call each tool inside caly:execute_typescript as external_<tool> (for example external_create_booking); the program must return its 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 caly tools at all: Caly is not connected yet. Follow the setup-caly skill.

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, including bookingFields (the booking questions an attendee must answer).
  • caly:find_available_slots: free start times for an event type between two dates, each with a UTC start and a local startLocal.
  • caly:create_booking: books the meeting (eventTypeId, start as UTC ISO 8601, attendee with name, timeZone and usually email, optional phoneNumber, 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

  1. Call caly:whoami and caly:list_event_types. Pick the event type from the user's words; ask if it is ambiguous.
  2. 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.
  3. Call caly:get_event_type and read bookingFields. Ask the user for any required answer you do not have yet.
  4. 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.
  5. 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.
  6. After the yes, call caly:create_booking once with the slot's UTC start and the collected details.
  7. 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 its uid, which reschedules and cancellations need.

Rules

  • Never call caly:create_booking without the user's explicit confirmation of the summary in step 5.
  • Never retry a failed caly:create_booking blindly. Read the error, fix the input, and confirm again if anything changed. After a TIMEOUT or UPSTREAM_ERROR, check caly:list_bookings for 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-bookings skill instead of creating a second booking.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.