Google Calendar Skill logo

Google Calendar Skill

Community
zeenie-ai
google-calendar-skill

Create, list, update, and delete Google Calendar events. Supports attendees, reminders, and recurring events.

Overview

Publisherzeenie-ai
RepositoryOpenCompany
Skill namegoogle-calendar-skill
Stars
912
Forks
137
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by zeenie-ai on GitHub. Read the source before you install it.

Installation

Install the Google Calendar Skill AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/zeenie-ai/OpenCompany.git /tmp/OpenCompany
mkdir -p .claude/skills
cp -r /tmp/OpenCompany/server/skills/productivity_agent/google-calendar-skill .claude/skills/google-calendar-skill
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Google Calendar Skill in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Google Calendar Skill on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Google Calendar Skill is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Google Calendar Skill

Manage Google Calendar events - create, list, update, and delete.

Tool: google_calendar

Consolidated Google Calendar tool with operation parameter.

Operations

OperationDescriptionRequired Fields
createCreate a new eventtitle, start_time, end_time
listList events in date range(none, defaults to this week)
updateUpdate an existing eventevent_id
deleteDelete an eventevent_id

create - Create a new event

FieldTypeRequiredDescription
operationstringYesMust be "create"
titlestringYesEvent title/summary
start_timestringYesStart time in ISO 8601 format
end_timestringYesEnd time in ISO 8601 format
descriptionstringNoEvent description
locationstringNoEvent location
attendeesstringNoComma-separated email addresses
reminder_minutesintegerNoMinutes before event for reminder
timezonestringNoTimezone (default: user's timezone)

Example - Simple event:

json
{
  "operation": "create",
  "title": "Team Meeting",
  "start_time": "2024-02-01T14:00:00",
  "end_time": "2024-02-01T15:00:00",
  "description": "Weekly team sync"
}

Example - Event with attendees:

json
{
  "operation": "create",
  "title": "Project Review",
  "start_time": "2024-02-01T10:00:00",
  "end_time": "2024-02-01T11:30:00",
  "location": "Conference Room A",
  "attendees": "alice@example.com,bob@example.com",
  "reminder_minutes": 30
}

list - List events in date range

FieldTypeRequiredDescription
operationstringYesMust be "list"
start_datestringNoStart date (ISO 8601, default: today)
end_datestringNoEnd date (ISO 8601, default: 7 days ahead)
max_resultsintegerNoMaximum results (default: 10, max: 100)
calendar_idstringNoCalendar ID (default: primary)

Example:

json
{
  "operation": "list",
  "start_date": "2024-02-01",
  "end_date": "2024-02-07",
  "max_results": 20
}

update - Update an existing event

FieldTypeRequiredDescription
operationstringYesMust be "update"
event_idstringYesEvent ID to update
update_titlestringNoNew title
update_start_timestringNoNew start time
update_end_timestringNoNew end time
update_descriptionstringNoNew description
update_locationstringNoNew location
update_attendeesstringNoNew attendees (replaces existing)

Example:

json
{
  "operation": "update",
  "event_id": "abc123xyz",
  "update_title": "Updated Team Meeting",
  "update_start_time": "2024-02-01T15:00:00",
  "update_end_time": "2024-02-01T16:00:00"
}

delete - Delete an event

FieldTypeRequiredDescription
operationstringYesMust be "delete"
event_idstringYesEvent ID to delete
calendar_idstringNoCalendar ID (default: primary)

Example:

json
{
  "operation": "delete",
  "event_id": "abc123xyz"
}

Date/Time Formats

  • ISO 8601: 2024-02-01T14:00:00 (local time)
  • With timezone: 2024-02-01T14:00:00-05:00 (EST)
  • UTC: 2024-02-01T19:00:00Z
  • Date only: 2024-02-01 (all-day event)

Common Workflows

  1. Schedule a meeting: Create event with attendees, they receive invites
  2. Check availability: List events for a date range
  3. Reschedule: Update event with new times
  4. Cancel meeting: Delete the event

Setup Requirements

  1. Connect Calendar node to AI Agent's input-tools handle
  2. Authenticate with Google Workspace in Credentials Modal
  3. Ensure Calendar API scopes are authorized

Frequently asked questions

What does the Google Calendar Skill AI skill do?

Create, list, update, and delete Google Calendar events. Supports attendees, reminders, and recurring events.

Why use Google Calendar Skill on TypingMind?

Because you install it once and use it with any model. Google Calendar Skill is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Google Calendar Skill in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/zeenie-ai/OpenCompany/tree/main/server/skills/productivity_agent/google-calendar-skill. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Google Calendar Skill?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Google Calendar Skill?

As many as you like. As long as a model supports skills, you can use Google Calendar Skill with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Google Calendar Skill AI skill free?

Yes. It is published on GitHub by zeenie-ai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