Agent skill

Resy Hunter

by LeoYeAI in LeoYeAI/openclaw-master-skills

Monitor hard-to-get restaurant reservations on Resy, OpenTable, and Tock.

MITAuto-check passed

Install Resy Hunter

skills CLI

$ npx skills add LeoYeAI/openclaw-master-skills --skill resy-hunter -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install LeoYeAI/openclaw-master-skills resy-hunter --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/resy-hunter .claude/skills/resy-hunter && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "resy-hunter" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/resy-hunter into .claude/skills/resy-hunter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resy-hunter", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/resy-hunter

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add LeoYeAI/openclaw-master-skills --skill resy-hunter -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install LeoYeAI/openclaw-master-skills resy-hunter --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/resy-hunter .agents/skills/resy-hunter && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "resy-hunter" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/resy-hunter into .agents/skills/resy-hunter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resy-hunter", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add LeoYeAI/openclaw-master-skills --skill resy-hunter -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install LeoYeAI/openclaw-master-skills resy-hunter --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/resy-hunter .cursor/skills/resy-hunter && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "resy-hunter" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/resy-hunter into .cursor/skills/resy-hunter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resy-hunter", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/LeoYeAI/openclaw-master-skills.git --path skills/resy-hunter

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add LeoYeAI/openclaw-master-skills --skill resy-hunter -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install LeoYeAI/openclaw-master-skills resy-hunter --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/resy-hunter .gemini/skills/resy-hunter && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "resy-hunter" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/resy-hunter into .gemini/skills/resy-hunter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resy-hunter", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install LeoYeAI/openclaw-master-skills resy-hunter

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add LeoYeAI/openclaw-master-skills --skill resy-hunter -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/resy-hunter .github/skills/resy-hunter && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "resy-hunter" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/resy-hunter into .github/skills/resy-hunter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resy-hunter", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add LeoYeAI/openclaw-master-skills --skill resy-hunter -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install LeoYeAI/openclaw-master-skills resy-hunter --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/resy-hunter .opencode/skills/resy-hunter && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "resy-hunter" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/resy-hunter into .opencode/skills/resy-hunter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resy-hunter", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: resy-hunter
GitHub stars: 2.2k
Token cost: ~4.1k tokens
SKILL.md length: 1,785 words
Files: 17 (incl. scripts, references)
Skills in repo: 1,235
Repo updated: Jul 20, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Monitor hard-to-get restaurant reservations on Resy, OpenTable, and Tock.

Works in 5 steps: bash scripts/resy-search-venue.sh… → Loop through each date: bash… → Filter returned slots to only those… → …
SKILL.md covers When to Use, Platforms Supported, Parsing Natural Language… and How to Run Checks, plus 9 more sections
Runs Shell and JavaScript scripts from its folder; calls bash, node and npm; reaches resy.com and opentable.com; needs RESY_PASSWORD and RESY_API_KEY

What it does

Resy Hunter is an agent skill from LeoYeAI/openclaw-master-skills. Monitor hard-to-get restaurant reservations on Resy, OpenTable, and Tock. Check availability, manage a watchlist, and get Telegram alerts when tables open up.

Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 19 other files, including scripts and reference files (for example `_meta.json`, `examples/watchlist.example.json` and `package-lock.json`).

It works with Telegram. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.

Example prompts

“/resy-hunter”

Requirements

Node.js
A Bash shell
A credential in RESY_API_KEY

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

bash scripts/resy-search-venue.sh "Tatiana by Kwame" → get venue_id
Loop through each date: bash scripts/resy-check.sh 2
Filter returned slots to only those between 18:00-21:00
Present all dates that have matching slots, with booking links
If zero results across all 30 days, offer to add to watchlist for monitoring

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 9 files in scripts/ (Shell and JavaScript), which the agent can run.
Shell commands in SKILL.md call:
- bash
- node
- npm
- npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- resy.com
- opentable.com
- exploretock.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- RESY_PASSWORD
- RESY_API_KEY
- TELEGRAM_BOT_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Resy Hunter loads about 4.1k tokens when it runs, and up to ~5.7k if it reads all its reference files. Until then it costs about 43 tokens; SKILL.md has 1,785 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~43
When it runs · the whole SKILL.md, loaded when a task matches: ~4.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~5.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,785 words, ~4,131 tokens.

