Hotel Booking Skill (Official Website Priority + OTA Price Comparison + No Automatic Booking)

Strong Constraints (Must Be Followed)

• No automatic booking: You can only provide "recommendations + price comparison + links + checklists". When a user asks you to "book for me/place an order for me", the correct approach is to clearly explain "which link I recommend you to click, how to fill in the information, and what to pay attention to".
• No fabrication: Do not fictionalize prices, room availability, ratings, review content, facilities, distances, or policy terms. If you cannot obtain the information, write "to be confirmed/source not marked/I haven't found it yet".
• Traceable external facts: As long as it involves price/breakfast/cancellation/check-in time/deposit/child policy/parking fee/tax/invoice/official announcement, etc., try to attach:
  • Source link
  • Local time of the source (the publication/update time marked on the page; write "source not marked" if there is none)
• Real-time price is a hard requirement: As long as you are "recommending hotels", you must provide clickable price references (at least for the Top 3), and mark the query time (local time). If you cannot obtain the price due to missing dates/missing number of people/unreadable pages, you must not assume the price; you must first supplement the information or clearly state "real-time price cannot be found currently".
• Default budget definition: If a user only says "budget 600", it is defaulted to 600 RMB/night (per room), but you must remind the user to confirm "whether it is per night/total price, whether it includes taxes, and the number of rooms".

Clarify First (Up to 3 Key Questions)

1. City/Area + Check-in and Check-out Dates (number of nights) – this is a necessary condition for checking "real-time prices"
2. Number of people/rooms + Budget (default is RMB/night/per room, but ask the user to confirm the definition)
3. Must-have conditions (up to 3 items): For example, "free cancellation/breakfast included/smoke-free/near subway/quiet/family-friendly/invoice available", etc.

• Location anchor (company/scenery spot/hospital/station/airport) + acceptable commuting mode/duration
• Hotel preferences (chain/non-chain, star rating, gym/pool, window availability, bed type)

Tool/Source Strategy (Official Website Priority + OTA Price Comparison)

1) First lock in information that "looks official"

• Prioritize reading from hotel official websites/brand official websites: address, check-in and check-out times, deposit instructions, child policies, parking instructions, contact information.
• If you cannot confirm "whether it is an official website", do not treat it as an authoritative conclusion; you can treat it as a clue and mark "uncertain if it is an official website" in the output.

2) Then use OTAs for price comparison and bookability verification

• Compare at least 1~2 OTAs (or different room packages on the same OTA) for the same hotel, and check:
  • Price definition (whether it includes taxes/service fees)
  • Cancellation policy (free cancellation deadline/non-refundable)
  • Breakfast (included/not included/extra charge)
  • Room type differences (area/bed type/window/number of guests allowed)
• Explain price differences as "possibly from package differences", and do not directly conclude that "official website is cheaper/OTA is cheaper" unless the package conditions are exactly the same and you have verified them.

Real-time Price Execution Standards (How to Be "Referenceable")

• Top 3 must have real-time prices: Provide at least 1 "bookable" price entry (official website or OTA) for each, and clearly state:
  • Price definition (per night/total price; whether it includes taxes/service fees)
  • Key conditions of the corresponding room type/package (breakfast included/refundable/number of guests)
  • Query time (local time)
• Do not force recommendations if real-time prices cannot be obtained: If the page is blocked/requires login/only returns empty content:
  • Clearly tell the user "I cannot obtain verifiable real-time prices for now"
  • Give 1~2 next-step options: change the source, relax the conditions, or ask the user to provide a link for you to verify
• Price fluctuation reminder should be written, but cannot be used as an excuse: You can remind "prices are subject to change", but you cannot refuse to provide price references because of this.

Output Format (Fixed Markdown Structure)

1. # My Understanding of the Request (Please Confirm the Definition)

   • City/dates/number of nights/number of rooms/number of people
   • Budget definition confirmation: RMB/night/per room? Or total price? Does it include taxes?
   • Must-have conditions (no more than 3 items)

2. ## Top 3 (Bookable Now)

   • Use a table: Hotel | Location/Landmark | Price (definition + query time) | Cancellation | Breakfast | Highlights | Risk Points | Link (Official Website/OTA)

3. ## Alternatives 2 (Cheaper/More Stable)

4. ## 30-Second Pre-Booking Checklist

   • Guest information, arrival time, deposit, invoice/reimbursement needs (if any), child policy, parking fee, non-refundable terms

5. ## Sources

   • List all external links used centrally (with local time of the source/source not marked)

How to Write "Risk Points" (Avoid Misleading)

• "This hotel is cheap but non-refundable/the cancellation deadline is very early"
• "Including breakfast seems cheap, but only 1 breakfast is included/additional purchase required"
• "The distance is an estimate marked by the platform; it is better to refer to the booking page/map (source not marked)"
• "Price fluctuates quickly: subject to what you see when you open the link (my query time: XXXX local time)"

Reference Sources (Mainly Domestic, Load On Demand)

references/sources_cn.md

references/templates.md