Agent skill

Google Calendar Automation

by aiskillstore in aiskillstore/marketplace

Lightweight Google Calendar integration with standalone OAuth authentication.

Apache-2.0Auto-check passedBackend & APIs

Install Google Calendar Automation

skills CLI

$ npx skills add aiskillstore/marketplace --skill google-calendar-automation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install aiskillstore/marketplace google-calendar-automation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sickn33/google-calendar-automation .claude/skills/google-calendar-automation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "google-calendar-automation" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/sickn33/google-calendar-automation into .claude/skills/google-calendar-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-calendar-automation", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/aiskillstore/marketplace/tree/main/skills/sickn33/google-calendar-automation

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add aiskillstore/marketplace --skill google-calendar-automation -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install aiskillstore/marketplace google-calendar-automation --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/sickn33/google-calendar-automation .agents/skills/google-calendar-automation && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "google-calendar-automation" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/sickn33/google-calendar-automation into .agents/skills/google-calendar-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-calendar-automation", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add aiskillstore/marketplace --skill google-calendar-automation -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install aiskillstore/marketplace google-calendar-automation --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/sickn33/google-calendar-automation .cursor/skills/google-calendar-automation && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "google-calendar-automation" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/sickn33/google-calendar-automation into .cursor/skills/google-calendar-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-calendar-automation", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/aiskillstore/marketplace.git --path skills/sickn33/google-calendar-automation

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add aiskillstore/marketplace --skill google-calendar-automation -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install aiskillstore/marketplace google-calendar-automation --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/sickn33/google-calendar-automation .gemini/skills/google-calendar-automation && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "google-calendar-automation" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/sickn33/google-calendar-automation into .gemini/skills/google-calendar-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-calendar-automation", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install aiskillstore/marketplace google-calendar-automation

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add aiskillstore/marketplace --skill google-calendar-automation -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/sickn33/google-calendar-automation .github/skills/google-calendar-automation && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "google-calendar-automation" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/sickn33/google-calendar-automation into .github/skills/google-calendar-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-calendar-automation", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add aiskillstore/marketplace --skill google-calendar-automation -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install aiskillstore/marketplace google-calendar-automation --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/sickn33/google-calendar-automation .opencode/skills/google-calendar-automation && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "google-calendar-automation" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/sickn33/google-calendar-automation into .opencode/skills/google-calendar-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-calendar-automation", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: google-calendar-automation
GitHub stars: 433
Used in: 3 other repos
Token cost: ~1.3k tokens
SKILL.md length: 248 words
Files: 2
Skills in repo: 1,044
Repo updated: Oct 10, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Lightweight Google Calendar integration with standalone OAuth authentication.

Tasks that involve OAuth and OpenID Connect
SKILL.md covers When to Use, First-Time Setup, Commands and Date/Time Format, plus 3 more sections
Calls python

What it does

Google Calendar Automation is an agent skill from aiskillstore/marketplace. Lightweight Google Calendar integration with standalone OAuth authentication. No MCP server required.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `skill-report.json`).

It sits in Backend & APIs, covering OAuth and OpenID Connect. It works with Google Calendar and Model Context Protocol. The repository describes itself as: Security-audited skills for Claude, Codex & Claude Code. One-click install, quality verified. The licence is Apache-2.0.

When your agent uses it

Tasks that involve OAuth and OpenID Connect

Example prompts

“/google-calendar-automation”

Requirements

Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit 44923f3. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Google Calendar Automation loads about 1.3k tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 248 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~32
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from aiskillstore/marketplace at commit 44923f3, republished under its Apache-2.0 licence (© aiskillstore). 248 words, ~1,254 tokens.

Download SKILL.mdSave it as .claude/skills/google-calendar-automation/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: google-calendar-automation
description: Lightweight Google Calendar integration with standalone OAuth authentication. No MCP server required.
license: Apache-2.0
risk: critical
source: community
metadata.author: sanjay3290
metadata.version: 1.0

Google Calendar

Lightweight Google Calendar integration with standalone OAuth authentication. No MCP server required.

⚠️ Requires Google Workspace account. Personal Gmail accounts are not supported.

When to Use

You need to list, create, inspect, or update Google Calendar events from local scripts.
The task requires OAuth-backed calendar automation without standing up an MCP server.
You need quick operational access to calendars, schedules, attendees, or event details in a Workspace environment.

First-Time Setup

Authenticate with Google (opens browser):

bash

python scripts/auth.py login

Check authentication status:

bash

python scripts/auth.py status

Logout when needed:

bash

python scripts/auth.py logout

Commands

