Agent skill

Google Calendar

by vellum-ai in vellum-ai/vellum-assistant

View Google Calendar events for any day, create and manage events, and check availability

MITAuto-check passedProductivity & Automation

Install Google Calendar

skills CLI

$ npx skills add vellum-ai/vellum-assistant --skill google-calendar -a claude-code

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

GitHub CLI

$ gh skill install vellum-ai/vellum-assistant google-calendar --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/vellum-ai/vellum-assistant.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/google-calendar .claude/skills/google-calendar && 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" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/google-calendar into .claude/skills/google-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-calendar", 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/vellum-ai/vellum-assistant/tree/main/skills/google-calendar

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 vellum-ai/vellum-assistant --skill google-calendar -a codex

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

GitHub CLI

$ gh skill install vellum-ai/vellum-assistant google-calendar --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/google-calendar .agents/skills/google-calendar && 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" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/google-calendar into .agents/skills/google-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-calendar", 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 vellum-ai/vellum-assistant --skill google-calendar -a cursor

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

GitHub CLI

$ gh skill install vellum-ai/vellum-assistant google-calendar --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/google-calendar .cursor/skills/google-calendar && 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" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/google-calendar into .cursor/skills/google-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-calendar", 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/vellum-ai/vellum-assistant.git --path skills/google-calendar

--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 vellum-ai/vellum-assistant --skill google-calendar -a gemini-cli

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

GitHub CLI

$ gh skill install vellum-ai/vellum-assistant google-calendar --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/vellum-ai/vellum-assistant.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/google-calendar .gemini/skills/google-calendar && 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" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/google-calendar into .gemini/skills/google-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-calendar", 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 vellum-ai/vellum-assistant google-calendar

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 vellum-ai/vellum-assistant --skill google-calendar -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/google-calendar .github/skills/google-calendar && 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" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/google-calendar into .github/skills/google-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-calendar", 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 vellum-ai/vellum-assistant --skill google-calendar -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 vellum-ai/vellum-assistant google-calendar --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/google-calendar .opencode/skills/google-calendar && 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" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/google-calendar into .opencode/skills/google-calendar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-calendar", 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
GitHub stars: 1.4k
Token cost: ~1.5k tokens
SKILL.md length: 631 words
Files: 6 (incl. scripts, assets)
Skills in repo: 108
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

View Google Calendar events for any day, create and manage events, and check availability

Works in 2 steps: Check connection health first. Run… → If no connection is found or the status…
Productivity & Automation work in your project
SKILL.md covers Script Reference, Usage Examples, Connection Setup and Scheduling Playbook, plus 3 more sections
Runs TypeScript scripts from its folder; calls bun

What it does

Google Calendar is an agent skill from vellum-ai/vellum-assistant. View Google Calendar events for any day, create and manage events, and check availability

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and assets (for example `scripts/gcal.ts`, `scripts/lib/common.test.ts` and `scripts/lib/common.ts`). Compatibility notes: Designed for Vellum personal assistants

It sits in Productivity & Automation. It works with Google Calendar. The repository describes itself as: An AI Assistant that’s easy to setup, does your work 24/7, knows your preferences and gets better over time. The licence is MIT.

When your agent uses it

Productivity & Automation work in your project

Example prompts

“/google-calendar”

Requirements

Node.js
Compatibility (from SKILL.md): Designed for Vellum personal assistants

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

Check connection health first. Run assistant oauth status google. This checks whether the user's Google account is connected and the token…
If no connection is found or the status check fails: Load the vellum-oauth-integrations skill. The skill will evaluate whether managed or…

What it can do on your machine

Read from SKILL.md and the folder at commit 33cc983. 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
Ships 4 files in scripts/ (TypeScript), which the agent can run.
Shell commands in SKILL.md call:
- bun
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.
Compatibility
Designed for Vellum personal assistants
From compatibility in the SKILL.md frontmatter.

Context cost

Google Calendar loads about 1.5k tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 631 words of instructions outside code blocks.

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

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); the scripts in this folder are not scanned.

SKILL.md

The full file from vellum-ai/vellum-assistant at commit 33cc983, republished under its MIT licence (© vellum-ai). 631 words, ~1,520 tokens.

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

name: google-calendar
description: View Google Calendar events for any day, create and manage events, and check availability
compatibility: Designed for Vellum personal assistants
metadata.icon: assets/icon.svg
metadata.emoji: 📅

Script Reference

All operations use a single CLI script that returns JSON:

