Agent Skills
Pro plan. Skills use the API and hosted calendars. View plans.
CalendarPipe publishes a collection of Agent Skills that give AI coding agents direct access to calendar operations. Install a skill and your agent can manage hosted calendars, send invitations, RSVP to inbound invites, and execute tasks triggered by calendar events.
Skills work with Claude Code, VS Code (GitHub Copilot), and any client that follows the Agent Skills convention.
Available Skills
calendarpipe
Core skill for managing CalendarPipe. Gives your agent the ability to:
- Create, update, and delete events
- Send invitations and cancel them
- RSVP to inbound invitations
- Check schedules and poll for updates
- Create and test sync rules, including dry-running gate code before saving it
This skill works standalone. It includes a helper script for authenticated API calls and an endpoint index generated from the API spec, which it reads directly for endpoint detail — so it stays current as the API grows.
agent-calendar
Turns calendar invitations into scheduled actions. When an invitation arrives with a task in its description, the skill:
- Accepts the invitation automatically
- Schedules a one-shot cron job at the event's start time
- Reconciles on restart — re-creates missing crons and cleans up cancelled events
Depends on calendarpipe for API access and configuration.
Installation
The easiest way to install is with the skills CLI — the standard package manager for the open Agent Skills ecosystem. It works with Claude Code, Cursor, Copilot, Codex, and 40+ other agents.
Install all skills
npx skills add calendarpipe/skills
The CLI auto-detects which coding agents you have installed and symlinks the skills into the right directories.
Install a specific skill
npx skills add calendarpipe/skills --skill calendarpipe
npx skills add calendarpipe/skills --skill agent-calendar
Install globally (all projects)
npx skills add calendarpipe/skills -g
Target a specific agent
npx skills add calendarpipe/skills -a claude-code
npx skills add calendarpipe/skills -a cursor
Setup
On first use the calendarpipe skill walks you through setup — API key, calendar selection — and stores your configuration under ~/.config/calendarpipe/ (or $XDG_CONFIG_HOME if set). Keeping it outside the skill directory means updating or reinstalling a skill never touches your credentials or scheduled tasks.
Set CALENDARPIPE_API_KEY in your environment to override the stored token — useful in CI.
If you installed a skill before August 2026, configuration used to live inside the skill directory. Both skills detect the old files on first run and move them for you.
agent-calendar uses calendarpipe for API access, so install both if you want task scheduling.
Updating
npx skills update
Example: Scheduling a Meeting
Once the calendarpipe skill is installed, your agent can handle requests like:
"Schedule a 30-minute sync with alice@example.com tomorrow at 2pm ET"
The agent will use the skill to create an event with attendees on your hosted calendar, and CalendarPipe handles the invitation delivery automatically.
Example: Mirroring a Calendar
Sync rules are available through the skill too, so your agent can set one up end to end:
"Mirror my work calendar into my personal one, but replace every title with 'Busy' and drop the descriptions"
The agent lists your connected calendars, writes the gate function, dry-runs it against your real events so you can see exactly what the copies would look like, and only then creates and enables the rule.
Example: Task Automation
With agent-calendar installed, other agents (or humans) can send your agent a calendar invitation with a task description:
Event title: Deploy staging build Description:
Run the staging deployment pipeline and report results backStart time: 2026-03-27T14:00:00Z
Your agent accepts the invitation and executes the task at the scheduled time.
Related
- Invitations — the iTIP workflow the skills implement.
- Hosted Calendars — the calendars that power agent workflows.
- GitHub Repository — source and issues. The repository is a published mirror, so report problems as issues rather than pull requests.