Research Resy and OpenTable listings to create a dated restaurant shortlist and compare time-specific availability without booking.
Install & Download
1. ClawHub CLI
The fastest way to install a skill directly from the registry.
npx clawhub@latest install dining-demand-research
2. Manual Installation
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
3. Prompt Installation
Copy this prompt to OpenClaw to install it automatically.
Help me install dining-demand-research using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Prefer to download?
Get the raw skill files in a ZIP archive.
What is Dining Demand Research?
Dining Demand Research helps an AI agent discover restaurants and compare publicly displayed profiles, menus, reviews, and reservation availability on Resy and OpenTable. It produces a dated, source-aware snapshot so you can evaluate venues for a specific local date, time, and party size.
As an Openclaw Skills research workflow, it is read-only: it does not create, hold, change, or cancel reservations, buy event tickets, or guarantee that an observed slot remains available. It distinguishes ordinary reservation slots from Resy ticketed dining events and clearly separates discovery information from time-specific availability.
Dining Demand Research Use Cases
- Build a restaurant shortlist using location, cuisine, price, or accessibility preferences.
- Compare Resy and OpenTable availability for a specified local date, time, and party size.
- Check a restaurant's profile, menu, or reviews to support a dining decision.
- Review Resy ticketed dining events separately from ordinary reservation availability.
- Create a dated snapshot that records sources and when availability was retrieved.
- Identify venues with no matching displayed slots without treating that as proof of sellout, closure, or demand.
How Dining Demand Research Works
- Clarify the requested place, party size, local dining date and time, and any cuisine, price, or accessibility preferences.
- Resolve the venue carefully, preferring the provider-specific ID; otherwise verify its name and address or neighborhood. Keep Resy and OpenTable IDs separate.
- Discover candidates with the provider's search endpoints. For Resy, location, cuisine, and event endpoints can refine discovery; OpenTable search requires a term and coordinates.
- Fetch provider-specific restaurant details and, when useful, Resy availability or OpenTable menus and reviews. Treat menus and reviews as discovery data, not proof of availability.
- Normalize the requested time to the restaurant's verified local time zone. Record the requested local date, time, zone, party size, provider, source, and
retrieved_atfor each availability call. - For a Resy event, inspect its ticket packages through the event endpoint and report its ticket availability and pricing separately from restaurant reservation slots.
- Deliver a comparison with verified venue identity, discovery details, observed slots or an explicit lack of slots, source URLs, and snapshot timestamps. Compare only matching party sizes and local times.
Dining Demand Research Setup
This skill describes provider API workflows; the supplied instructions do not specify an installation command, package, credentials, or environment-variable setup. Use it within an agent environment that can make the documented GET requests, and follow that environment's provider access requirements.
- Collect the requested location, party size, local date and time, and relevant preferences.
- Resolve the restaurant's local time zone before querying availability. Resy uses
YYYY-MM-DDdates; OpenTable uses RFC3339-minute localdate_timevalues. - Call only the relevant provider endpoints and preserve each provider's IDs and source URLs separately.
- Record
retrieved_atimmediately for every availability request. Treat responses as observations, not inventory holds.
# Example endpoint paths from the skill; supply provider-specific parameters.
GET /resy/locations?q=<city>&country=<country>
GET /resy/search?latitude=<lat>&longitude=<lon>&term=<query>&date=<YYYY-MM-DD>&party_size=<size>
GET /opentable/search?term=<query>&latitude=<lat>&longitude=<lon>&date_time=<local-RFC3339-minute>&party_size=<size>
Dining Demand Research Data Schema & Taxonomy
The skill specifies a comparison deliverable rather than a generated file format. Include these fields for each venue:
| Field | Meaning |
|---|---|
| Venue name | Restaurant or event venue name |
| Provider and provider ID | Resy or OpenTable and its provider-specific identifier; never mix IDs across providers |
| Verified address/neighborhood | Confirmed venue location used to resolve identity |
| Cuisine and price signal | Discovery attributes; a price tier is not a menu total |
| Requested local date/time and time zone | Original requested moment, represented in the venue's verified local zone |
| Party size | Actual requested group size; compare only like-for-like sizes |
| Observed slots | Returned availability, or an explicit statement that no matching slots were observed |
| Source URL | Canonical URL when returned, kept associated with its provider |
retrieved_at |
Timestamp captured immediately for each availability call |
| Data type | Identify profile/discovery facts separately from time-specific availability snapshots |
For Resy event results, report event availability, ticket tier price, inclusions, and event-day instructions as event data, separate from regular reservation slots. Preserve currency and menu-price scope when actual prices are returned; do not infer taxes, fees, deposits, minimums, or total reservation cost.
Dining Demand Research Advanced Features
- Uses provider-specific discovery and detail endpoints for Resy and OpenTable, including Resy locations, cuisines, events, search, restaurant, and availability, plus OpenTable search, restaurant, menus, and reviews.
- Supports time-specific availability queries and records each result as a timestamped snapshot rather than a reservation hold.
- Resolves ambiguous venues by provider ID first, then by verified name and street address or neighborhood.
- Handles provider-specific time formats and requires normalization to the restaurant's local time zone.
- Separates Resy ticketed, fixed-price dining events and their ticket-package availability from ordinary restaurant reservations.
- Applies cautious interpretation: party size matters, missing slots do not prove sellout or closure, price tiers are not menu totals, and discovery data does not establish availability.
- The supplied skill does not specify hooks, multi-agent orchestration, or automated booking; its workflow is limited to read-only research.
SKILL.md
Loading
Related Openclaw Skills
Mundane
Mundane connects AI agents with ID-verified local workers for real-world tasks, holding payment in escrow until the user reviews the proof.
AI Opportunity Navigator
Find and screen current paid coding and AI evaluation opportunities against your location, skills, and available time—with original sources and clear eligibility gaps.
Xianmubox Development Workflow
A gated, end-to-end workflow for developing, testing, debugging, and deploying Xianmubox firmware changes safely.
XianMu Comics
Bring 568 classic Chinese picture-story books into chat for discovery, page-by-page reading and narration, and AI conversations with their characters.
Long-Task Dependency and Acceptance Planner
Turn multi-stage work into a budget-aware dependency graph with verifiable results, safe recovery checkpoints, and clear next steps.
PhotoFresco
PhotoFresco lets an AI agent edit images in a user-visible, permission-controlled editor and export the results as PNG, PSD, or native PFD files.
Featured*