Success: { "ok": true, "data": ... }
Failure: { "ok": false, "error": "..." }

Script	Subcommand	Description
`scripts/gcal.ts`	`list`	List events within a date range
`scripts/gcal.ts`	`get`	Get full details of a specific event
`scripts/gcal.ts`	`create`	Create a new event (requires user confirmation)
`scripts/gcal.ts`	`availability`	Check free/busy times across calendars
`scripts/gcal.ts`	`rsvp`	Respond to an event invitation (accepted, declined, tentative)

Usage Examples

bash

# List events in a date range
bun scripts/gcal.ts list --time-min "2024-01-15T00:00:00Z" --time-max "2024-01-22T00:00:00Z"

# Get full details of a specific event
bun scripts/gcal.ts get --event-id "abc123"

# Create a new event (gates on assistant ui confirm)
bun scripts/gcal.ts create --summary "Team Meeting" --start "2024-01-15T09:00:00-05:00" --end "2024-01-15T10:00:00-05:00" --timezone "America/New_York"

# Check availability for a day
bun scripts/gcal.ts availability --time-min "2024-01-15T00:00:00Z" --time-max "2024-01-15T23:59:59Z"

# RSVP to an event invitation
bun scripts/gcal.ts rsvp --event-id "abc123" --response accepted

# Target a specific connected account (see "Multiple Accounts" below)
bun scripts/gcal.ts list --time-min "2024-01-15T00:00:00Z" --time-max "2024-01-22T00:00:00Z" --account "work@example.com"

Every subcommand accepts --account <email> to select which connected Google account the request runs against. When omitted, the request runs against a single account chosen automatically — safe only when exactly one Google account is connected. Each JSON envelope echoes the queried account in an account field when it is reported by the OAuth layer, so an empty result is self-describing (e.g. No events found in the specified time range for work@example.com.).

Connection Setup

Check connection health first. Run assistant oauth status google. This checks whether the user's Google account is connected and the token is valid. Google Calendar shares the same OAuth connection as Gmail — if the user already connected Gmail, calendar access is included.
- If the status output shows more than one active connection, you MUST pass --account <email> on every scripts/gcal.ts invocation, matching the calendar the user is asking about. When the user references a calendar by name or company (e.g. "my Acme calendar"), map it to the connected account email before querying. Omitting --account with multiple connections silently queries one arbitrary account — an empty or partial result then looks like a genuinely free calendar when it is really the wrong account. Confirm the account field in each response matches the account you intended.
If no connection is found or the status check fails: Load the vellum-oauth-integrations skill. The skill will evaluate whether managed or your-own mode is appropriate and guide the user accordingly.

Scheduling Playbook

When the user wants to schedule something:

Always check availability first before proposing times. Use bun scripts/gcal.ts availability to find free slots.
Propose 2-3 available time options to the user.
Once the user picks a time, create the event with bun scripts/gcal.ts create.
If adding other attendees, mention that they'll receive an invitation email.

Show full SKILL.md (265 more words)Show less

Date & Time Handling

Use ISO 8601 format for dates and times (e.g., 2024-01-15T09:00:00-05:00).
For all-day events, use date-only format (e.g., 2024-01-15).
Always ask the user for their timezone if it's not already known from context or their profile.
When listing events, display times in the user's local timezone.

Confidence & Safety

Create and RSVP are medium-risk operations:

Create: The create subcommand gates on assistant ui confirm — it presents a confirmation dialog to the user and only proceeds if approved. Pass --skip-confirm when the user has already given explicit confirmation in the conversation.
RSVP: The rsvp subcommand gates on assistant ui confirm — it presents a confirmation dialog showing the event, current status, and new response. Pass --skip-confirm when the user has already given explicit confirmation in the conversation.

Error Recovery

When a calendar script fails with a token or authorization error:

Try to reconnect silently. Run assistant oauth ping google. This often resolves expired tokens automatically.
If reconnection fails, go straight to setup. Don't present options, ask which route the user prefers, or explain what went wrong technically. Just tell the user briefly (e.g., "Google Calendar needs to be reconnected - let me set that up") and immediately load the vellum-oauth-integrations skill. The user came to you to get something done, not to troubleshoot - make it seamless.
Never try alternative approaches. Don't use curl, browser automation, or any workaround. If the scripts can't do it, the reconnection flow is the answer.
Never expose error details. The user doesn't need to see error messages about tokens, OAuth, or API failures. Translate errors into plain language.

Files

SKILL.md and 5 other files (scripts, assets) in skills/google-calendar of vellum-ai/vellum-assistant.

