OpenTable

Setup

On first use, read setup.md and confirm service model, reservation goals, and operating constraints before proposing changes.

When to Use

User needs to operate or improve OpenTable performance for a restaurant, group, or hospitality concept. Agent handles reservation strategy, listing quality, pacing controls, guest communication, and failure recovery. This skill is advisory by default and does not configure authenticated OpenTable automation on its own.

Architecture

Memory lives in ~/opentable/. See memory-template.md for setup and status fields.

~/opentable/
|-- memory.md                 # Current strategy, goals, and integration state
|-- reservation-log.md        # Demand patterns, pacing changes, and outcomes
|-- guest-signals.md          # No-show patterns, special requests, and friction points
`-- incidents.md              # Overbooking, outage, and recovery records

Quick Reference

Use the smallest relevant file for the task.

Data Storage

Local notes stay under ~/opentable/:

• strategy snapshot and current priorities in memory file
• reservation pacing and demand signals in reservation log
• guest behavior patterns in guest signals file
• incident timeline and mitigations in incidents file

Core Rules

1. Anchor Every Change to a Service Goal

Before touching availability or policies, identify the target outcome:

• raise seated covers
• increase average check through better mix
• reduce no-shows and dead inventory
• protect guest experience at peak times

If the goal is unclear, propose options and get confirmation first.

2. Keep Inventory Honest Across All Time Windows

Availability must reflect what operations can actually seat.

• do not open slots that kitchen or floor cannot absorb
• separate peak, shoulder, and off-peak strategy
• treat special events and holidays as explicit override windows

Prefer fewer accurate slots over inflated inventory that leads to walk-back.

3. Use Pacing and Table Mix as Primary Control Levers

Adjust flow with pacing first, not only with blanket block rules.

• map party-size mix by hour
• reserve capacity for high-value windows and turn targets
• adjust release cadence for same-day demand spikes

Never apply broad slot changes without documenting expected impact.

4. Design Guest Messaging to Prevent Friction

Confirmations, reminders, and policy copy should reduce uncertainty.

• keep cancellation windows explicit
• send reminder timing based on lead-time profile
• align special request language with what can actually be delivered

Do not use punitive language when a neutral policy explanation works.