← ClaudeAtlas

playo-bookinglisted

Propose, confirm and book badminton courts on Playo, send the user a payment link, and manage bookings they already have (list, details, cancel with a refund preview, reschedule). Use whenever the user asks about booking a court, a game or a slot, when they ask what is free, what they have booked, about cancelling, moving or refunding a booking, about their gift-card credit or karma points, and for the scheduled booking check-ins.
the-mrinal/agent-toolkit · ★ 0 · AI & Automation · score 70
Install: claude install-skill the-mrinal/agent-toolkit
# Booking a Playo court The `playo` MCP server owns every decision that involves money. You decide **when** to act and you do the talking; it decides **what** gets booked and at what price. Never assemble a booking yourself. ## The one rule **Never call `playo__book`, `playo__cancel_booking` or `playo__reschedule_booking` without an explicit yes from the user for that exact quote or that exact refund figure.** Each one changes something real and costs real money. Their reply to a proposal you just sent ("yes", "book it", "go ahead") counts. A general "book me something this weekend" or "sort out my bookings" does **not** — propose first, then wait for the reply. There is no separate confirmation UI here: the confirmation *is* their next message. So always end a proposal with a plain question, and never book in the same turn as the proposal. ## Normal flow 1. **Check the session.** `playo__auth_status` (free, no network). If `needsLogin` is true: send the user `fixHint` and **stop**. Nothing works until they run `npm run login` on their Mac. Do not retry other tools. 2. **Work out the dates first.** The tools take explicit `YYYY-MM-DD`; you resolve the words. In India time: - **"this weekend" / "the weekend"** = the **next Saturday and Sunday that still have bookable time**, searched as one range (`from` = Saturday, `to` = Sunday). Always look **forward**, never back: - Mon–Fri → the coming Sat + Sun. - Saturday → the rest of today + tomo