SKILL.md
assets/icon.svg
scripts/gcal.ts
scripts/lib/common.test.ts
scripts/lib/common.ts
scripts/lib/gcal-client.ts

Open the folder on GitHubat commit 33cc983

Compare with similar skills

Google Calendar 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 compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Google Calendar this skillvellum-ai/vellum-assistant	1.4k	—	~1.5k	Automated safety check: Pass	MIT	yesterday
Gcclibadlogic/pi-skills	2.6k	—	~530	Automated safety check: Pass	MIT	4 mo ago
Google Workspaceyc-software/qm	15k	—	~1.8k	Automated safety check: Pass	MIT	today
Composio Cloud Toolsquarqlabs/argus	279	—	~543	Automated safety check: Pass	Apache-2.0	4 mo ago
Canonical SchemaNxcoreAI/EverRoom	3k	—	~895	Automated safety check: Pass	Custom licence	2 days ago
Google CalendarNeverSight/learn-skills.dev	217	2 repos	~826	Automated safety check: Pass	None	today

Similar skills

Gccli
badlogic/pi-skills
Google Calendar CLI for listing calendars, viewing/creating/updating events, and checking availability.
2.6k GitHub stars~530 tokensUpdated 4 mo ago
Productivity & AutomationAuto-check passed
Google Workspace
yc-software/qm
Read and act on the user's Gmail, Google Calendar, and Google Tasks through per-user OAuth.
15k GitHub stars~1.8k tokensUpdated today
Productivity & AutomationAuto-check passed
Composio Cloud Tools
quarqlabs/argus
Routes requests to external SaaS apps such as GitHub, Gmail, Google Calendar, Slack, Notion and Linear through cloud tools, with safeguards on irreversible actions.
279 GitHub stars~543 tokensUpdated 4 mo ago
Productivity & AutomationAuto-check passed
Canonical Schema
NxcoreAI/EverRoom
canonical schema 字段语义与各 provider 原始格式要点（gmail/outlook/google-calendar）。产出格式映射时使用。
3k GitHub stars~895 tokensUpdated 2 days ago
Productivity & AutomationAuto-check passed
Google Calendar
NeverSight/learn-skills.dev
Interact with Google Calendar via the Google Calendar API – list upcoming events, create new events, update or delete them.
217 GitHub starsUsed in 2 repos~826 tokens
Productivity & AutomationAuto-check passed
Google Calendar
earlyaidopters/claudeclaw
Manage your Google Calendar from Claude Code. An agent skill from earlyaidopters/claudeclaw.
173 GitHub stars~1.2k tokensUpdated 5 mo ago
Productivity & AutomationAuto-check: notes

Questions about Google Calendar

What does Google Calendar do?

View Google Calendar events for any day, create and manage events, and check availability. Google Calendar is an agent skill from vellum-ai/vellum-assistant.

When should I use Google Calendar?

Google Calendar fits situations like: productivity & Automation work in your project.

How do I install Google Calendar in Claude Code?

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

How do I install Google Calendar in Codex?

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

Can I use Google Calendar 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 vellum-ai/vellum-assistant --skill google-calendar -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, .gemini/skills/google-calendar, .github/skills/google-calendar and .opencode/skills/google-calendar in your project.

What does Google Calendar need to run?

Going by SKILL.md and its folder, Google Calendar needs TypeScript for the scripts in its folder and the command-line tools its instructions call (bun). Our summary lists: Node.js. Compatibility (from SKILL.md): Designed for Vellum personal assistants.

Does Google Calendar 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 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Google Calendar use?

Google Calendar is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Google Calendar use?

About 1.5k tokens (SKILL.md is roughly 6.1k 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?

Skills that share tags, products or a category with Google Calendar: Gccli (badlogic/pi-skills, 2.6k stars), Google Workspace (yc-software/qm, 15k stars), Composio Cloud Tools (quarqlabs/argus, 279 stars) and Canonical Schema (NxcoreAI/EverRoom, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Google Calendar?

vellum-ai (a GitHub organization) maintains it in vellum-ai/vellum-assistant, which has 1,408 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on October 9, 2026.

Source: vellum-ai/vellum-assistant 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

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Compatibility

Context cost

Safety

SKILL.md

Script Reference

Usage Examples

Connection Setup

Scheduling Playbook

Date & Time Handling

Confidence & Safety

Error Recovery

Files

Compare with similar skills

Similar skills

More from vellum-ai/vellum-assistant

Related

Questions about Google Calendar