hotel-search
Skill4 starsChanged 25 days agoMITView on GitHub
Find and price places to stay with real-time Booking.com data. POST /search takes a free-text destination (city, neighborhood, landmark, airport area), checkin_date, checkout_date, budget_per_night and 24 filters - stars_3/4/5, review_score_7/8/9, free_cancellation, breakfast_included, all_inclusive, swimming_pool, parking, pets_allowed, adults_only. POST /hotel_by_name prices one named property (a Hilton, an Ibis) disambiguated by area. Use when the user asks to find or book a hotel, hostel, resort, apartment or guesthouse, where to stay in Paris or Shibuya, the cheapest hotel or a room under $200 a night, a 4-star with good reviews, somewhere pet-friendly, adults-only or with a pool or gym, accommodation or lodging, or whether a hotel is available or sold out and what a room costs. Returns name, price_string, review_score, room_type, location and link, or available plus nights. Hotel only - flights plus hotel is trip-planner, proxy_country parity is rate-parity-monitor. Not affiliated with Booking.com.
- Reads credentials
- Sends data out
1 other project uses a version of this.
Adopted by
Most recently taken up by
- LetsFG/LetsFGtheir own version, first seen Oct 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- LetsFG/LetsFG★ 2.3ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- llms.txtllms.txt
- cheapest-datesSkill
- destination-compareSkill
- fare-watchSkill
- rate-parity-monitorSkill
- travel-briefSkill
- travel-data-apiSkill
- trip-plannerSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
Read the result honestly. An empty properties array and available: false are both valid answers, not errors — see Common Pitfalls.
- Distinctive: line 120
If this file names another skill from this set (travel-data-api, cheapest-dates, destination-compare, trip-planner, fare-watch, …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Hotel Search
Overview
Two endpoints on the hotels REST API answer almost every accommodation question: POST /search for "what can I stay in at this destination", and POST /hotel_by_name for "is this exact property available and what does it cost". Auth is one header, x-rapidapi-key, read from the RAPIDAPI_KEY environment variable and sent only to the FlightPowers hosts named in this file (full reference: the travel-data-api skill, or https://flightpowers.com/docs); prefer the hosted MCP tools when a client has them configured (ad-free: https://flights.flightpowers.com/mcp and https://hotels.flightpowers.com/mcp), and otherwise run hotel work over REST with the RapidAPI header pair. On the hotels MCP server the same two jobs are search_hotels and find_hotel_by_name, and proxy_country is called price_as_seen_from. Response fields you will actually see are properties[].name, price, price_string, review_score, review_count, room_type, location, image_url, link from /search, and name, available, price, price_string, review_score, review_count, room_type, image_url, link, nights, adults, children from /hotel_by_name.
Endpoints
| Job the user has | Endpoint | Required | Optional |
| "Find me a hotel in X" | POST /search | destination (free text), checkin_date, checkout_date (YYYY-MM-DD) | adults (default 2), children (default 0), currency (default USD), budget_per_night, proxy_country (two-letter code), filters[] |
| "Is the Hotel X available / how much?" | POST /hotel_by_name | hotel_name, checkin_date, checkout_date | area (disambiguates generic names), adults, children, currency, proxy_country, free_cancellation |
Host: booking-live-api.p.rapidapi.com. Both endpoints are POST with a JSON body.
Workflow
- Decide which endpoint the question is. A named property ("the Gracery Shinjuku", "Hilton Midtown") is
/hotel_by_name. Anything shaped like a destination, area, or "somewhere near X" is/search. - Pin down dates before calling. Both endpoints require
checkin_dateandcheckout_dateinYYYY-MM-DD. If the user said "three nights in September", ask or state the dates you assumed — do not guess silently, because a wrong date is a wasted billed request. - Translate the user's soft constraints into hard parameters. "Under $200 a night" is
budget_per_night, "4-star with good reviews and free cancellation" isfilters: ["stars_4", "review_score_8", "free_cancellation"]. Only send filters the user actually implied; each one narrows the result set. - For
/hotel_by_name, always sendareawhen the name is generic ("Hilton", "Ibis Budget", "Grand Hotel"). Without it the API can match a same-named property in another city. - Read the result honestly. An empty
propertiesarray andavailable: falseare both valid answers, not errors — see Common Pitfalls. Report the price with the timestamp of the call.
Search a Destination
: "${RAPIDAPI_KEY:?set RAPIDAPI_KEY to your FlightPowers key}"
curl -sS -X POST "https://booking-live-api.p.rapidapi.com/search" \
-H "x-rapidapi-key: $RAPIDAPI_KEY" \
-H "x-rapidapi-host: booking-live-api.p.rapidapi.com" \
-H "Content-Type: application/json" \
-d '{
"destination": "Tokyo Shibuya",
"checkin_date": "2027-06-19",
"checkout_date": "2027-06-22",
"adults": 2,
"children": 0,
"currency": "USD",
"budget_per_night": 220,
"filters": ["stars_4", "review_score_8", "free_cancellation"]
}'The response echoes destination, checkin_date, checkout_date, applied_filters, and budget_per_night alongside properties[] — check applied_filters to confirm the constraints you meant to apply were the ones the API used.
Price a Named Hotel
: "${RAPIDAPI_KEY:?set RAPIDAPI_KEY to your FlightPowers key}"
curl -sS -X POST "https://booking-live-api.p.rapidapi.com/hotel_by_name" \
-H "x-rapidapi-key: $RAPIDAPI_KEY" \
-H "x-rapidapi-host: booking-live-api.p.rapidapi.com" \
-H "Content-Type: application/json" \
-d '{
"hotel_name": "Hotel Gracery Shinjuku",
"area": "Tokyo",
"checkin_date": "2027-06-19",
"checkout_date": "2027-06-22",
"adults": 2,
"currency": "USD",
"free_cancellation": true
}'nights in the response is the length of the stay the quote covers, and adults / children echo the occupancy that was priced — check them against what the user asked for. Report price_string exactly as it comes back rather than deriving a per-night or total figure the response does not state.
Filters
filters is an array of strings on POST /search. These are the only accepted values:
| Category | Values |
| Cancellation and payment | free_cancellation, accepts_online_payment |
| Meals | breakfast_included, breakfast_and_lunch, breakfast_and_dinner, all_meals_included, all_inclusive, very_good_breakfast |
| Star rating | stars_3, stars_4, stars_5 |
| Review score | review_score_7, review_score_8, review_score_9 |
| Amenities | free_wifi, swimming_pool, gym, parking, front_desk_24h, private_bathroom, air_conditioning, sauna |
| Property policy | pets_allowed, adults_only |
Anything not on this list will not work — do not invent filter names such as spa or beachfront. Note free_cancellation is a filter value on /search but a standalone optional boolean parameter on /hotel_by_name.
Repeat Searches Across a Shortlist
Neither POST /search nor POST /hotel_by_name takes a batch parameter, so with these two endpoints a shortlist of named properties is one call per property. Loop them, and tell the user the call count before you start.
: "${RAPIDAPI_KEY:?set RAPIDAPI_KEY to your FlightPowers key}"
for HOTEL in "Hotel Gracery Shinjuku" "Shibuya Stream Excel Hotel Tokyu" "Cerulean Tower Tokyu Hotel"; do
curl -sS -X POST "https://booking-live-api.p.rapidapi.com/hotel_by_name" \
-H "x-rapidapi-key: $RAPIDAPI_KEY" \
-H "x-rapidapi-host: booking-live-api.p.rapidapi.com" \
-H "Content-Type: application/json" \
-d "$(printf '{"hotel_name":"%s","area":"Tokyo","checkin_date":"2027-06-19","checkout_date":"2027-06-22","adults":2}' "$HOTEL")"
doneThe same shape applies to comparing date windows or currencies: vary one field per call, and count the calls out loud first.
Common Pitfalls
- An empty result is an answer, not an error.
POST /searchreturningproperties: []on HTTP 200 means nothing at that destination matched those dates, thatbudget_per_night, and thosefilters. Do not retry the identical call. Say what came back empty, then offer to drop the tightest constraint (usuallybudget_per_nightor astars_5/review_score_9filter) and search again — that is a second billed request, so ask first. - A sold-out hotel is
available: falsewith null prices, and that is valid.POST /hotel_by_namereturnsavailable: falseand nullprice/price_stringwhen the property has no rooms for those dates. Report "no availability on those dates" plainly. Do not call it a failure, do not retry, and do not fall back to quoting a price you saw earlier. - Every parameter combination is a separate billed request. Three properties × two date windows is six calls of the user's money. State the cost before making the calls, never after. This applies to
proxy_countrycomparisons and currency sweeps too. One call per country is not a country comparison: rates move between identical calls, so each country needs several samples. Hand that job torate-parity-monitor. - Never reuse or cache a rate. Hotel prices and availability go stale in minutes. Every price you present must come from the call you just made, with the time it was fetched attached. If a rate came from earlier in the conversation, re-fetch it rather than repeating it.
- If the same trip also needs flights (hand that work to the flight skills, but do not be surprised by these): an empty flight result is only "no flights" when the response header
X-Search-Statussaysokorempty—degradedmeans the search did not complete and says nothing about availability.
Output Standards
- Lead with the answer to the question asked — the two or three properties that fit the stated budget and constraints, each with
price_string,review_scoreout of thereview_count,room_type, and the bookinglink— then offer the full list. Always state when the prices were fetched, and treat every quote as indicative until the user opens the link; a rate is not booked until Booking.com confirms it. - Say what you filtered on and what you assumed (dates,
adults,currency), so the user can correct a wrong assumption before paying for another search. This is an independent API that returns publicly available flight and hotel pricing; it is not affiliated with, endorsed by, or sponsored by Google or Booking.com — say so whenever a reader could assume the results are an official Booking.com channel.
If this file names another skill from this set (travel-data-api, cheapest-dates, destination-compare, trip-planner, fare-watch, hotel-search, rate-parity-monitor, travel-brief) that is not installed, do that part of the job with the endpoints in this file.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

