SKILL.md

---
name: kismet-booking-integrity
description: Pricing and booking truthfulness rules for Kismet stays. Use WHENEVER money, availability, fees, quotes, or booking links come up — any "how much", "is it available", "can we book", "which is cheaper", or price comparison between properties, even mid-conversation after a search. Covers dated totals vs nightly anchors, fee enumeration (pet, cleaning, taxes), booking-rule gates before issuing links (minimum stay, minimum booking age, payment and cancellation terms), and rejected-dates recovery.
---

# Kismet Booking Integrity

The guest will act on your numbers and your links. Both must survive contact
with the manager's checkout page.

## Price talk

- Search results show **per-night figures** (anchors in browse mode, dated
  rates with `dateWindows`). Never compare or recommend on per-night figures
  alone. Get a **dated total** first —
  `get_bookable_detail` with checkIn/checkOut returns total including
  estimated taxes.
- **Enumerate only fees returned by the tool.** If the response includes a pet
  fee or another stay-specific charge, fold it into the effective total before
  comparing properties and show the arithmetic clearly. Never infer a fee from
  what is common elsewhere or add a charge the manager has not returned.
- Say "including estimated taxes" when that's what the total is. Never
  present an estimate as an invoice.
- Savings claims belong to whoever makes them. A collection's own copy may
  claim "save 15–20% vs Airbnb fees" — attribute it ("the manager's copy
  says…"), don't assert it as a Kismet-wide fact.

## Gate every booking link

Before calling `get_booking_link`, check the property's booking rules from
`get_bookable_detail` — and pass the property's collection in `collections`
(the slug is on each search result as `collectionSlug`); the tool can derive
it from the property slug otherwise:

1. **Minimum stay** — if the guest's window is shorter, do NOT issue the
   link. Tell them the minimum, offer the nearest compliant window, and
   reprice it. (Server-side validation via `datesRejected` exists in the
   contract but treat yourself as the last line of defense.)
2. **Minimum booking age** — commonly 21 even where guest age minimum is 18.
   If the booker might be under it, say so before they hit the wall.
3. **Payment schedule** — e.g. 50% at booking, remainder 30 days out; 100%
   inside 30 days. Volunteer this when the trip is near-term.
4. **Cancellation terms** — surface the refund cutoff whenever the guest is
   deciding between options or booking far ahead.

If a link request comes back with `datesRejected`, offer any returned
alternate windows verbatim. If none are returned, hand the guest the
property's calendar link from the same response, or re-search with compliant
`dateWindows` — never improvise availability, never guess that "nearby dates
are probably open."

## Deliver the link — clickable, dated, tool-minted

A decision point deserves a link, not directions. When the guest has a
property and a rules-compliant window — or asks to book, reserve, or check
availability — mint it with `get_booking_link` and hand it over; don't make
them ask twice.

- **Only tool-minted links.** The minted link is validated against live
  availability and booking rules, deep-links the exact dates, and carries
  the guest's session so their context continues on the manager's site. A
  remembered or hand-built URL can point at the wrong property, the wrong
  dates, or a stay the checkout will refuse.
- **Present it as a clickable Markdown link on its own line** — anchor text
  is the property name + dates, dated total adjacent per Price talk:

  [View & book Riverbend Cabin · Oct 16–18](…) — $756 total incl.
  estimated taxes for 2 nights.

  Never paste a bare URL, never describe where to click instead of
  linking, never send the guest to "search the site."
- The dated link lands on the property's own checkout with those exact
  dates pre-filled, so what the guest sees there is the manager's live
  price for the stay you discussed. Say the dates in the anchor so the
  guest can verify at a glance.
- Rejection recovery follows the same rule: present the returned calendar
  link clickable, alongside the alternate windows.
- Link what the guest is deciding on — one clear link beats five.

## Never

- Never invent availability, rates, or fees not returned by a tool.
- Never present browse-mode (dateless) results in a price discussion.
- Never issue a link you have reason to believe the checkout will refuse.
- Never hand-construct, edit, or shorten a booking URL — only links minted
  by `get_booking_link` (or returned by a tool) go to the guest.