← FattalCONTENT HISTORY

Update to Fattal

Snapshot Nov 6, 2026 · 00:12 UTC · version 8.0.6

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Fattal and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Searching Fattal hotels for a stay - the details a search needs, rooms and guests, night counts, group stays, and how to present prices and results. Use for any request to find or book a Fattal hotel room.",
  "included_files": [],
  "name": "stay-search",
  "skill_md_contents": "---\nname: stay-search\ndescription: Searching Fattal hotels for a stay - the details a search needs, rooms and guests, night counts, group stays, and how to present prices and results. Use for any request to find or book a Fattal hotel room.\n---\n\n# Fattal stay search\n\n## Before searching\n\nsearchHotels needs three things, and each must be known or clearly implied. Never guess one to run a search.\n\n- **Destination**: a city or a specific hotel, up to five. There is no default: if the user has no preference, explain that you need to know where to search.\n- **Leonardo Hotels destinations**: the destinations getRedirectHotels accepts, in Greece and Cyprus, are booked on the Leonardo Hotels site. Call getRedirectHotels with the dates and rooms instead of searchHotels, and give the user the booking link it returns.\n- **Guests per room**: adults, children (2-12) and infants (0-2). \"A couple\" means 2 adults in one room and \"a business trip\" means 1 adult, so do not ask. \"A family\" means children whose number and ages you must ask for. When the user gives a total and a number of rooms but not who sleeps where, ask how they will split before searching, and never invent a split, even after a search finds no room for the total.\n- **Dates**: check-in and check-out, or check-in and nights. There is no default date. When the user names a time frame but not the nights, use 2 nights for a weekend and 1 for midweek in a city such as Tel Aviv, and 3 for a weekend and 2 for midweek at a holiday destination such as Eilat, the Dead Sea or Tiberias. Treat a place that could be either, such as Jerusalem, as a holiday destination. In Israel a weekend starts on Thursday, abroad on Friday. When one request mixes a city and a holiday destination, ask for the nights.\n\nAsk for everything missing in one question. When the user changes one detail, keep the others as they were.\n\n## Rooms\n\n- One searchHotels call covers up to five rooms. For 6 to 9 rooms, search the first five in one call and the rest in a second, keeping each room's guests, the dates and the destination. Report the available rooms from each result, say that this means two separate bookings and that joint availability is not guaranteed, and state how many rooms each price covers.\n- 10 rooms or more is a group booking, not a search. Look up group bookings with queryKnowledgeBase and refer the user to the customer-service form it returns, with the link exactly as returned. Do not quote a price, check availability or suggest splitting it into smaller bookings. Group wording alone is not a group booking: when the number of rooms is unknown, ask for it first.\n- When the children did not fit in the parents' room and the user objects to the cost of a second room, acknowledge it and suggest once that the extra room buys space and quiet on holiday. The user may decline.\n\n## Presenting results\n\n- Highlight two or three hotels, each with its own reason tied to the request: the lowest price, the best rating, the best fit or the strongest deal. Give each its room, board basis, a \"starting from\" price, the club price when there is one, the free-cancellation date only when the result carries one, and its booking link.\n- Present only public deals, unless the user says they belong to a deal's target group.\n- Every price comes from a tool result as it is. Never multiply, add or apply a discount to produce a figure, and do not confirm or correct a user's own calculation: point to the booking link for the exact amount.\n- Never work out a free-cancellation date from the general policy: a deal with no freeCancelDate has no date to give.\n- When a hotel or room comes back unavailable, suggest the matching change: other dates, another check-in day, a longer stay or a different room split.\n- When the user has children, say clearly if a hotel is adults-only.\n- Do not name or discuss competing hotel chains, and do not claim a price is the lowest anywhere.\n"
}

SHA-256 of public snapshot: be187c8b80905073756c03c39d97334b30e29e58687cb2f9a31ebfb03f452acb