calcom-access — Claude Code skill: Cal.com API via 1Password
calcom-access is a Claude Code skill for five other platforms that gives the agent access to Cal.com API for bookings, event types, schedules and slot availability. The API key is read from 1Password via CALCOM_OP_UUID.
MIT 107 installs ★ 3 updated 2026-10-25
npx skills add terrylica/cc-skills --skill calcom-access -a claude-codeWhat calcom-access does
The skill exposes Cal.com API v2 commands to the agent: list or filter bookings by status, create and update event types, query schedules, check slot availability, cancel bookings by ID.
Authentication goes through 1Password CLI (op). The skill reads the API key from a 1Password item identified by CALCOM_OP_UUID. It ships a Bun-based binary called calcom; on first use the skill builds it with bun install && bun run build. Every time the skill activates, it runs a preflight: checks the binary, the env variable and the active op session — and stops with instructions if any of those are missing.
No API key stored in 1Password yet? The skill walks through setup: searches the "Claude Automation" vault for matching items or guides the user through op item create to store a new key. Without an active op signin session, nothing runs.
What it helps with
- List upcoming bookings filtered by status from the agent
- Create a new event type with a custom slug and duration
- Check free slots with
availability checkinside a workflow - Cancel a booking by ID without leaving the terminal
- Wire Cal.com credentials through 1Password instead of hardcoding keys
Example prompts for the agent
- List all event types on my Cal.com account
- Show 20 upcoming bookings with status filter
- Create an event type called '30-min Interview' with slug
interview-30and length 30
How to install calcom-access
1Skills CLI (Vercel)
npx skills add terrylica/cc-skills --skill calcom-access -a claude-code2Manually: put the files in place
~/.claude/skills/calcom-access/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/calcom-access/
1Skills CLI (Vercel)
npx skills add terrylica/cc-skills --skill calcom-access -a codex2Manually: put the files in place
.agents/skills/calcom-access/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add terrylica/cc-skills --skill calcom-access -a cursor2Manually: put the files in place
.cursor/skills/calcom-access/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install terrylica/cc-skills plugins/calcom-commander/skills/calcom-access2Manually: put the files in place
.github/skills/calcom-access/SKILL.md1Skills CLI (Vercel)
npx skills add terrylica/cc-skills --skill calcom-access -a gemini-cli2Platform CLI
gemini skills install https://github.com/terrylica/cc-skills --path plugins/calcom-commander/skills/calcom-accessManually: put the files in place
.devin/skills/calcom-access/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add terrylica/cc-skills --skill calcom-access -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about calcom-access
How do I install calcom-access in Claude Code?
Run npx skills add terrylica/cc-skills --skill calcom-access -a claude-code. The skill lands at ~/.claude/skills/calcom-access/SKILL.md.
What does the calcom-access skill do?
It gives the agent a set of Cal.com API v2 commands: read and create bookings, event types and schedules, all authenticated through 1Password CLI.
What does calcom-access require to work?
1Password CLI (op) with an active signed-in session and the CALCOM_OP_UUID environment variable pointing to the right 1Password item. Bun is also required because the skill builds its CLI binary on first run.
Source text
SKILL.md · MIT
---
name: calcom-access
description: "Access the Cal.com API via CLI with a 1Password API key: bookings, event types, schedules and availability. TRIGGERS - calcom, cal.com, list bookings, event types, create booking page."
allowed-tools: Read, Bash, Grep, Glob, Write, AskUserQuestion
---
# Cal.com Access
Manage Cal.com bookings and event types programmatically via Claude Code.
> **Self-Evolving Skill**: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.
## MANDATORY PREFLIGHT (Execute Before Any Cal.com Operation)
**CRITICAL**: You MUST complete this preflight checklist before running any Cal.com commands. Do NOT skip steps.
### Step 1: Check CLI Binary Exists
```bash
ls -la "$HOME/.claude/plugins/marketplaces/cc-skills/plugins/calcom-commander/scripts/calcom-cli/calcom" 2>/dev/null || echo "BINARY_NOT_FOUND"
```
**If BINARY_NOT_FOUND**: Build it first:
```bash
cd ~/.claude/plugins/marketplaces/cc-skills/plugins/calcom-commander/scripts/calcom-cli && bun install && bun run build
```
### Step 2: Check CALCOM_OP_UUID Environment Variable
```bash
echo "CALCOM_OP_UUID: ${CALCOM_OP_UUID:-NOT_SET}"
```
**If NOT_SET**: You MUST run the Setup Flow below. Do NOT proceed to Cal.com commands.
### Step 3: Verify 1Password Authentication
```bash
op account list 2>&1 | head -3
```
**If error or not signed in**: Inform user to run `op signin` first.
### Step 4: Test API Connectivity
```bash
CALCOM_CLI="$HOME/.claude/plugins/marketplaces/cc-skills/plugins/calcom-commander/scripts/calcom-cli/calcom"
$CALCOM_CLI event-types list 2>&1 | head -5
```
---
## Setup Flow (When CALCOM_OP_UUID is NOT_SET)
Follow these steps IN ORDER. Use AskUserQuestion at decision points.
### Setup Step 1: Check 1Password CLI
```bash
command -v op && echo "OP_CLI_INSTALLED" || echo "OP_CLI_MISSING"
```
**If OP_CLI_MISSING**: Stop and inform user:
> 1Password CLI is required. Install with: `brew install 1password-cli`
### Setup Step 2: Discover Cal.com API Keys in 1Password
```bash
op item list --vault "Claude Automation" --format json 2>/dev/null | jq -r '.[] | select(.title | test("calcom|cal.com|calendar"; "i")) | "\(.id)\t\(.title)"'
```
**Parse the output** and proceed based on results.
### Setup Step 3: User Selects API Credentials
**If items found**, use AskUserQuestion with discovered items.
**If NO items found**, guide the user:
1. Log into the Cal.com instance (self-hosted or cal.com)
2. Go to Settings > Developer > API Keys
3. Generate a new API key with appropriate scopes
4. Store in 1Password Claude Automation vault:
```bash
op item create --category "API Credential" --title "Cal.com API Key" \
--vault "Claude Automation" \
"credential=<api-key>" \
"api_url=<cal.com-instance-url>"
```
### Setup Step 4: Supply the UUID
After user selects an item (with UUID), use AskUserQuestion to confirm where it goes: this shell only (`export CALCOM_OP_UUID=<selected-uuid>`), or the launchd daemons (add `export CALCOM_OP_UUID='<selected-uuid>'` to `~/gh/<org>/<automation-repo>/.env.launchd`, which the launcher scripts source).
### Setup Step 5: Verify
```bash
echo "CALCOM_OP_UUID: ${CALCOM_OP_UUID:-NOT_SET}"
```
### Setup Step 6: Test Connection
```bash
CALCOM_OP_UUID="${CALCOM_OP_UUID}" $HOME/.claude/plugins/marketplaces/cc-skills/plugins/calcom-commander/scripts/calcom-cli/calcom event-types list
```
---
## Cal.com Commands (Only After Preflight Passes)
```bash
CALCOM_CLI="$HOME/.claude/plugins/marketplaces/cc-skills/plugins/calcom-commander/scripts/calcom-cli/calcom"
# List event types
$CALCOM_CLI event-types list
# List bookings
$CALCOM_CLI bookings list -n 10
# List bookings by status
$CALCOM_CLI bookings list --status upcoming -n 20
# Get booking details
$CALCOM_CLI bookings get <booking_id>
# Create event type
$CALCOM_CLI event-types create --title "30min Interview" --slug "interview-30" --length 30
# Update event type
$CALCOM_CLI event-types update <event_type_id> --title "Updated Title"
# List schedules (availability)
$CALCOM_CLI schedules list
# JSON output (for parsing)
$CALCOM_CLI bookings list -n 10 --json
```
## Cal.com API v2 Reference
| Endpoint | CLI Command | Description |
| ------------ | -------------------- | ------------------------- |
| Event Types | `event-types list` | List all event types |
| Event Types | `event-types create` | Create new event type |
| Bookings | `bookings list` | List bookings |
| Bookings | `bookings get` | Get booking details |
| Bookings | `bookings cancel` | Cancel a booking |
| Schedules | `schedules list` | List availability windows |
| Schedules | `schedules create` | Create availability |
| Availability | `availability check` | Check slot availability |
## Environment Variables
| Variable | Required | Description |
| ---------------- | -------- | ----------------------------------- |
| `CALCOM_OP_UUID` | Yes | 1Password item UUID for API key |
| `CALCOM_API_URL` | No | API base URL (default: self-hosted) |
## References
- [calcom-api-setup.md](./references/calcom-api-setup.md) - Cal.com API key setup guide
- [env-setup.md](./references/env-setup.md) - Where each variable comes from, per consumer
## Post-Change Checklist
- [ ] YAML frontmatter valid (no colons in description)
- [ ] Trigger keywords current
- [ ] Path patterns use $HOME not hardcoded paths
- [ ] References exist and are linked
## Post-Execution Reflection
After this skill completes, reflect before closing the task:
0. **Locate yourself.** — Find this SKILL.md's canonical path before editing.
1. **What failed?** — Fix the instruction that caused it.
2. **What worked better than expected?** — Promote to recommended practice.
3. **What drifted?** — Fix any script, reference, or dependency that no longer matches reality.
4. **Log it.** — Evolution-log entry with trigger, fix, and evidence.
Do NOT defer. The next invocation inherits whatever you leave behind.
© terrylica · MIT · terrylica/cc-skills