Restaurant Booking - OpenTable
v1.0.2Book restaurant tables on OpenTable via the browser tool. Handles hidden time slots and terms checkboxes with JS evaluate fallbacks. Works with a logged-in s...
⭐ 0· 116·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (OpenTable booking) align with requirements and instructions. The only declared requirement is browser.enabled (the browser tool/profile), which is necessary for in-browser JS evaluation and clicking. No unrelated binaries, env vars, or installs are requested.
Instruction Scope
Instructions explicitly target OpenTable domains and describe JS evaluate snippets to find/click hidden elements, update widgets, and scrape confirmation details. This is appropriate for the stated goal. Note: the snippets read page text (including potential confirmation numbers and card last-4) and perform clicks using the active logged-in session — expected for booking, but it means the skill operates with whatever is present in the user's OpenTable session and page DOM.
Install Mechanism
No install spec and no code files to write to disk (instruction-only). Lowest-risk install model; nothing is downloaded or executed outside the browser tool.
Credentials
No environment variables, API keys, or unrelated credentials are requested. The required config path (browser.enabled) is proportional to a browser-based automation skill. The skill relies on the user's existing OpenTable session and card-on-file — that dependency is declared in the README.
Persistence & Privilege
Skill is not always:true and does not request elevated/persistent platform privileges. It does not modify other skills or system-wide config. Autonomous invocation is allowed by default but is not combined with other concerning flags.
Assessment
This skill appears to do what it says: automate bookings using the OpenClaw browser tool and your logged-in OpenTable session. Before installing or invoking it, consider: (1) it will act using your browser profile/session and card-on-file — it can complete bookings without further card entry, so only use it if you trust the automation to place reservations on your behalf; (2) review and restrict which browser profile the skill can use (use a dedicated profile such as the suggested profile="openclaw"), and keep your OpenTable account secured with a strong password/MFA; (3) the JS snippets read page text (confirmation numbers, dates, and last-4 card digits) — that's necessary for confirmation but may include other visible PII on the page; (4) verify the browser tool and the agent environment are trusted (the skill contains no network exfiltration endpoints, but the browser environment could still be used to interact with any page it is navigated to); (5) if you are uncomfortable, do not provide a logged-in profile or card on file, or use a disposable/test account. If you want higher assurance, ask the skill author for an explicit domain whitelist or to restrict actions to verified OpenTable domains only.Like a lobster shell, security has layers — review code before you run it.
latestvk9726eha4qenrhyybw6py9ccfx834zye
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🍽️ Clawdis
Configbrowser.enabled
