agentleFS
OpenLaborOpenLabor/openlabor/skills/google-calendar/SKILL.md

Google Calendar

Skill5 starsChanged 3 months agoMITView on GitHub

Create events, check availability, manage schedules, and coordinate meetings via Composio

  • Reads credentials

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create events, check availability, manage schedules, and coordinate meetings.

    line 17
  2. Distinctive:

    Always check availability before suggesting times

    line 94
  3. Distinctive:

    Add agenda in the description field

    line 96
  4. Distinctive:

    Check prospect's timezone before suggesting meeting times

    line 100
  5. Distinctive:

    Always use ISO 8601 datetime format (YYYY-MM-DDTHH:MM:SS)

    line 111
  6. Distinctive:

    Use "primary" as calendar_id for the main calendar

    line 113
  7. Distinctive:

    If you get a 400 "not connected" error, tell the user to connect Google Calendar in the Apps tab

    line 114
  8. Distinctive:

    Never expose credentials to the user

    line 115

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
<!-- openlabor-connector: google_calendar, api_key={{INTERNAL_API_KEY}}, employee={{EMPLOYEE_ID}}, base={{API_BASE_URL}} -->

Google Calendar

Create events, check availability, manage schedules, and coordinate meetings.

You have access to Google Calendar through the OpenLabor connector API.

How to Execute Calendar Actions

use google_calendar <TOOL_NAME> '<json_args>'

Events

Create an Event

  • Tool: GOOGLECALENDAR_CREATE_EVENT
  • Args: { "summary": "Team Meeting", "start_datetime": "2026-03-25T10:00:00", "end_datetime": "2026-03-25T11:00:00", "timezone": "America/New_York" }
  • Optional: "description", "location", "attendees" (array of emails)

Quick Add (natural language)

  • Tool: GOOGLECALENDAR_QUICK_ADD
  • Args: { "text": "Lunch with Sarah tomorrow at noon" }

List Events

  • Tool: GOOGLECALENDAR_FIND_EVENT
  • Args: { "timeMin": "2026-03-22T00:00:00Z", "timeMax": "2026-03-29T00:00:00Z" }
  • Optional: "query" (search text), "max_results", "order_by" ("startTime", "updated")

List Events Across All Calendars

  • Tool: GOOGLECALENDAR_EVENTS_LIST_ALL_CALENDARS
  • Args: { "time_min": "2026-03-22T00:00:00Z", "time_max": "2026-03-29T00:00:00Z" }

Get Event Details

  • Tool: GOOGLECALENDAR_EVENTS_GET
  • Args: { "event_id": "EVENT_ID" }

Update an Event

  • Tool: GOOGLECALENDAR_PATCH_EVENT
  • Args: { "event_id": "EVENT_ID", "calendar_id": "primary", "summary": "Updated Title", "start_time": "2026-03-25T14:00:00", "end_time": "2026-03-25T15:00:00" }

Delete an Event

  • Tool: GOOGLECALENDAR_DELETE_EVENT
  • Args: { "event_id": "EVENT_ID" }

Move an Event to Another Calendar

  • Tool: GOOGLECALENDAR_EVENTS_MOVE
  • Args: { "event_id": "EVENT_ID", "calendar_id": "primary", "destination": "CALENDAR_ID" }

Remove an Attendee

  • Tool: GOOGLECALENDAR_REMOVE_ATTENDEE
  • Args: { "event_id": "EVENT_ID", "attendee_email": "person@example.com" }

Availability

Find Free Slots

  • Tool: GOOGLECALENDAR_FIND_FREE_SLOTS
  • Args: { "time_min": "2026-03-22T09:00:00Z", "time_max": "2026-03-22T18:00:00Z", "items": [{ "id": "primary" }] }

Get Current Date/Time

  • Tool: GOOGLECALENDAR_GET_CURRENT_DATE_TIME
  • Args: { "timezone": "America/New_York" }

Calendar Management

List Calendars

  • Tool: GOOGLECALENDAR_LIST_CALENDARS
  • Args: {}

Get Calendar Details

  • Tool: GOOGLECALENDAR_GET_CALENDAR
  • Args: { "calendar_id": "primary" }

Create a New Calendar

  • Tool: GOOGLECALENDAR_DUPLICATE_CALENDAR
  • Args: { "summary": "Marketing Calendar" }

Scheduling Best Practices

For Meetings

  • Always check availability before suggesting times
  • Include timezone in all datetime values
  • Add agenda in the description field
  • Set attendees to notify them automatically

For SDRs

  • Check prospect's timezone before suggesting meeting times
  • Offer 2-3 time slots
  • Include meeting link and agenda in description
  • Set reminders for follow-up

For Email Secretaries

  • Manage the boss's calendar proactively
  • Block focus time and buffer between meetings
  • Coordinate across calendars for scheduling

Guidelines

  1. Always use ISO 8601 datetime format (YYYY-MM-DDTHH:MM:SS)
  2. Include timezone — don't assume UTC
  3. Use "primary" as calendar_id for the main calendar
  4. If you get a 400 "not connected" error, tell the user to connect Google Calendar in the Apps tab
  5. Never expose credentials to the user

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.