All operations via scripts/gcal.py. Auto-authenticates on first use if not logged in.

List Calendars

bash

python scripts/gcal.py list-calendars

List Events

bash

# List events from primary calendar (default: next 30 days)
python scripts/gcal.py list-events

# List events with specific time range
python scripts/gcal.py list-events --time-min 2024-01-15T00:00:00Z --time-max 2024-01-31T23:59:59Z

# List events from a specific calendar
python scripts/gcal.py list-events --calendar "work@example.com"

# Limit results
python scripts/gcal.py list-events --max-results 10

Get Event Details

bash

python scripts/gcal.py get-event EVENT_ID
python scripts/gcal.py get-event EVENT_ID --calendar "work@example.com"

Create Event

bash

# Basic event
python scripts/gcal.py create-event "Team Meeting" "2024-01-15T10:00:00Z" "2024-01-15T11:00:00Z"

# Event with description and location
python scripts/gcal.py create-event "Team Meeting" "2024-01-15T10:00:00Z" "2024-01-15T11:00:00Z" \
    --description "Weekly sync" --location "Conference Room A"

# Event with attendees
python scripts/gcal.py create-event "Team Meeting" "2024-01-15T10:00:00Z" "2024-01-15T11:00:00Z" \
    --attendees user1@example.com user2@example.com

# Event on specific calendar
python scripts/gcal.py create-event "Meeting" "2024-01-15T10:00:00Z" "2024-01-15T11:00:00Z" \
    --calendar "work@example.com"

Update Event

bash

# Update event title
python scripts/gcal.py update-event EVENT_ID --summary "New Title"

# Update event time
python scripts/gcal.py update-event EVENT_ID --start "2024-01-15T14:00:00Z" --end "2024-01-15T15:00:00Z"

# Update multiple fields
python scripts/gcal.py update-event EVENT_ID \
    --summary "Updated Meeting" --description "New agenda" --location "Room B"

# Update attendees
python scripts/gcal.py update-event EVENT_ID --attendees user1@example.com user3@example.com

Delete Event

bash

python scripts/gcal.py delete-event EVENT_ID
python scripts/gcal.py delete-event EVENT_ID --calendar "work@example.com"

Find Free Time

Find the first available slot for a meeting with specified attendees:

bash

# Find 30-minute slot for yourself
python scripts/gcal.py find-free-time \
    --attendees me \
    --time-min "2024-01-15T09:00:00Z" \
    --time-max "2024-01-15T17:00:00Z" \
    --duration 30

# Find 60-minute slot with multiple attendees
python scripts/gcal.py find-free-time \
    --attendees me user1@example.com user2@example.com \
    --time-min "2024-01-15T09:00:00Z" \
    --time-max "2024-01-19T17:00:00Z" \
    --duration 60

Respond to Event Invitation

bash

# Accept an invitation
python scripts/gcal.py respond-to-event EVENT_ID accepted

# Decline an invitation
python scripts/gcal.py respond-to-event EVENT_ID declined

# Mark as tentative
python scripts/gcal.py respond-to-event EVENT_ID tentative

# Respond without notifying organizer
python scripts/gcal.py respond-to-event EVENT_ID accepted --no-notify

Date/Time Format

All times use ISO 8601 format with timezone:

UTC: 2024-01-15T10:30:00Z
With offset: 2024-01-15T10:30:00-05:00 (EST)

Calendar ID Format

Primary calendar: Use primary or omit the --calendar flag
Other calendars: Use the calendar ID from list-calendars (usually an email address)

Token Management

Tokens stored securely using the system keyring:

macOS: Keychain
Windows: Windows Credential Locker
Linux: Secret Service API (GNOME Keyring, KDE Wallet, etc.)

Service name: google-calendar-skill-oauth

Tokens are automatically refreshed when expired using Google's cloud function.

Limitations

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Files

SKILL.md and 1 other file in skills/sickn33/google-calendar-automation of aiskillstore/marketplace.

SKILL.md
skill-report.json

Open the folder on GitHubat commit 44923f3

Used in 3 other repositories

We found 16 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in aiskillstore/marketplace, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Google Calendar Automation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Google Calendar Automation compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Google Calendar Automation this skillaiskillstore/marketplace	433	3 repos	~1.3k	Automated safety check: Pass	Apache-2.0	yesterday
OneCLI Gatewaynanocoai/nanoclaw	31k	—	~856	Automated safety check: Pass	MIT	today
Google Calendarsanjay3290/ai-skills	432	—	~1.2k	Automated safety check: Pass	Apache-2.0	1 mo ago
Xquik MCPXquik-dev/x-twitter-scraper	211	1 repos	~997	Automated safety check: Pass	MIT	today
Neo4j Aura Agent Skillneo4j-contrib/neo4j-skills	114	—	~4.4k	Automated safety check: Notes	MIT	yesterday
Frontmcp Auth UIagentfront/frontmcp	146	—	~3.7k	Automated safety check: Pass	Apache-2.0	today

