用空位“雷达”替你抢旅游目的地的米其林/热门餐厅

旅行目的地米其林与热门餐厅空位监控、自动预约与定金提醒助手。 收集用户旅行日期、目的城市、人数与用餐偏好后，自动匹配米其林/热门餐厅清单， 持续监控空位并尝试自动预约，需要定金或确认时通过短信/Push 通知用户。 当用户提到"餐厅预约""米其林订位""旅行餐厅""热门餐厅预定""自动订餐厅""抢位" "餐厅空位...

This skill's goal (monitoring and attempting restaurant bookings) is reasonable, but before installing or using it you should ask the developer to clarify a few concrete details: 1) How will outbound notifications be sent? (Which SMS/Push/IM provider will be used? Will the skill require you to supply API keys such as Twilio/SendGrid/Push service tokens?) 2) How are verification codes handled in practice? (If the skill 'auto-reads' or requests forwarding of SMS codes, what channel is used and is that channel secure? Will the skill ever ask you to paste OTPs into the chat?) 3) How are payment/credit-card details handled and transmitted? (Prefer never to type full card numbers into chat — require a secure payment flow or redirect to the restaurant/payment provider.) 4) Will the agent need your accounts or passwords for booking platforms, and if so, how will those credentials be stored/used/rotated? 5) Request a data-flow diagram and a retention policy: what is logged, for how long, and where are logs stored/encrypted? 6) Confirm who pays for SMS costs and whether two-way SMS commands can trigger charges. If the developer cannot clearly list the external services used and how credentials are handled, treat the integration as risky. As a safety measure, avoid providing full credit-card or account passwords in chat; prefer manual confirmation flows for payments and OTPs, and only provide minimal personal contact info required for a given booking.

Type: OpenClaw Skill Name: restaurant-reservation-radar Version: 1.0.0 The 'restaurant-reservation-radar' skill bundle is a well-documented tool designed to help users monitor and book high-demand restaurant reservations globally. It collects necessary PII (phone number, email) and preferences to automate interactions with legitimate booking platforms like Tabelog, TheFork, and OpenTable, as detailed in SKILL.md and reference.md. The instructions include explicit safety constraints, such as requiring user confirmation for payments and prohibiting the persistent storage of sensitive data, with no evidence of malicious intent or prompt injection.