Zapier SDK
zapier/sdk
Zapier SDK for TypeScript. An agent skill from zapier/sdk.
Agent-callable Google Calendar tools — create, update, move, search, and delete events, manage calendars, check free/busy availability, resolve event colors, and manage calendar sharing.
Install Google Calendar
$ npx skills add zapier/connectors --skill google-calendar -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install zapier/connectors google-calendar --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/zapier/connectors.git skills-src && mkdir -p .claude/skills && cp -r skills-src/apps/google-calendar .claude/skills/google-calendar && rm -rf skills-srcUse ~/.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/
Install the "google-calendar" agent skill from https://github.com/zapier/connectors/tree/main/apps/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 install https://github.com/zapier/connectors/tree/main/apps/google-calendarType 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.
$ npx skills add zapier/connectors --skill google-calendar -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install zapier/connectors google-calendar --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/connectors.git skills-src && mkdir -p .agents/skills && cp -r skills-src/apps/google-calendar .agents/skills/google-calendar && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "google-calendar" agent skill from https://github.com/zapier/connectors/tree/main/apps/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.
$ npx skills add zapier/connectors --skill google-calendar -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install zapier/connectors google-calendar --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/connectors.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/apps/google-calendar .cursor/skills/google-calendar && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "google-calendar" agent skill from https://github.com/zapier/connectors/tree/main/apps/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 https://github.com/zapier/connectors.git --path apps/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.
$ npx skills add zapier/connectors --skill google-calendar -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install zapier/connectors google-calendar --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/connectors.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/apps/google-calendar .gemini/skills/google-calendar && rm -rf skills-srcUse ~/.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/
Install the "google-calendar" agent skill from https://github.com/zapier/connectors/tree/main/apps/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.
$ gh skill install zapier/connectors google-calendarInstalls 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).
$ npx skills add zapier/connectors --skill google-calendar -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/zapier/connectors.git skills-src && mkdir -p .github/skills && cp -r skills-src/apps/google-calendar .github/skills/google-calendar && rm -rf skills-srcUse ~/.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/
Install the "google-calendar" agent skill from https://github.com/zapier/connectors/tree/main/apps/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.
$ npx skills add zapier/connectors --skill google-calendar -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install zapier/connectors google-calendar --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zapier/connectors.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/apps/google-calendar .opencode/skills/google-calendar && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "google-calendar" agent skill from https://github.com/zapier/connectors/tree/main/apps/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
- 176
- Token cost
- ~4k tokens
- SKILL.md length
- 1,296 words
- Files
- 60 (incl. scripts, references)
- Skills in repo
- 29
- Repo updated
- First seen
- Licence
- Elastic-2.0
At a glance
Agent-callable Google Calendar tools — create, update, move, search, and delete events, manage calendars, check free/busy availability, resolve event colors, and manage calendar sharing.
- The user mentions Google Calendar
- SKILL.md covers When to use this, Setup, Scripts and Disambiguation & refusals, plus 3 more sections
- Runs TypeScript and JavaScript scripts from its folder; calls npm, npx and git; reaches googleapis.com
- Wants to schedule
What it does
Google Calendar is an agent skill from zapier/connectors, published by the product's own GitHub organization. Agent-callable Google Calendar tools — create, update, move, search, and delete events, manage calendars, check free/busy availability, resolve event colors, and manage calendar sharing. Use when the user mentions Google Calendar or wants to schedule, find, reschedule, or share events and calendars — including requests that do not name Google Calendar explicitly, e.g. "put a meeting on my calendar Tuesday 3pm" or "am I free Friday afternoon".
Its SKILL.md is about 4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 63 other files, including scripts and reference files (for example `.claude-plugin/plugin.json`, `.mcp.json` and `CHANGELOG.md`). Compatibility notes: Run npm install --omit=dev in this directory, then node cli.js. The TypeScript source needs Node.js 22.18+; on older Node, run cli.js for build-it-yourself /…
It sits in Productivity & Automation. It works with Google Calendar and Zapier. The repository describes itself as: Connect your agent to the apps you already use - with or without Zapier.
When your agent uses it
- The user mentions Google Calendar
- Wants to schedule
- Share events and calendars — including requests that do not name Google Calendar explicitly
Example prompts
- “put a meeting on my calendar Tuesday 3pm”
- “am I free Friday afternoon”
- “/google-calendar”
Requirements
- Node.js
- Compatibility (from SKILL.md): Run `npm install --omit=dev` in this directory, then `node cli.js`. The TypeScript source needs Node.js 22.18+; on older Node, run `cli.js` for build-it-yourself / prebuilt / alternative-runtime options.
What it can do on your machine
Read from SKILL.md and the folder at commit e48d26f. 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 1 file in scripts/ (TypeScript and JavaScript, from the files we listed), which the agent can run.
Shell commands in SKILL.md call:
npmnpxgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
googleapis.com
Also links to:
developers.google.comagentskills.io
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
Run `npm install --omit=dev` in this directory, then `node cli.js`. The TypeScript source needs Node.js 22.18+; on older Node, run `cli.js` for build-it-yourself / prebuilt / alternative-runtime options.
From compatibility in the SKILL.md frontmatter.
Context cost
Google Calendar loads about 4k tokens when it runs, and up to ~16k if it reads all its reference files. Until then it costs about 116 tokens; SKILL.md has 1,296 words of instructions outside code blocks.
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
Its licence (Elastic-2.0) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,296 words (~3,965 tokens).
“Tools for managing Google Calendar — create, read, update, move, and delete events; search a calendar; list and create calendars; check free/busy availability; resolve the event-color palette; and manage calendar sharing (ACL). Wraps the Google Calendar API v3 (https://www.googleapis.com/calendar/v3/). Authentication…”
- name
- google-calendar
- compatibility
- Run `npm install --omit=dev` in this directory, then `node cli.js`. The TypeScript source needs Node.js 22.18+; on older Node, run `cli.js` for build-it-yourself / prebuilt / alternative-runtime options.
- license
- Elastic-2.0
- metadata.title
- Google Calendar
- metadata.source
- https://github.com/zapier/connectors/blob/main/apps/google-calendar/SKILL.md
- metadata.zapier-app-key
- GoogleCalendarCLIAPI
- metadata.api-docs
- https://developers.google.com/workspace/calendar/api/v3/reference
Files
SKILL.md and 59 other files (scripts, references) in apps/google-calendar of zapier/connectors.
- SKILL.md
- .claude-plugin/plugin.json
- .mcp.json
- CHANGELOG.md
- LICENSE
- NOTICE
- README.md
- cli.js
- cli.ts
- connections.ts
- evals/evals.json
- evals/results.md
- index.ts
- lib/google-calendar.ts
- package.json
- references/google-calendar-api-gotchas.md
- references/use-as-cli.md
- … and 43 more
Open the folder on GitHubat commit e48d26f
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Google Calendar this skillzapier/connectors | 176 | — | ~4k | Automated safety check: Pass | Elastic-2.0 | |
| Zapier SDKzapier/sdk | 263 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Zapier Demozapier/zapier-mcp | 430 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Gcclibadlogic/pi-skills | 2.6k | — | ~530 | Automated safety check: Pass | MIT | |
| Google Workspaceyc-software/qm | 15k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Zapier Statuszapier/zapier-mcp | 430 | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
- Official
- Official
Zapier Demo
zapier/zapier-mcp
Walk a new user through setting up their first Zapier action and running it live — the smallest possible win.
Gccli
badlogic/pi-skills
Google Calendar CLI for listing calendars, viewing/creating/updating events, and checking availability.
Google Workspace
yc-software/qm
Read and act on the user's Gmail, Google Calendar, and Google Tasks through per-user OAuth.
- Official
Zapier Status
zapier/zapier-mcp
Check the health of your Zapier MCP setup. An agent skill from zapier/zapier-mcp.
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.
More from zapier/connectors
All 29 skills in this repo- Official
Alpaca
zapier/connectors
Agent-callable Alpaca trading tools — place and manage stock, crypto, and options orders, read account balances, positions, and portfolio history, look up assets and market hours, and read watchlists.
- Official
Clay
zapier/connectors
Agent-callable Clay tools — create, update, and find rows in Clay tables, and navigate workspaces, tables, views, and users.
- Official
Discord
zapier/connectors
Agent-callable Discord tools — send and manage messages, start threads and forum posts, manage channels, members, and roles, and post via webhooks.
- Official
Dropbox
zapier/connectors
Agent-callable Dropbox tools — upload, organize, find, and share files and folders.
- Official
Elevenlabs
zapier/connectors
Agent-callable ElevenLabs tools — generate spoken audio from text, create sound effects and multi-speaker dialogue, re-voice and clean up audio, transcribe audio and video, design synthetic voices…
- Official
Firecrawl
zapier/connectors
Agent-callable Firecrawl tools — scrape a URL to clean Markdown, crawl a site, search the web, map site URLs, and extract structured data.
Related
Works with
Categories
Questions about Google Calendar
What does Google Calendar do?
Agent-callable Google Calendar tools — create, update, move, search, and delete events, manage calendars, check free/busy availability, resolve event colors, and manage calendar sharing. Google Calendar is an agent skill from zapier/connectors, published by the product's own GitHub organization. Agent-callable Google Calendar tools — create, update, move, search, and delete events, manage calendars, check free/busy availability, resolve event colors, and manage calendar sharing.
When should I use Google Calendar?
Google Calendar fits situations like: the user mentions Google Calendar; wants to schedule; share events and calendars — including requests that do not name Google Calendar explicitly.
How do I install Google Calendar in Claude Code?
Run `npx skills add zapier/connectors --skill google-calendar -a claude-code`. Or copy the skill folder (apps/google-calendar in zapier/connectors) 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 zapier/connectors --skill google-calendar -a codex`. Or copy the skill folder (apps/google-calendar in zapier/connectors) 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 zapier/connectors --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 and JavaScript for the scripts in its folder and the command-line tools its instructions call (npm, npx and git). Our summary lists: Node.js. Compatibility (from SKILL.md): Run `npm install --omit=dev` in this directory, then `node cli.js`. The TypeScript source needs Node.js 22.18+; on older Node, run `cli.js` for build-it-yourself / prebuilt / alternative-runtime options..
Does Google Calendar access the network?
SKILL.md names 3 domains. In commands or code: googleapis.com; the agent is likely to contact it when it follows the instructions. As links in the text: developers.google.com and agentskills.io. 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 Elastic-2.0 licence (declared in SKILL.md).
How many tokens does Google Calendar use?
About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 12k tokens, read only when the agent opens those files.
What are the alternatives to Google Calendar?
Skills that share tags, products or a category with Google Calendar: Zapier SDK (zapier/sdk, 263 stars), Zapier Demo (zapier/zapier-mcp, 430 stars), Gccli (badlogic/pi-skills, 2.6k stars) and Google Workspace (yc-software/qm, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Google Calendar?
zapier (a GitHub organization, an official publisher) maintains it in zapier/connectors, which has 176 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on August 25, 2026.
Source: zapier/connectors on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.