agentleFS
farukzahrafarukzahra/agent-skills/skills/google-calendar-mcp/SKILL.md

google-calendar-mcp

Skill0 starsChanged 2 months agoMITView on GitHub

Create, list, update, and delete Google Calendar events via the Cursor Google Calendar MCP plugin. Use when the user asks for a calendar reminder, event, appointment, or to schedule something on Google Calendar.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Put a copy-paste Cursor prompt in description so the user can reopen the chat task on that day:

    line 83
  2. Very specific:

    Prefer timeZone + ISO 8601 startTime/endTime over guessing offsets.

    line 94
  3. Distinctive:

    If MCP returns auth errors:

    line 98
  4. Very specific:

    Do not store OAuth tokens in the repo or ../secrets/.

    line 101
  5. Distinctive:

    Commit calendar event IDs as project config (ephemeral per user).

    line 110
  6. Distinctive:

    Ask the user to create events manually if MCP is connected and authenticated.

    line 111
  7. Distinctive:

    Use browser automation for Calendar when MCP works.

    line 112

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Google Calendar (MCP)

Manage Faruk's Google Calendar through the Cursor Google Calendar plugin MCP — no Python scripts or extra OAuth setup when the plugin is already connected.

MCP namespace

ItemValue
Namespaceplugin-google-calendar-google-calendar
AuthOAuth via Cursor plugin (user signs in once in Cursor)
Default calendarprimary (farukz@gmail.com)

Discover tools first: GetDynamicTools with namespace: plugin-google-calendar-google-calendar.

Available tools

ToolUse
list_calendarsList calendars and IDs
list_eventsEvents in a time range
get_eventVerify or read one event by ID
create_eventNew event or reminder
update_eventChange title, time, description
delete_eventRemove event
suggest_timeFind free slots
respond_to_eventAccept / decline invitations

Workflow — reminder or event

  1. Parse intent — title, date/time, all-day vs timed, timezone, optional agent prompt in description.
  2. Call GetDynamicTools for create_event schema (required: summary, startTime, endTime).
  3. Invoke via CallDynamicTool:
    • Namespace: plugin-google-calendar-google-calendar
    • Tool: create_event
  4. Verify with get_event using returned id.
  5. Report summary, date, htmlLink, and reminder settings to the user.

create_event patterns

All-day reminder (check something on a date)

{
  "summary": "Short title",
  "description": "Context + optional Cursor prompt for that day.",
  "allDay": true,
  "startTime": "2026-09-29",
  "endTime": "2026-09-30",
  "timeZone": "America/Los_Angeles",
  "overrideReminders": [
    { "method": "popup", "minutes": 1440 },
    { "method": "popup", "minutes": 0 }
  ]
}
  • All-day endTime is the next calendar day (exclusive end).
  • overrideReminders: minutes = how many minutes before the event. 0 = at start; 1440 = 24h before.

Timed meeting

{
  "summary": "Meeting title",
  "startTime": "2026-09-29T10:00:00-03:00",
  "endTime": "2026-09-29T11:00:00-03:00",
  "timeZone": "America/Sao_Paulo",
  "addGoogleMeetUrl": true
}

Description with agent prompt

Put a copy-paste Cursor prompt in description so the user can reopen the chat task on that day:

**Prompt para o agente (cole no Cursor):**
> Verifica o status do meu plano que expirou em 28/09/2026...

Timezones

  • User local: America/Sao_Paulo (UTC-3).
  • US Pacific expiry times: America/Los_Angeles (GMT-07:00).
  • Prefer timeZone + ISO 8601 startTime/endTime over guessing offsets.

Auth failures

If MCP returns auth errors:

  1. User must connect Google Calendar in Cursor Settings → MCP / Plugins.
  2. Do not store OAuth tokens in the repo or ../secrets/.
  3. Escalate once for OAuth consent or 2FA — then stop.

Alternative (not default)

odyssey4me/google-calendar on skills.sh uses a Python CLI + local OAuth. Prefer this MCP skill when the Cursor plugin is available; use odyssey4me only when MCP is unavailable.

Do not

  • Commit calendar event IDs as project config (ephemeral per user).
  • Ask the user to create events manually if MCP is connected and authenticated.
  • Use browser automation for Calendar when MCP works.

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.