Similar skills

OneCLI Gateway
nanocoai/nanoclaw
Explains how to call external APIs through the OneCLI proxy, which injects stored credentials into outgoing HTTPS requests so the agent never handles keys.
31k GitHub stars~856 tokensUpdated today
Backend & APIsAuto-check passed
Google Calendar
sanjay3290/ai-skills
Interact with Google Calendar - list calendars, view events, create/update/delete events, and find free time.
432 GitHub stars~1.2k tokensUpdated 1 mo ago
Backend & APIsAuto-check passed
Xquik MCP
Xquik-dev/x-twitter-scraper
Connect, verify, and troubleshoot Xquik's remote MCP server.
211 GitHub starsUsed in 1 repo~997 tokens
Backend & APIsAuto-check passed
Neo4j Aura Agent Skill
neo4j-contrib/neo4j-skills
Manages Neo4j Aura Agents via the v2beta1 REST API — create, list, get, update, delete, and invoke Aura agents backed by an AuraDB instance.
114 GitHub stars~4.4k tokensUpdated yesterday
Backend & APIsAuto-check: notes
Frontmcp Auth UI
agentfront/frontmcp
A skill your agent uses when customizing, branding, or replacing the built-in FrontMCP OAuth pages (the login, consent, federated-select, incremental-authorization, and error pages) with your own…
146 GitHub stars~3.7k tokensUpdated today
Backend & APIsAuto-check passed
Entra Agent Id
microsoft/GitHub-Copilot-for-Azure
Official
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant)…
255 GitHub starsUsed in 2 repos~4k tokens
Backend & APIsAuto-check passed

Questions about Google Calendar Automation

What does Google Calendar Automation do?

Lightweight Google Calendar integration with standalone OAuth authentication. Google Calendar Automation is an agent skill from aiskillstore/marketplace. Lightweight Google Calendar integration with standalone OAuth authentication.

When should I use Google Calendar Automation?

Google Calendar Automation fits situations like: tasks that involve OAuth and OpenID Connect.

How do I install Google Calendar Automation in Claude Code?

Run `npx skills add aiskillstore/marketplace --skill google-calendar-automation -a claude-code`. Or copy the skill folder (skills/sickn33/google-calendar-automation in aiskillstore/marketplace) into .claude/skills/google-calendar-automation in your project. Claude Code loads it when a task matches its description.

How do I install Google Calendar Automation in Codex?

Run `npx skills add aiskillstore/marketplace --skill google-calendar-automation -a codex`. Or copy the skill folder (skills/sickn33/google-calendar-automation in aiskillstore/marketplace) into .agents/skills/google-calendar-automation in your project. Codex loads it when a task matches its description.

Can I use Google Calendar Automation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aiskillstore/marketplace --skill google-calendar-automation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/google-calendar-automation, .gemini/skills/google-calendar-automation, .github/skills/google-calendar-automation and .opencode/skills/google-calendar-automation in your project.

What does Google Calendar Automation need to run?

Going by SKILL.md and its folder, Google Calendar Automation needs the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Google Calendar Automation access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Google Calendar Automation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Google Calendar Automation use?

Google Calendar Automation is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Google Calendar Automation use?

About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Google Calendar Automation?

Skills that share tags, products or a category with Google Calendar Automation: OneCLI Gateway (nanocoai/nanoclaw, 31k stars), Google Calendar (sanjay3290/ai-skills, 432 stars), Xquik MCP (Xquik-dev/x-twitter-scraper, 211 stars) and Neo4j Aura Agent Skill (neo4j-contrib/neo4j-skills, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Google Calendar Automation?

aiskillstore (a GitHub organization) maintains it in aiskillstore/marketplace, which has 433 GitHub stars. The repository holds 1,044 skills in this directory. The repository was last updated on October 10, 2026.

Source: aiskillstore/marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Google Calendar Automation

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Google Calendar

When to Use

First-Time Setup

Commands

List Calendars

List Events

Get Event Details

Create Event

Update Event

Delete Event

Find Free Time

Respond to Event Invitation

Date/Time Format

Calendar ID Format

Token Management

Limitations

Files

Used in 3 other repositories

Compare with similar skills

Similar skills

More from aiskillstore/marketplace

Related

Questions about Google Calendar Automation