booking-config — Claude Code skill: what it does, how to install
booking-config configures Cal.com event types, schedules, and webhooks via CLI commands. Useful when you need to adjust booking pages and availability without opening the web interface.
MIT 103 installs ★ 3 updated 2026-10-25
npx skills add terrylica/cc-skills --skill booking-config -a claude-codeWhat booking-config does
This skill manages Cal.com configuration using a bundled calcom CLI binary from the calcom-commander plugin. The agent prompts for event parameters, creates or updates booking pages, sets weekday availability windows, and inspects free slots for given date ranges.
It also handles Cal.com webhook registration for events like bookings, reschedules, and cancellations. API credentials are pulled on the fly from 1Password using the op command.
Without the CLI binary at $HOME/.claude/plugins/marketplaces/cc-skills/plugins/calcom-commander/scripts/calcom-cli/calcom and valid CALCOM_OP_UUID and CALCOM_API_URL environment variables, every command will fail.
What it helps with
- Create a Cal.com booking page with custom duration and title
- Define weekly availability hours and timezone
- Query available booking slots across specific dates
- Register Cal.com webhooks to forward event payloads
Example prompts for the agent
- Create a 30-minute screening interview event type in Cal.com
- Set up a weekday business hours schedule from 9am to 5pm
- Check available booking slots for the upcoming week
How to install booking-config
1Skills CLI (Vercel)
npx skills add terrylica/cc-skills --skill booking-config -a claude-code2Manually: put the files in place
~/.claude/skills/booking-config/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/booking-config/
1Skills CLI (Vercel)
npx skills add terrylica/cc-skills --skill booking-config -a codex2Manually: put the files in place
.agents/skills/booking-config/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add terrylica/cc-skills --skill booking-config -a cursor2Manually: put the files in place
.cursor/skills/booking-config/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install terrylica/cc-skills plugins/calcom-commander/skills/booking-config2Manually: put the files in place
.github/skills/booking-config/SKILL.md1Skills CLI (Vercel)
npx skills add terrylica/cc-skills --skill booking-config -a gemini-cli2Platform CLI
gemini skills install https://github.com/terrylica/cc-skills --path plugins/calcom-commander/skills/booking-configManually: put the files in place
.devin/skills/booking-config/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add terrylica/cc-skills --skill booking-config -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 booking-config
How to install booking-config in Claude Code?
Run npx skills add terrylica/cc-skills --skill booking-config -a claude-code.
What does booking-config do?
It handles Cal.com event types, availability schedules, slot checks, and webhook registrations directly through CLI tooling.
What environment variables does booking-config require?
You must set CALCOM_OP_UUID and CALCOM_API_URL, and provide WEBHOOK_RELAY_URL if registering webhooks.
Source text
SKILL.md · MIT
---
name: booking-config
description: Cal.com event types, schedules, and availability configuration. TRIGGERS - event type, booking page, schedule
allowed-tools: Read, Bash, Grep, Glob, Write, AskUserQuestion
---
# Booking Configuration
Configure Cal.com event types, schedules, and availability windows via CLI.
> **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
### Step 1: Check CLI Binary
```bash
ls -la "$HOME/.claude/plugins/marketplaces/cc-skills/plugins/calcom-commander/scripts/calcom-cli/calcom" 2>/dev/null || echo "BINARY_NOT_FOUND"
```
### Step 2: Verify Environment
```bash
echo "CALCOM_OP_UUID: ${CALCOM_OP_UUID:-NOT_SET}"
echo "CALCOM_API_URL: ${CALCOM_API_URL:-NOT_SET}"
```
**All must be SET.** If any are NOT_SET, run the setup command first.
### Step 3: Test API Access
```bash
CALCOM_CLI="$HOME/.claude/plugins/marketplaces/cc-skills/plugins/calcom-commander/scripts/calcom-cli/calcom"
$CALCOM_CLI event-types list 2>&1 | head -3
```
## Event Type Management
### Create Event Type
Use AskUserQuestion to collect required fields:
```
AskUserQuestion({
questions: [{
question: "What type of booking page do you want to create?",
header: "Event Type",
options: [
{ label: "30-min Meeting", description: "Standard 30-minute meeting slot" },
{ label: "60-min Interview", description: "Full hour interview session" },
{ label: "15-min Quick Call", description: "Brief check-in call" },
{ label: "Custom", description: "Specify custom duration and details" }
],
multiSelect: false
}]
})
```
```bash
CALCOM_CLI="$HOME/.claude/plugins/marketplaces/cc-skills/plugins/calcom-commander/scripts/calcom-cli/calcom"
# Create event type with collected details
$CALCOM_CLI event-types create \
--title "30min Interview" \
--slug "interview-30" \
--length 30 \
--description "Screening interview for VA candidates"
```
### Update Event Type
```bash
# Update title
$CALCOM_CLI event-types update <id> --title "Updated Title"
# Update duration
$CALCOM_CLI event-types update <id> --length 45
# Disable event type
$CALCOM_CLI event-types update <id> --hidden true
```
## Schedule Management
### List Schedules
```bash
$CALCOM_CLI schedules list
```
### Create Schedule
```bash
# Create a weekday schedule (9am-5pm)
$CALCOM_CLI schedules create \
--name "Business Hours" \
--timezone "America/New_York" \
--availability '[
{"days": [1,2,3,4,5], "startTime": "09:00", "endTime": "17:00"}
]'
```
### Check Availability
```bash
# Check available slots for a specific date range
$CALCOM_CLI availability check \
--event-type-id <id> \
--start "2026-02-15" \
--end "2026-02-20"
```
## Common Booking Page Patterns
### Candidate Screening Interview
```bash
$CALCOM_CLI event-types create \
--title "VA Screening Interview" \
--slug "va-screening" \
--length 30 \
--description "BruntWork virtual assistant candidate screening" \
--requires-confirmation true
```
### Open Office Hours
```bash
$CALCOM_CLI event-types create \
--title "Office Hours" \
--slug "office-hours" \
--length 15 \
--description "Drop-in office hours for team questions"
```
## Webhook Management
Manage Cal.com webhooks for real-time Pushover notifications via the webhook relay.
### List Webhooks
```bash
CALCOM_API_KEY=$(op item get "$CALCOM_OP_UUID" --vault "Claude Automation" --fields password --reveal)
curl -s "https://api.cal.com/v1/webhooks?apiKey=$CALCOM_API_KEY" | python3 -m json.tool
```
### Register Webhook
```bash
curl -s -X POST "https://api.cal.com/v1/webhooks?apiKey=$CALCOM_API_KEY" \
-H "Content-Type: application/json" \
-d "{\"subscriberUrl\":\"$WEBHOOK_RELAY_URL\",\"eventTriggers\":[\"BOOKING_CREATED\",\"BOOKING_RESCHEDULED\",\"BOOKING_CANCELLED\"],\"active\":true}"
```
### Delete Webhook
```bash
curl -s -X DELETE "https://api.cal.com/v1/webhooks/<webhook-id>?apiKey=$CALCOM_API_KEY"
```
**Prerequisites**: `WEBHOOK_RELAY_URL` must be set in the environment (`~/gh/<org>/<automation-repo>/.env.launchd` for the daemons, or exported in your shell). Deploy the relay first via the `infra-deploy` skill.
## Post-Change Checklist
- [ ] YAML frontmatter valid (no colons in description)
- [ ] Trigger keywords current
- [ ] Path patterns use $HOME not hardcoded paths
## 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