with one click
create-cal-com-link
Create targeted Cal links for specific people or teams
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Create targeted Cal links for specific people or teams
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | create-cal-com-link |
| description | Create targeted Cal links for specific people or teams |
.env.example to .env and set CAL_API_KEY.bash .opencode/skills/create-cal-com-link/scripts/create-schedule.sh "Jasper" "Asia/Singapore"
# copy schedule id + default availability id from the output
bash .opencode/skills/create-cal-com-link/scripts/delete-default-availability.sh <availability-id>
bash .opencode/skills/create-cal-com-link/scripts/add-availability-window.sh <schedule-id> "[1,2,3,4,5]" "10:00:00" "13:00:00"
bash .opencode/skills/create-cal-com-link/scripts/create-event-type.sh <schedule-id> "Jasper x Benjamin" "jasper-x-benjamin" 30 "integrations:daily"
bash .opencode/skills/create-cal-com-link/scripts/set-event-type-range.sh <event-type-id> 4 "Asia/Singapore"
Use this when someone says: "Create a link for Jasper, he's on Singapore time, next 4 days."
Asia/Singapore).bash .opencode/skills/create-cal-com-link/scripts/create-schedule.sh "Jasper (next 4 days)" "Asia/Singapore"
# capture schedule id + availability id from the response
bash .opencode/skills/create-cal-com-link/scripts/delete-default-availability.sh <availability-id>
bash .opencode/skills/create-cal-com-link/scripts/add-availability-window.sh <schedule-id> "[1,2,3,4,5]" "10:00:00" "13:00:00"
bash .opencode/skills/create-cal-com-link/scripts/create-event-type.sh <schedule-id> "Jasper x Benjamin" "jasper-x-benjamin" 30 "integrations:daily"
bash .opencode/skills/create-cal-com-link/scripts/set-event-type-range.sh <event-type-id> 4 "Asia/Singapore"
1970-01-01T08:00:00.000Z.set-event-type-range.sh to time-box the link..env.example to .env and set CAL_API_KEY.scripts/ uses .env.example as the minimum configuration reference.Drive the OpenWork dev renderer with Chrome MCP and verify workspace UI flows. Triggers when user mentions: - "use Chrome MCP with OpenWork" - "hook up to pnpm dev renderer" - "add an OpenWork workspace through the UI"
Create a PR with structured evidence: build verification, UI screenshots uploaded to an ephemeral host, API test results, and a verification comment. No screenshots committed to the repo. Triggers when user mentions: - "create a pr" - "make a pr" - "open a pr" - "push and pr"
Boot up the Den dev stack and the OpenWork desktop app locally, then test common flows like sign-in, dashboard, and telemetry. Triggers when user mentions: - "test den" - "test the app locally" - "boot up den" - "den dev flow" - "test sign in"
Generate or update the internal OpenWork release changelog tracker as plain markdown release sections. Triggers when user mentions: - "generate changelog markdown" - "track this release" - "add a changelog entry"
CUPID app architecture guidance for apps/app/src/app/**
Manage Vercel environment variables for OpenWork projects from the CLI, including linking the local app directory first. Triggers when user mentions: - "add a vercel env var" - "set a vercel env var" - "vercel environment variable"