Download SKILL.mdSave it as .claude/skills/resy-hunter/SKILL.md (or your agent's skills folder). This skill also uses 16 other files; get the full folder from GitHub.

name: resy-hunter
description: Monitor hard-to-get restaurant reservations on Resy, OpenTable, and Tock. Check availability, manage a watchlist, and get Telegram alerts when tables open up.
version: 2.1.0

Resy Hunter

Monitor restaurant reservations across Resy, OpenTable, and Tock. Detect open tables and alert the user via Telegram.

When to Use

User asks to check if a restaurant has availability
User wants to find open tables at a specific restaurant on a date
User wants to monitor a restaurant for cancellations or new openings
User wants to manage their restaurant watchlist (add, remove, list)
User asks to set up background monitoring or alerts

Platforms Supported

Platform	Script	Identifier	Auth Required	Notes
Resy	`resy-check.sh`	`venue_id` (integer)	Yes — `RESY_API_KEY` + `RESY_EMAIL` + `RESY_PASSWORD`	Auto-login via API, token cached 12h
OpenTable	`opentable-check.js`	`restaurant_id` (integer)	Yes — manual login via `opentable-login.js`	One-time visible browser login, session persisted
Tock	`tock-check.js`	`slug` (URL slug)	No	Playwright bypasses Cloudflare

Parsing Natural Language Requests

Users speak casually. Extract these fields from every request:

Field	How to parse	Default
Restaurant	Name mentioned, or "my list" / "my watchlist" → sweep all watchlist entries	—
Party size	"for 2", "party of 4", "2 people", "two"	Ask if missing
Date(s)	"March 9" → `2026-03-09`. "this Saturday" → resolve to YYYY-MM-DD. "next 30 days" → generate array of dates. "this weekend" → upcoming Sat + Sun. "any Friday in April" → all Fridays in April.	Ask if missing
Time window	"6-9pm" → `earliest: "18:00", latest: "21:00"`. "7:30p" → `earliest: "19:00", latest: "20:00"` (±30min). "dinner" / "prime time" → `earliest: "18:00", latest: "21:00"`. "lunch" → `earliest: "11:30", latest: "14:00"`. "tonight" → `earliest: "18:00", latest: "22:00"`	All times
Fallback	"if nothing, check my list" → on zero results, sweep watchlist with same date/party/time constraints	None
Action	"book me" / "find me a res" / "get me a table" → find availability and present booking links (skill is read-only, never books). "monitor" / "alert me" / "watch for" → set up cron. "add to my list" → watchlist add.	Check availability

"Book" always means "find availability." This skill never books. Always present results with a direct booking link so the user can book themselves.

Example Requests → Execution Plans

"Book me a res at Tatiana by Kwame sometime in the next 30 days between 6-9pm for 2 people"

Parsed:

Restaurant: Tatiana by Kwame → run resy-search-venue.sh "Tatiana by Kwame" to get venue_id
Dates: next 30 days → generate ["2026-03-06", "2026-03-07", ..., "2026-04-04"]
Time: 6-9pm → earliest: "18:00", latest: "21:00"
Party size: 2

Execute:

bash scripts/resy-search-venue.sh "Tatiana by Kwame" → get venue_id
Loop through each date: bash scripts/resy-check.sh <venue_id> <date> 2
Filter returned slots to only those between 18:00-21:00
Present all dates that have matching slots, with booking links
If zero results across all 30 days, offer to add to watchlist for monitoring

"Find me a res from my list of restaurants for 3 people this Sat between 6-7:30p, alert me with which ones are available and I will pick one"

Parsed:

Restaurant: "from my list" → sweep entire watchlist
Date: "this Sat" → resolve to upcoming Saturday YYYY-MM-DD
Time: 6-7:30p → earliest: "18:00", latest: "19:30"
Party size: 3 (override each entry's party_size for this check)

Execute:

bash scripts/watchlist.sh list → get all entries
For each entry, run the platform check script with the resolved Saturday date and party_size=3
Filter slots to 18:00-19:30 window
Present results grouped by restaurant, with booking links
Let the user pick — do not choose for them

"Book me at Carbone for 2 on March 9 5-9pm, if no availability find something else from my list"

Parsed:

Restaurant: Carbone → search venue_id
Date: March 9 → 2026-03-09
Time: 5-9pm → earliest: "17:00", latest: "21:00"
Party size: 2
Fallback: sweep watchlist

Execute:

bash scripts/resy-search-venue.sh "Carbone" → get venue_id
bash scripts/resy-check.sh <venue_id> 2026-03-09 2
Filter slots to 17:00-21:00
If slots found → present with booking link, done
If no slots → bash scripts/watchlist.sh list, then check each entry for 2026-03-09 party_size=2 with 17:00-21:00 filter
Present any alternatives found from the watchlist

"Any openings at Don Angie tonight for 4?"

Parsed:

Restaurant: Don Angie → search venue_id
Date: tonight → today's date
Time: (tonight implies dinner) → earliest: "18:00", latest: "22:00"
Party size: 4

Execute:

bash scripts/resy-search-venue.sh "Don Angie" → get venue_id
bash scripts/resy-check.sh <venue_id> <today> 4
Filter to 18:00-22:00, present results

"Set up alerts for Atomix, party of 2, any Friday or Saturday in April between 7-9"

Parsed:

Restaurant: Atomix → search venue_id
Dates: every Fri + Sat in April 2026 → ["2026-04-03", "2026-04-04", "2026-04-10", "2026-04-11", ...]
Time: 7-9 → earliest: "19:00", latest: "21:00"
Party size: 2
Action: set up monitoring

Execute:

bash scripts/resy-search-venue.sh "Atomix" → get venue_id
bash scripts/watchlist.sh add '{"name":"Atomix","platform":"resy","venue_id":<id>,"party_size":2,"dates":["2026-04-03","2026-04-04",...],"preferred_times":{"earliest":"19:00","latest":"21:00"}}'
Set up cron if not already running:

bash

openclaw cron add --name "resy-hunter-sweep" --every "15m" --session isolated --message "Run resy-hunter monitor..." --announce

Confirm to user: "Monitoring Atomix for Friday/Saturday openings in April, 7-9 PM, party of 2. I'll alert you on Telegram when something opens."

"What's available this weekend from my list?"

Parsed:

Restaurant: "from my list" → sweep watchlist
Date: "this weekend" → upcoming Saturday + Sunday
Time: not specified → all times
Party size: not specified → use each entry's configured party_size

Execute:

bash scripts/watchlist.sh list → get all entries
For each entry, check both Saturday and Sunday dates using the entry's own party_size
Present all results grouped by restaurant and date

"Check everything on my list for tomorrow night"

Parsed:

Restaurant: "everything on my list" → sweep watchlist
Date: tomorrow → resolve to YYYY-MM-DD
Time: "night" → earliest: "18:00", latest: "22:00"
Party size: use each entry's configured party_size

Execute: same as watchlist sweep pattern above

"Monitor Torrisi for cancellations, party of 4, March 15, prime time"

Parsed:

Restaurant: Torrisi → search venue_id
Date: March 15 → 2026-03-15
Time: "prime time" → earliest: "18:00", latest: "21:00"
Party size: 4
Action: "monitor for cancellations" → add to watchlist + set up cron

Execute:

Search venue_id, add to watchlist, set up cron
Confirm monitoring is active

"Add Lilia to my watchlist, 2 people, next three Saturdays, dinner time"

Parsed:

Restaurant: Lilia → search venue_id
Dates: next 3 Saturdays → resolve to specific YYYY-MM-DD values
Time: "dinner time" → earliest: "18:00", latest: "21:00"
Party size: 2
Action: watchlist add only (no cron unless asked)

Execute:

bash scripts/resy-search-venue.sh "Lilia" → get venue_id
bash scripts/watchlist.sh add '{"name":"Lilia","platform":"resy","venue_id":<id>,"party_size":2,"dates":["<sat1>","<sat2>","<sat3>"],"preferred_times":{"earliest":"18:00","latest":"21:00"}}'

"Is there anything at 4 Charles or Via Carota for 2 this Thursday?"

Parsed:

Restaurants: two separate — "4 Charles" and "Via Carota"
Date: this Thursday → resolve
Party size: 2

Execute:

Search venue_ids for both restaurants
Check both for the resolved Thursday date with party_size=2
Present results side by side

"Cancel monitoring for Carbone"

Parsed:

Action: remove from watchlist

Execute:

bash scripts/watchlist.sh list → find Carbone's id
bash scripts/watchlist.sh remove <id>
If watchlist is now empty, suggest removing the cron job too

Show full SKILL.md (736 more words)Show less

How to Run Checks

Determine the platform (ask the user if unclear)
Get the restaurant identifier:
- Resy: If the user doesn't know the venue_id, run scripts/resy-search-venue.sh "<name>" [lat] [long] to find it
- OpenTable: The restaurant_id is in the OpenTable URL (e.g., opentable.com/r/restaurant-name-city?rid=123456 → rid is 123456)
- Tock: The slug is in the URL (e.g., exploretock.com/alinea → slug is alinea)
Run the appropriate check script:
- Resy: bash ~/.openclaw/skills/resy-hunter/scripts/resy-check.sh <venue_id> <date> <party_size>
- OpenTable: node ~/.openclaw/skills/resy-hunter/scripts/opentable-check.js <restaurant_id> <date> <party_size>
- Tock: node ~/.openclaw/skills/resy-hunter/scripts/tock-check.js <slug> <date> <party_size>
Parse the JSON output and present available slots in a clean table format:
```
Restaurant | Date | Time | Type | Platform
```
If no slots found, offer to add to the watchlist for background monitoring

Watchlist Management

The watchlist lives at ~/.openclaw/data/resy-hunter/watchlist.json (separate from the skill directory so reinstalls don't wipe user data).

List: bash ~/.openclaw/skills/resy-hunter/scripts/watchlist.sh list
Add: bash ~/.openclaw/skills/resy-hunter/scripts/watchlist.sh add '<json>'
- JSON must include: name, platform (resy/opentable/tock), platform identifier (venue_id/restaurant_id/slug), party_size, dates array
- Optional: preferred_times object with earliest and latest in HH:MM format
Remove: bash ~/.openclaw/skills/resy-hunter/scripts/watchlist.sh remove <id>
Set Priority: bash ~/.openclaw/skills/resy-hunter/scripts/watchlist.sh set-priority <id> <high|low>

Priority Levels

high — Telegram alerts fire immediately when new slots appear
low — Slots are tracked (dedup works) but Telegram alerts only when the user explicitly asks for a sweep

Default priority is low when adding entries. Set it to high for restaurants the user actively wants alerts on. The JSON report from monitor.sh always includes all priorities.

Default Time Window

All entries default to a 6:00 PM – 10:00 PM time window. Slots outside this window are filtered out. Override per restaurant via preferred_times when adding:

Example add:

bash

bash ~/.openclaw/skills/resy-hunter/scripts/watchlist.sh add '{
  "name": "Carbone",
  "platform": "resy",
  "venue_id": 5286,
  "party_size": 2,
  "dates": ["2026-03-15", "2026-03-22"],
  "preferred_times": {"earliest": "18:00", "latest": "21:30"},
  "priority": "high"
}'

Background Monitoring

The monitor runs checks in parallel and staggers platforms by frequency:

Resy (curl): checked every sweep, up to 8 concurrent
Tock (Playwright): checked once per hour, up to 2 concurrent
OpenTable (Playwright): checked once per hour, up to 2 concurrent

To set up cron monitoring, run:

bash

openclaw cron add \
  --name "resy-hunter-sweep" \
  --every "15m" \
  --session isolated \
  --message "Run resy-hunter monitor. Execute bash ~/.openclaw/skills/resy-hunter/scripts/monitor.sh. If new availability is found in the output JSON (new_availability array is non-empty), format a clear alert listing each restaurant name, platform, date, available time slots, and party size. Include a direct booking link. If nothing new, respond only: No new availability." \
  --announce

The 15-minute cron means Resy is checked every 15 minutes while Tock and OpenTable are automatically checked once per hour (the monitor tracks timestamps and skips platforms checked less than 60 minutes ago).

For high-frequency sniping on a specific date (e.g., when reservations drop):

bash

openclaw cron add \
  --name "resy-hunter-snipe" \
  --every "2m" \
  --session isolated \
  --message "Snipe mode: run bash ~/.openclaw/skills/resy-hunter/scripts/resy-check.sh <venue_id> <date> <party_size>. Report immediately if any slot appears." \
  --announce

To stop monitoring: openclaw cron remove --name "resy-hunter-sweep"

Manual Monitor Sweep

To run a one-time sweep of the entire watchlist:

bash

bash ~/.openclaw/skills/resy-hunter/scripts/monitor.sh

To check only a specific platform (bypasses the hourly interval timer):

bash

bash ~/.openclaw/skills/resy-hunter/scripts/monitor.sh --platform resy
bash ~/.openclaw/skills/resy-hunter/scripts/monitor.sh --platform tock
bash ~/.openclaw/skills/resy-hunter/scripts/monitor.sh --platform opentable

Multiple platforms can be combined:

bash

bash ~/.openclaw/skills/resy-hunter/scripts/monitor.sh --platform resy --platform tock

Interpret the output JSON:

new_availability array: newly detected slots since last sweep
total_checked: number of restaurant+date combinations checked
total_with_availability: how many had open slots

Sending Notifications Manually

bash

bash ~/.openclaw/skills/resy-hunter/scripts/notify.sh "Your message here"

This sends a Telegram message. The bot token is pulled from OpenClaw's Telegram channel config (channels.telegram.botToken). Falls back to TELEGRAM_BOT_TOKEN env var if config not found.

Booking Links

When reporting availability, always include a direct booking link:

Resy: https://resy.com/cities/<city>-<region>/venues/<slug>?date=<YYYY-MM-DD>&seats=<party_size>
OpenTable: https://www.opentable.com/booking/widget?rid=<restaurant_id>&datetime=<ISO>&covers=<party_size>
Tock: https://www.exploretock.com/<slug>/search?date=<YYYY-MM-DD>&size=<party_size>

Error Handling

If a Resy request returns HTTP 419, the script automatically clears the cached token and re-authenticates. No manual action needed.
If Resy login fails (HTTP 401/403), check RESY_EMAIL and RESY_PASSWORD.
If OpenTable returns session_expired: true, run node ~/.openclaw/skills/resy-hunter/scripts/opentable-login.js to re-authenticate manually. The monitor will send a Telegram alert when this happens.
If Tock returns blocked: true in output, Cloudflare blocked even the Playwright browser. Return the URL for the user to check manually. This is rare — retrying usually works.

Credential Setup

Resy (auto-login via API):

RESY_API_KEY — one-time extraction from browser DevTools (static, never expires):
- Log into resy.com → DevTools → Network tab
- Find any request to api.resy.com
- Authorization header → value after ResyAPI api_key= is the API key
RESY_EMAIL — your Resy account email
RESY_PASSWORD — your Resy account password
Auth tokens are fetched and cached automatically (12-hour TTL). No manual token extraction needed.

OpenTable (manual login via Playwright):

Run once: node ~/.openclaw/skills/resy-hunter/scripts/opentable-login.js
A visible browser opens to OpenTable's login page
Log in with your email + OTP code manually
The script detects login and saves session cookies to ~/.openclaw/data/resy-hunter/opentable-session.json
Future runs use the saved session headlessly. If it expires, the monitor sends a Telegram alert telling you to re-run opentable-login.js.

Tock (no credentials): No credentials needed. Playwright uses a real browser that passes Cloudflare Turnstile challenges automatically.

First-Time Setup

After installing the skill, run once to install dependencies:

bash

cd ~/.openclaw/skills/resy-hunter
npm install
npx playwright install chromium

Important

This skill is read-only. Never attempt to book a reservation. The user books manually.
Respect rate limits. Do not run checks more frequently than every 2 minutes.
Dates in the past should be skipped automatically by the monitor script.

Files

SKILL.md and 16 other files (scripts, references) in skills/resy-hunter of LeoYeAI/openclaw-master-skills.

SKILL.md
_meta.json
examples/watchlist.example.json
package-lock.json
package.json
references/platforms.md
references/resy-api.md
scripts/monitor.sh
scripts/notify.sh
scripts/opentable-check.js
scripts/opentable-login.js
scripts/resy-auth.sh
scripts/resy-check.sh
scripts/resy-search-venue.sh
scripts/tock-check.js
scripts/watchlist.sh
watchlist.json

Open the folder on GitHubat commit e5199b5

Compare with similar skills

Resy Hunter next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Resy Hunter compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Resy Hunter this skillLeoYeAI/openclaw-master-skills	2.2k	—	~4.1k	Automated safety check: Pass	MIT	2 mo ago
Perform Tasktelegramdesktop/tdesktop	33k	2 repos	~3k	Automated safety check: Pass	GPL-3.0	today
Custom Mode Creator for claude-memthedotmack/claude-mem	99k	—	~2.4k	Automated safety check: Pass	Apache-2.0	today
Dependency Watchtelegramdesktop/tdesktop	33k	—	~2.2k	Automated safety check: Pass	GPL-3.0	today
Continuetelegramdesktop/tdesktop	33k	2 repos	~9.4k	Automated safety check: Pass	GPL-3.0	today
Process InboxTDesktop-x64/tdesktop	3k	1 repos	~4.3k	Automated safety check: Pass	GPL-3.0	18 days ago

Similar skills

Perform Task
telegramdesktop/tdesktop
Resolve, start or resume, implement, review, test, and publish exactly one existing ai-tdesktop task by short slug or full dated id, including rare blocked retries and split-required results.
33k GitHub starsUsed in 2 repos~3k tokens
Productivity & AutomationAuto-check passed
Custom Mode Creator for claude-mem
thedotmack/claude-mem
Walks you through creating, installing and verifying a custom claude-mem mode, including note types, tags and optional Telegram alerts for chosen memories.
99k GitHub stars~2.4k tokensUpdated today
Agent WorkflowsAuto-check passed
Dependency Watch
telegramdesktop/tdesktop
Audit Telegram Desktop dependencies on freshly fetched origin/dev for releases and security fixes, including upstream lag and backport candidates in patched forks.
33k GitHub stars~2.2k tokensUpdated today
Productivity & AutomationAuto-check passed
Continue
telegramdesktop/tdesktop
Continue autonomous Telegram Desktop development from the shared ai-tdesktop repository.
33k GitHub starsUsed in 2 repos~9.4k tokens
Productivity & AutomationAuto-check passed
Process Inbox
TDesktop-x64/tdesktop
Process the local ignored ai-tdesktop inbox into durable, independently testable Telegram Desktop task records while task execution worktrees remain active.
3k GitHub starsUsed in 1 repo~4.3k tokens
Productivity & AutomationAuto-check passed
Process Inbox
telegramdesktop/tdesktop
Process the local ignored ai-tdesktop inbox into durable, independently testable Telegram Desktop task records while task execution worktrees remain active.
33k GitHub stars~5.4k tokensUpdated today
Productivity & AutomationAuto-check passed

Questions about Resy Hunter

What does Resy Hunter do?

Monitor hard-to-get restaurant reservations on Resy, OpenTable, and Tock. Resy Hunter is an agent skill from LeoYeAI/openclaw-master-skills. Monitor hard-to-get restaurant reservations on Resy, OpenTable, and Tock.

How do I install Resy Hunter in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill resy-hunter -a claude-code`. Or copy the skill folder (skills/resy-hunter in LeoYeAI/openclaw-master-skills) into .claude/skills/resy-hunter in your project. Claude Code loads it when a task matches its description.

How do I install Resy Hunter in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill resy-hunter -a codex`. Or copy the skill folder (skills/resy-hunter in LeoYeAI/openclaw-master-skills) into .agents/skills/resy-hunter in your project. Codex loads it when a task matches its description.

Can I use Resy Hunter in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill resy-hunter -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/resy-hunter, .gemini/skills/resy-hunter, .github/skills/resy-hunter and .opencode/skills/resy-hunter in your project.

What does Resy Hunter need to run?

Going by SKILL.md and its folder, Resy Hunter needs a shell and JavaScript for the scripts in its folder, the command-line tools its instructions call (bash, node, npm and npx) and credentials named RESY_PASSWORD, RESY_API_KEY and TELEGRAM_BOT_TOKEN. Our summary lists: Node.js; A Bash shell; A credential in RESY_API_KEY.

Does Resy Hunter access the network?

SKILL.md names 3 domains. In commands or code: resy.com, opentable.com and exploretock.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Resy Hunter safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Resy Hunter use?

Resy Hunter is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Resy Hunter use?

About 4.1k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.

What are the alternatives to Resy Hunter?

Skills that share tags, products or a category with Resy Hunter: Perform Task (telegramdesktop/tdesktop, 33k stars), Custom Mode Creator for claude-mem (thedotmack/claude-mem, 99k stars), Dependency Watch (telegramdesktop/tdesktop, 33k stars) and Continue (telegramdesktop/tdesktop, 33k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Resy Hunter?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,160 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.

Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Resy Hunter

Facts

At a glance

What it does

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Resy Hunter

When to Use

Platforms Supported

Parsing Natural Language Requests

Example Requests → Execution Plans

How to Run Checks

Watchlist Management

Priority Levels

Default Time Window

Background Monitoring

Manual Monitor Sweep

Sending Notifications Manually

Booking Links

Error Handling

Credential Setup

First-Time Setup

Important

Files

Compare with similar skills

Similar skills

More from LeoYeAI/openclaw-master-skills

Related

Questions about Resy Hunter