메뉴
Manage discovery call scheduling using booking_engine.py — a self-hosted Cal.com replacement backed by Supabase. Covers opening slots, booking leads, sending reminders, and completing meetings.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Intelligent routing between Bravo and Codex — decides when to delegate tasks to Codex vs handle internally
Secrets and authentication management. Ensures API keys, tokens, and credentials are NEVER exposed in plain text. Use when handling any credential, API key, or sensitive configuration.
Use when CC asks to create a new agent, scaffold a new agent repo, or clone Bravo's architecture for a new domain (client agent, sibling agent, specialized agent). Generates a new AI-agent repo from templates, wires it into C_SUITE_ARCHITECTURE.md and brain/APP_REGISTRY.md, preserves the V5.6 outbound chokepoint, and gives the new agent a doctor command on day one.
Claims-based access control for multi-agent coordination. Defines what each agent can read, write, execute, and spawn. Enforces least-privilege: agents only access what they need. Use when: spawning agents, multi-agent tasks, security-sensitive operations. Skip when: single-agent inline work, trivial tasks.
Build and maintain product-grade agent infrastructure: onboarding diagnostics, runtime home, packaging, skill lifecycle, tool manifests, and agent scaffolds.
Spawn and coordinate Claude Code Agent Teams (experimental) — parallel subagents for complex multi-domain tasks
| name | booking-management |
| description | Manage discovery call scheduling using booking_engine.py — a self-hosted Cal.com replacement backed by Supabase. Covers opening slots, booking leads, sending reminders, and completing meetings. |
| triggers | ["booking","calendar","schedule","discovery call","slot","reminder","appointment","meeting"] |
| tier | standard |
| dependencies | ["lead-management","email-marketing"] |
booking_engine.py replaces Cal.com with zero subscription cost. Slots and bookings are stored in the Supabase bravo project. The engine handles the full lifecycle: open slots, confirm bookings, send email reminders, and log meeting outcomes back to the lead record. Run remind daily in the heartbeat to catch same-day and next-day meetings automatically.
All operations go through python scripts/booking_engine.py. Append --json to any command for machine-readable output.
| Operation | Command |
|---|---|
| Open a single day of slots | booking_engine.py slots open --date 2026-03-24 --start 10:00 --end 16:00 --interval 30 --type discovery |
| Open a full week of slots | booking_engine.py slots open-week --start-date 2026-03-24 --days mon,tue,wed,thu,fri --start 10:00 --end 16:00 --interval 30 --type discovery |
| List slots | booking_engine.py slots list --available-only --type discovery |
| Close a slot | booking_engine.py slots close <slot_id> |
| View available slots (next N days) | booking_engine.py available --type discovery --next 7 |
| Operation | Command |
|---|---|
| Book a slot for a lead | booking_engine.py book <slot_id> --name "John Smith" --email "john@acme.com" --lead-id uuid --notes "Interested in AI automation" |
| Cancel a booking | booking_engine.py cancel <booking_id> --reason "Rescheduled" |
| List upcoming bookings | booking_engine.py list --status confirmed --upcoming |
| View a booking | booking_engine.py view <booking_id> |
| Mark meeting complete | booking_engine.py complete <booking_id> --notes "Great call. Sending proposal Monday." |
| Operation | Command |
|---|---|
| Send due reminders | booking_engine.py remind |
discovery (20-30 min calls).booking_engine.py slots list --date YYYY-MM-DD then slots close <slot_id> for each empty one.The standard flow for converting a hot lead into a booked call:
qualified status in lead_engine (lead_engine.py update <lead_id> --status qualified)booking_engine.py available --type discovery --next 7 --jsonbooking_engine.py book <slot_id> --name "..." --email "..." --lead-id <lead_id>email_engine.py send --to <email> --subject "Discovery Call Confirmed" --body "..." --lead-id <lead_id>lead_engine.py interact <lead_id> --type meeting --channel phone --subject "Discovery call booked"The engine stores a meeting_link field on each booking. Populate it with the Google Meet or Zoom link when sending the confirmation.
Run booking_engine.py remind daily — ideally in the morning heartbeat. It sends reminder emails to all leads with confirmed bookings due in the next 24 hours, using the email_engine.py send flow internally.
Reminders fire once per booking (the reminder_sent flag prevents duplicates). If a reminder fails (email bounce, SMTP error), it is logged with status=failed and the flag stays false — it will retry on the next remind run.
After every discovery call, run this sequence within 2 hours while the conversation is fresh:
booking_engine.py complete <booking_id> --notes "Discussed X, pain point is Y, budget is Z"lead_engine.py update <lead_id> --status proposal --notes "Call complete. Sending proposal."lead_engine.py interact <lead_id> --type meeting --channel phone --subject "Discovery call"Meeting notes on complete are stored against the booking record. Pull them back when writing a proposal: booking_engine.py view <booking_id>.
qualified; post-meeting, update the lead status immediately--lead-id to keep the interaction log accuraterevenue_engine.py log-revenue the day the contract is confirmedAll outbound communications (emails, notifications, messages) referenced in this skill MUST be routed through
scripts/integrations/send_gateway.py. Directsmtplibor raw SMTP calls are architecturally prohibited (V5.6 chokepoint rule). Use:python scripts/integrations/send_gateway.py send --channel email --to <email> --subject "..." --body "..." --lead-id <uuid>See [[skills/send-gateway/SKILL.md]] for the full contract.