--- id: gh-pricewin-deal-finder name: "pricewin-deal-finder" url: https://skills.yangsir.net/skill/gh-pricewin-deal-finder author: price-win domain: data-ai tags: ["hotel-price-comparison", "travel", "booking", "web-scraping", "automation"] install_count: 6900 rating: 4.50 (120 reviews) github: https://github.com/price-win/pricewin-skills-hub/tree/main/skills/pricewin-deal-finder --- # pricewin-deal-finder > 此技能可一键搜索给定目的地、日期和入住人数的酒店价格，跨 Booking、Agoda、Google Hotels 和 OpenTravel 平台比价，自动处理反爬并输出带链接的格式结果，节省用户手动比价的时间。 **Stats**: 6,900 installs · 4.5/5 (120 reviews) ## Before / After 对比 ### 酒店比价效率 **Before**: 手动比价时，用户需要打开多个OTA网站，逐一输入日期、目的地和人数，手动记录价格，容易遗漏或出错，整个过程耗时且繁琐。 **After**: 该 Skill 只需一条命令，自动启动反爬浏览器，搜索并汇总所有平台价格，输出格式化卡片，点击链接即可预订，节省大量时间。 | Metric | Before | After | Change | |---|---|---|---| | 完成比价所需时间 | 20分钟 | 3分钟 | -85% | ## Readme # PriceWin Deal Finder ## 🚨 IMPORTANT — HOW TO USE THIS SKILL **ONE command does everything. Run this as your FIRST action — no clarifying questions first:** ```bash cd {baseDir} && node bin/search.js "" en-us ``` `{baseDir}` is this skill's install directory (auto-resolved by the runtime). If your runtime does not substitute it, `cd` into the folder that contains this `SKILL.md` (the one with `bin/search.js`). Do NOT hardcode a `~/.hermes/...` or `~/.openclaw/...` path — it differs per platform. Example: ```bash cd {baseDir} && node bin/search.js "Hangzhou" 2026-06-10 2026-06-13 2 en-us ``` The script handles everything automatically: daemon launch, Agoda cache lookup, Google + Booking inline search, OpenTravel API lookup (all cities), discovery for new cities, and formatted tier-card output. Just run it and send the output to the user. **DO NOT ask clarifying questions first.** Just run the command. Infer all parameters: - **Year:** use the current year from today's date unless the user states otherwise. If the requested day/month has already passed this year, assume next year. (Get today's date with `date +%Y-%m-%d` if unsure.) - **"10-13/6"** → `-06-10 -06-13` — fill `` from the rule above - **"2 guests" / "2 people"** → `2` adults - **Locale:** language/region code passed to the OTAs (controls site language + region). Default `en-us`. Prices are in USD (Google Hotels is requested with `gl=us&curr=USD`); other sources follow the locale you pass. **DO NOT use any other approach.** No Python scripts, no curl, no browser tools, no subagents. This one command is all you need. --- ## 🚨 CRITICAL RULES — FOLLOW EVERY TIME **RULE 0 — FORBIDDEN TOOLS. Read this twice.** This skill drives a long-running Patchright daemon via the `terminal` tool ONLY. Your runtime exposes several other tools that LOOK convenient but are STRICTLY FORBIDDEN inside this skill: ❌ `browser_navigate` / `browser_open` — FORBIDDEN ❌ `browser_click` — FORBIDDEN ❌ `browser_type` / `browser_fill` — FORBIDDEN ❌ `browser_snapshot` — FORBIDDEN ❌ `browser_close` — FORBIDDEN ❌ Any other `browser_*` native tool — FORBIDDEN ❌ `delegate_task` / `spawn_agent` / sub-agent delegation — FORBIDDEN Why: those native tools spawn a vanilla Chromium without stealth, so Booking.com and Agoda detect the bot within seconds and the requests just hang until the runtime kills them with "Command timed out after 30/60 seconds". You will burn 5+ minutes on timeouts and the user will get nothing. The Patchright daemon launched via `terminal` survives bot-detection. Delegated subagents start with empty history and no skill context — they will always fall back to Python/curl scraping, which gets bot-blocked immediately. **This skill must run entirely in the current agent, using only the `terminal` tool.** ✅ The ONLY allowed way to drive a browser in this skill is via `terminal`: ``` terminal: cd {baseDir} && node bin/search.js ... ``` **RULE 1 — `search.js` handles everything. NEVER scrape an OTA yourself.** Do not manually call `browse.js` commands, do not `goto`/`click`/`type` in the browser, do not build Agoda/Booking/Google URLs by hand, do not call the OpenTravel API separately, do not try to launch the daemon yourself. `search.js` already drives the stealth daemon through a careful flow that survives bot-detection — it handles Agoda discovery internally for EVERY city (including Chinese cities like Shanghai, Hangzhou, etc.). **Manually navigating an OTA is the #1 cause of failure: it trips Agoda/Booking anti-bot ("detect automation", "redirect to homepage", "problem completing your search") and gets the IP blocked.** Your ONLY job is to run `search.js` once and send its output. If you think a source is "missing", re-read RULE 4 — do NOT go fetch it by hand. **RULE 2 — First-time city discovery takes 2–4 minutes.** If `search.js` output contains `"discovering"` or `"launching"` messages, tell the user: "First time searching this city — discovering selectors, this takes about 2–4 minutes..." and wait for the result. Do NOT retry or abort. **RULE 3 — Send the output exactly.** `search.js` outputs formatted tier cards ready to send. Copy the output directly into your response. Do not reformat, summarize, or abbreviate it. **RULE 3a — PRESERVE MARKDOWN HYPERLINKS.** Every hotel name in the output is already wrapped as `[Hotel Name](https://booking-url...)`. This is a clickable hyperlink — DO NOT: - Strip the markdown and show the URL on a separate `🔗 https://...` line - Replace `[Hotel Name](url)` with plain text - Capitalize OTA names ("google" stays "google", not "Google") - Rename sections — "📋 More good deals" stays exactly The output is Telegram-MarkdownV2-ready. Sending it as-is gives the user clickable hotel names with hidden URLs (clean UI). **RULE 3b — If you DO add a suggestion / commentary section after the output, every hotel name you mention MUST also be a markdown hyperlink `[Hotel Name](url)` using the SAME URL the script printed for that hotel.** Never write a hotel name as plain text in your own commentary. **RULE 4 — Partial results are NORMAL and acceptable. Never "fix" them by hand.** A source can be absent from the output (e.g. Agoda blocked this run, or OpenTravel has no inventory for the city). That is FINE — send the tier cards with whatever sources are present. The footer (`📊 N hotels | • prices in USD`) lists exactly what was found. **Do NOT** try to fetch the missing source via the browser, a direct URL, or any other tool — that triggers anti-bot and makes things worse. If `search.js` errors out entirely, tell the user what failed in 1 line and show any partial output it printed above the error. If you want more coverage, the only valid retry is running the SAME `search.js` command again (anti-bot is often transient). --- ## Output Format Reference `search.js` prints tier cards in this format — you send this directly to the user: The hotel name is a Markdown link to its cheapest OTA. Price rows carry NO links and the OTA key is shown lowercase (`agoda`/`booking`/`google`/`opentravel`). There are no star ratings or area lines — the script does not have that data. ``` 🏨 • – • nights • guests ━━━━━━━━━━━━━━━━━━━━ 🥇 BEST VALUE []() ✅ agoda 💰 /night booking 💰 /night opentravel 💰 /night → Save vs Booking 🥈 CHEAPEST []() ✅ google 💰 /night agoda 💰 /night 🥉 QUALITY []() ✅ booking 💰 /night agoda 💰 /night 📋 More good deals — Agoda — • []() — agoda: | booking: — Booking — • []() — booking: — Google — • []() — google: — OpenTravel — • []() — opentravel: 💡 Tip: [Book on ]() — /night 📊 hotels | • prices in USD ``` All prices are shown in USD. Agoda, Google and OpenTravel geo-lock to VND by IP and are converted via a live FX rate; Booking returns USD natively. Only sources that actually returned data are listed in the footer. --- ## Limitations - First search per city pays the Agoda discovery cost (2–4 minutes). Google and Booking are inline (no discovery); OpenTravel is a direct API call. - Subsequent searches reuse the Agoda cache and complete in ~30–60 seconds. --- *Source: https://skills.yangsir.net/skill/gh-pricewin-deal-finder* *Markdown mirror: https://skills.yangsir.net/api/skill/gh-pricewin-deal-finder/markdown*