Update to Smart City Stays

{
  "description": "Find and price a Smart City Stays serviced apartment in Cape Town (Century City or the V&A Waterfront) for given dates, using live availability and direct rates, and hand the user a link to book on smartcitystays.com. Use when someone asks for a short-stay, corporate or family apartment in Cape Town, or asks what a named Smart City Stays apartment costs.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 493
    },
    {
      "relative_path": "references/apartments.md",
      "size_in_bytes": 1354
    }
  ],
  "name": "find-a-stay",
  "skill_md_contents": "---\nname: find-a-stay\ndescription: Find and price a Smart City Stays serviced apartment in Cape Town (Century City or the V&A Waterfront) for given dates, using live availability and direct rates, and hand the user a link to book on smartcitystays.com. Use when someone asks for a short-stay, corporate or family apartment in Cape Town, or asks what a named Smart City Stays apartment costs.\n---\n\n# Find a Smart City Stays apartment\n\nExplicit instructions from the user take priority over this guidance.\n\n## Tools\n\n- `search_stays` (Smart City Stays server): live availability and prices across the portfolio.\n  Inputs: `checkin`, `checkout` (YYYY-MM-DD), optional `area` (`waterfront`, `century-city` or `any`),\n  optional `bedrooms` (0 = studio, up to 3), optional `guests`.\n- `get_quote`: live price and every available rate for one named apartment.\n  Inputs: `area`, `roomTypeId`, `checkin`, `checkout`. Look up `area` and `roomTypeId` in\n  `references/apartments.md` (ids repeat across areas, so always pass both).\n\nBoth tools only read availability and prices. Neither books, holds or charges anything.\n\n## Workflow\n\n1. Get the dates. If the user gave no check-in or check-out date, ask for them before calling a tool.\n   Resolve relative dates (\"next weekend\", \"3 nights from 10 March\") to YYYY-MM-DD in Cape Town time.\n   Check-in must not be in the past and check-out must be after check-in.\n2. Map the request to filters:\n   - \"Waterfront\", \"V&A\", \"Marina\" means `area: waterfront`. \"Century City\" means `area: century-city`.\n     Anywhere else in Cape Town, or no area given, means `area: any`.\n   - \"Studio\" means `bedrooms: 0`. A named bedroom count maps directly.\n   - If only a group size is given, pass `guests` and let the tool choose a sensible bedroom count.\n3. If the user names a specific apartment, find it in `references/apartments.md` and call `get_quote`.\n   If the name is ambiguous or not in the table, call `search_stays` with the matching area and bedrooms instead.\n   Otherwise call `search_stays`.\n4. Present results clearly: apartment name, area, total for the stay and nightly rate in ZAR, and the book link\n   exactly as returned. Keep the tool's order (cheapest first). Do not invent prices, amenities or availability.\n5. If nothing is available, say so plainly and suggest nearby dates, another area, or a different size.\n\n## Limits\n\n- Only Smart City Stays apartments in Cape Town are covered. For other cities or other hotels, say this\n  app cannot help.\n- The app cannot book, cancel, change or pay for a stay. Bookings are completed on smartcitystays.com\n  through the book link. For existing bookings, point the user to https://www.smartcitystays.com/contact.\n- Never ask for or accept card details in the chat.\n"
}