Update to TravelYalla

{
  "description": "Search and compare live TravelYalla hotel prices by city or hotel name, filter by stars, guest score, price or distance, and give travelyalla.com booking links. Use for any request for hotels, stays, accommodation or a hotel's details, in English or Arabic (فنادق، فندق، حجز فندق، إقامة، أرخص فندق), especially in Egypt, Saudi Arabia (including Makkah and Madinah) and the Gulf.",
  "included_files": [
    {
      "relative_path": "references/booking-links.md",
      "size_in_bytes": 1224
    }
  ],
  "name": "find-hotels",
  "skill_md_contents": "---\nname: find-hotels\ndescription: \"Search and compare live TravelYalla hotel prices by city or hotel name, filter by stars, guest score, price or distance, and give travelyalla.com booking links. Use for any request for hotels, stays, accommodation or a hotel's details, in English or Arabic (فنادق، فندق، حجز فندق، إقامة، أرخص فندق), especially in Egypt, Saudi Arabia (including Makkah and Madinah) and the Gulf.\"\n---\n\n# Find hotels\n\nTools: `search-destinations`, then `search-hotels`, then `get-hotel-details` for a hotel the user wants to know more about.\n\nExplicit user instructions take priority over the defaults here.\n\n## 1. Collect the stay\n\nYou need these before searching:\n\n- **Destination.** A city, area or hotel name.\n- **Check-in and check-out dates.** Resolve relative dates against today's date. Never use past dates. \"Next weekend\" means Friday to Sunday unless the user's region suggests Thursday to Saturday. State which dates you used.\n- **Guests per room.** If the user doesn't say, assume 2 adults in 1 room and tell them so. Children need their ages, from 0 to 17.\n\nIf the destination or the dates are missing, ask for them in one short question.\n\n## 2. Resolve the destination\n\nCall `search-destinations` with what the user said.\n\n- Take a hit with `type: \"city\"`. Use its `code` as `city` and its `country.code` as `country_code`.\n- If the user named a hotel, take the hotel hit's city code and country, and remember the hotel's name so you can find it in the results.\n- If several cities share the name, for example London in GB and London in US, pick the one the context points to. Ask if it's unclear.\n\n## 3. Search\n\nCall `search-hotels` with:\n\n- `city`, `country_code`.\n- `check_in`, `check_out` as `DDMMMYYYY` in upper case, for example `16OCT2026`.\n- `rooms`: one entry per room, for example `[{\"adults\": 2, \"children\": [7]}]`.\n- `nationality`: the guest's own country as ISO-2, not the destination's. Rates and the default currency depend on it. Use it if known. Otherwise search anyway and offer to re-run.\n- `currency`: only if the user asked for one. Never default to the destination's currency.\n- `language`: `ar` when the user writes in Arabic.\n- `sort_by` and `sort_dir`:\n  - `price` / `asc` for \"cheap\" or \"budget\"\n  - `stars` / `desc` for \"luxury\" or a star level\n  - `rated` / `desc` for \"best\" or \"top-rated\" (also the default)\n  - `distance` / `asc` for \"central\" or \"near the centre\".\n- `limit`: 10. Raise it when filters leave too few results.\n\nThe search takes about 20–30 seconds, so tell the user once.\n\nIf the search fails (for example \"no provider answered\"), retry once. If it still fails, say so and suggest other dates. Never invent hotels or prices.\n\n## 4. Present the results\n\nShow the 3–6 best matches. For each one, give:\n\n- `name` and `stars`\n- guest score as `review_score` from `review_count` reviews, when present\n- `distance_to_center_km`, when present\n- price per night (`night`) and the stay total (`total` for `nights` nights) in `currency`.\n\nApply the user's filters to the returned data, such as stars, maximum price or minimum score, and say how many hotels matched. Prices are live and can change until booked.\n\nFor a landmark such as \"near the British Museum\", `distance_to_center_km` measures distance from the city centre, not from the landmark. Use `get-hotel-details` coordinates for the top few candidates and describe nearness only approximately.\n\n## 5. Details\n\nCall `get-hotel-details` with a hotel's `code` when the user asks about it. Report its address, check-in and check-out times, and facilities.\n\nRoom types, board and cancellation terms are not available here. Send the user to the hotel's page for those.\n\n## 6. Booking link\n\nGive each hotel you recommend a travelyalla.com link built as described in [references/booking-links.md](references/booking-links.md). The user books and pays on the website. Never collect payment details in the chat.\n"
}