cc-skill:calcom-setup-patterns

Claude Code skill · anthropic · active

last 30 days

0 calls

0 of 30 days active

explain like I am new to this

what it does

This skill helps you set up Cal.com, the open-source alternative to Calendly. It guides you through decisions like whether to host it yourself or use their cloud service, how to structure your booking pages, how to qualify prospects before they book, and which integrations to connect first.

who it is for

Founders, sales leaders, and support managers who need scheduling software but want more control, lower costs, or the ability to ask qualifying questions before people book time.

when it fires

When you mention Cal.com, Calcom, booking pages, scheduling setup, routing forms, embedded booking, or appointment booking flows.

say something like

"How should I set up Cal.com for my sales team to do discovery calls and demos?"
"Should we self-host Cal.com or use their cloud version?"
"I want to ask qualifying questions before people book a sales call with us. How do I do that in Cal.com?"

what you might get back

Start with Cal.com Cloud, not self-hosted. Create two event types: one 15-minute discovery call with questions about company size and use case, one 45-minute demo with a 15-minute buffer after. Use a routing form to funnel low-fit prospects away. Connect your Google Calendar first so people don't book over existing meetings. Embed the booking link on your website.

how to know it worked

You get a clear recommendation on Cloud vs self-hosted, specific event type templates matched to your use case, and a checklist of what to set up first (calendar connection, questions, buffers).

is this skill working for me

never used

cloud runs

0 deployments

local fires

Claude Code (optional)

posts published

from drafts

attributed

$0.00

signups + revenue

Deploy this skill as a cloud automation to put it to work — runs on a schedule, dispatches output to Telegram or email, and logs every result here.

Deploy this skill

no laptop required

Run this skill on a schedule in the cloud. Pipe output to Telegram, email, or any webhook. Every run is logged here with full output, cost, and thumbs feedback.

How this performs

Cloud-automation runs, real outputs, and feedback.

No cloud runs yet for this skill.

Once you deploy it (above), every run will show up here with the actual output, exact cost, and a thumbs button so you can rate quality over time.

what this is

Claude Code skill at /Users/olanrewajukareem/.claude/skills/calcom-setup-patterns/SKILL.md. Auto-triggered by description matching when you type in Claude Code, OR embedded into agent system prompts (LeadFlow framework skills are wired this way). Auto-synced from disk every 6h via launchd.

Use this skill when configuring Cal.com scheduling, including embedded vs hosted booking, routing forms, team scheduling, calendar integrations, and payment-gated bookings. Triggers on "Cal.com", "Calcom", "scheduling", "booking page", "Cal.com routi

Local Claude Code use (optional)

Install the SKILL.md file locally so this skill is available the next time you open Claude Code on your Mac. Most users skip this and just use cloud deployments above.

Install on your machine

Save this skill to ~/.claude/skills/calcom-setup-patterns/SKILL.md so Claude Code auto-loads it whenever its description matches your prompt.

30-day activity

never used

2026-04-03today

cost model

unitincluded

capabilities

{
  "source": "global",
  "description": "Use this skill when configuring Cal.com scheduling, including embedded vs hosted booking, routing forms, team scheduling, calendar integrations, and payment-gated bookings. Triggers on \"Cal.com\", \"Calcom\", \"scheduling\", \"booking page\", \"Cal.com routing\", \"Cal.com embed\", \"Cal.com setup\", \"appointment booking\". Different from generic scheduling tools because Cal.com is open-source and self-hostable."
}

how it gets called

{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/calcom-setup-patterns/SKILL.md"
}

This tool has never been called in the last 30 days.

That means either: (a) the system has not had a task that matched its strengths, (b) a more cost-effective alternative was picked by the router, or (c) the related automation is toggled OFF on /automations. The Recommender reviews idle tools weekly and may suggest killing it.