{"id":87204,"plugin_id":"plugin_asdk_app_6ac7858900fc81919c8aa4b677d8a058","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-09T12:07:53.934Z","digest":"08c1f4f395f4d56b58ae570fec1084ee0f15db70668a2f093daf015596429796","against":null,"payload":{"description":"Compare Google Hotels or Booking.com hotel offers for dates and travelers, or inspect a supplied Booking property with HasData. Use for hotel research, not flights, homes for sale or making reservations.","included_files":[],"name":"hotel-research","skill_md_contents":"---\nname: hotel-research\ndescription: Compare Google Hotels or Booking.com hotel offers for dates and travelers, or inspect a supplied Booking property with HasData. Use for hotel research, not flights, homes for sale or making reservations.\n---\n\n# Compare hotels for the supplied stay\n\nRead `../hasdata-research/SKILL.md` and the Travel section of `../hasdata-research/references/tool-catalog.md`.\n\nUse `hasdata_google_travel_hotels_getGoogleHotels` with q, checkInDate and checkOutDate for Google Hotels. Booking discovery uses `hasdata_booking_search_getBookingSearchResults` with keyword; a supplied Booking property URL uses `hasdata_booking_place_getBookingPlaceDetails` without an unnecessary area search. Preserve the requested source; when unspecified, choose a suitable available source and state it rather than asking the user to select an API.\n\nIf the user has not named a source or room count, prefer Google Hotels, whose schema does not require rooms. For an explicitly requested Booking stay with a complete party but no room count, a one-room comparison may be used only as a clearly stated assumption when that party reasonably fits one room; ask when multiple rooms or occupancy would materially change the result. Preserve any supplied room count and never present an assumption as user-provided.\n\nCollect materially missing dates and party details before a priced-stay query. Booking search and details both require rooms, adults and children. When children > 0, get every child's age and pass childrenAges as a comma-separated list, one age 0-17 per child. Google Hotels also has childrenAges; use its own live schema. Never silently switch to an adults-only stay.\n\nEncode zero children by source. Booking requires children:0 for a supplied adults-only party. Google Hotels rejects explicit children:0; omit children and childrenAges when there are no children, but preserve any positive child count and supplied ages. Google Hotels has no rooms input in the checked schema; do not pass it or claim that a requested room count was applied. State that limitation when room count matters to the comparison.\n\nApply only source-specific actual filters and returned tokens. Keep names, dates, occupancy, currency and rate basis with offers. Distinguish nightly from whole-stay prices and show excluded taxes/fees when returned; unknown charges are not zero. No stock or cancellation guarantee from a snapshot, and no reservation/payment actions.\n\nFor explicitly requested Airbnb rentals use `../airbnb-research/SKILL.md`; homes for sale or long-term housing use `../property-research/SKILL.md`.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}