agentleFS
AbdullahMalik17AbdullahMalik17/Digital-FTE/.claude/skills/managing-calendar/SKILL.md

managing-calendar

Skill12 starsChanged 36 days agoMITView on GitHub

Manage Google Calendar events via MCP server. Use when scheduling meetings, checking availability, listing events, or processing meeting requests from emails. NOT when managing Outlook calendars (different API).

  • Reads credentials

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All times are stored in UTC by default.

    line 31
  2. Distinctive:

    Create OAuth credentials (Desktop app)

    line 115
  3. Distinctive:

    Not typically a concern for personal use.

    line 132
  4. Very specific:

    All operations logged via utils/audit_logger.py:

    line 136

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

FastMCP server for Google Calendar management.

Quick Start

# Start MCP server
python src/mcp_servers/google_calendar_server.py

MCP Tools

  1. list_events(calendar_id, max_results, time_min, time_max) - List upcoming events
  2. create_event(summary, start_time, end_time, description, location, attendees) - Create new event
  3. update_event(event_id, summary, description, location) - Modify existing event
  4. delete_event(event_id) - Cancel event

Production Gotchas

Timezone Handling

All times are stored in UTC by default. Client must convert:

# Server always uses UTC
'start': {
    'dateTime': start_time,
    'timeZone': 'UTC',  # Always UTC internally
}

# Convert for user display
from datetime import timezone
local_time = utc_time.astimezone(timezone.utc)

ISO Format Required

Time parameters MUST be ISO 8601 format:

# ✓ CORRECT
create_event(start_time="2026-01-30T10:00:00")

# ✗ WRONG - Natural language
create_event(start_time="tomorrow 10am")

# ✗ WRONG - Missing T separator
create_event(start_time="2026-01-30 10:00:00")

Calendar ID Conventions

  • 'primary' - User's main calendar (default)
  • Email address - Shared calendar access
  • Calendar ID from Google - For secondary calendars

Attendees Are Optional But Important

Omitting attendees creates a private event:

# Private event (no notifications)
create_event(summary="Focus time", start_time=..., end_time=...)

# Meeting with notifications
create_event(
    summary="Team sync",
    start_time=...,
    end_time=...,
    attendees=["alice@example.com", "bob@example.com"]
)

Separate Token File

Calendar uses different OAuth token than Gmail:

  • token_calendar.json - Calendar access
  • token.json / token_email.json - Gmail access

Event ID Required for Updates

You must first retrieve the event ID before updating:

# ✗ FAILS - No ID
update_event(summary="New title")

# ✓ WORKS - Get ID from list_events first
events = list_events()
event_id = events[0]['id']
update_event(event_id=event_id, summary="New title")

Configuration

Required in config/:

  • credentials.json - Google OAuth credentials
  • token_calendar.json - Calendar OAuth token

OAuth Scopes:

SCOPES = ['https://www.googleapis.com/auth/calendar']

Setup

1. Enable Google Calendar API

  1. Go to Google Cloud Console
  2. Enable "Google Calendar API"
  3. Create OAuth credentials (Desktop app)
  4. Download as config/credentials.json

2. First Run

python src/mcp_servers/google_calendar_server.py

This opens a browser for OAuth consent. Token saves to token_calendar.json.

Rate Limits

Google Calendar API limits:

  • 1,000,000 queries per day
  • 500 queries per 100 seconds per user

Not typically a concern for personal use.

Audit Logging

All operations logged via utils/audit_logger.py:

  • Domain: AuditDomain.PERSONAL
  • Actions: calendar.list_events, calendar.create_event, etc.

Verification

Run: python scripts/verify.py

Related Skills

  • watching-gmail - Detect meeting requests in emails
  • digital-fte-orchestrator - Process calendar-related tasks

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.