Date Night

Date Night Skill (Published)

End-to-end date night planning: restaurants, movies, events, logistics, and notifications. Powered by playwright-cli browser automation.

User Preferences

This skill uses ~/.openclaw/skills/date-night/config.json. Run onboarding on first use (see below). After that, load config silently at the start of every session.

cat ~/.openclaw/skills/date-night/config.json 2>/dev/null

Config schema:

{
  "name": "string",
  "first_name": "string",
  "last_name": "string",
  "user_email": "string",
  "user_phone": "string (digits only, e.g. 8015550155)",
  "partner": "string | null",
  "notify_channel": "iMessage | Telegram | Discord | Signal | SMS",
  "dietary": ["no alcohol", "vegetarian", "..."],
  "has_children": false,
  "children_count": 0,
  "children_ages": "string | null",
  "location": "City, ST",
  "zip": "00000",
  "preferred_theater": "string | null",
  "babysitter_rate": 18,
  "calendar_tool": "gog | gcal | ical",
  "onboarded_at": "ISO timestamp"
}

PII note: user_email, user_phone, first_name, and last_name are used to auto-fill reservation and ticket forms. They are stored locally in config.json and never transmitted except to the booking site during form submission.

First Run Onboarding

Check at every skill invocation:

CONFIG=~/.openclaw/skills/date-night/config.json
if [ ! -f "$CONFIG" ]; then
  echo "ONBOARDING_NEEDED"
fi

If ONBOARDING_NEEDED: run the onboarding flow before doing anything else.

Onboarding Flow

Ask questions one at a time, conversationally. This is a date night skill — make it feel warm and fun, not like filling out a DMV form.

Opening:

"Hey! Looks like it's your first time using the Date Night skill — exciting. Let me grab a few quick things so I can make it feel personal. Won't take long."

Question sequence (ask naturally, wait for each answer):

1. Name:

   "First — what's your name?" — Collect first name and last name (needed for reservation forms).

2. Email & Phone:

   "What email and phone number should I use for reservations? These go directly into booking forms — I store them locally and nowhere else."

3. Partner:

   "Planning these with a partner, or flying solo? (Solo date nights are completely valid.)" — If partner: "What's their name?"

4. Partner notification:

   "What's the best way to reach {partner}? Like, if I wanted to send them a heads-up about a reservation — iMessage, Telegram, Signal, Discord, something else?" — Skip if solo.

5. Dietary / lifestyle:

   "Any food preferences or restrictions I should know about? Things like no alcohol, vegetarian, gluten-free, shellfish allergy — or just 'none, we eat everything'?"

6. Kids:

   "Do you have kids at home? (I ask because I'll remind you about childcare after every booking.)" — If yes: "How many, and roughly what ages?"

7. Location:

   "What city or zip code are you in? I'll use this for finding nearby restaurants, theaters, and venues."

8. Theater preference (optional):

   "Any favorite movie theater chain, or a go-to theater near you? I can default to that when searching showtimes. (Skip if you don't have one.)"

9. Babysitter rate (optional, only if has_children):

   "What's your babysitter rate — roughly? I use it for budget estimates. Default is $18/hr if you're not sure."

10. Calendar tool:

    "Last one — how do you manage your calendar? I can add events automatically. Options: gog (Google), gcal, ical, or tell me what you use."

Closing:

"Perfect — you're all set! 🎉 Just say 'plan a date night,' 'find us a restaurant,' or 'get us tickets' anytime. I've got the rest."

Save Config

After collecting all answers, write the file:

mkdir -p ~/.openclaw/skills/date-night
cat > ~/.openclaw/skills/date-night/config.json << 'EOF'
{
  "name": "{name}",
  "first_name": "{first_name}",
  "last_name": "{last_name}",
  "user_email": "{email}",
  "user_phone": "{phone_digits}",
  "partner": "{partner_or_null}",
  "notify_channel": "{channel}",
  "dietary": ["{pref1}", "{pref2}"],
  "has_children": {true|false},
  "children_count": {N},
  "children_ages": "{ages_or_null}",
  "location": "{City, ST}",
  "zip": "{zip}",
  "preferred_theater": "{theater_or_null}",
  "babysitter_rate": {rate},
  "calendar_tool": "{tool}",
  "onboarded_at": "{ISO_TIMESTAMP}"
}
EOF

Applying Config Throughout the Skill

After loading config, substitute into all references:

Dietary preference enforcement: If dietary includes "no alcohol": never highlight wine lists, cocktail programs, bar scenes, or alcohol features when recommending restaurants or events. Focus on food, ambiance, service.

Reconfigure

If user says "update my date night preferences", "reconfigure date night", or "change my date night settings":

# Back up existing config
cp ~/.openclaw/skills/date-night/config.json \
   ~/.openclaw/skills/date-night/config.backup.json 2>/dev/null || true

Then re-run the onboarding flow with current values shown as defaults:

"Sure — let's update your preferences. I'll show what you have now and you can change anything. Hit Enter to keep the current value."

After re-running, overwrite config.json. Confirm:

"Updated! Changes are live for the next date night."

Requirements

External Binaries (must be installed separately)

PATH setup: export PATH="$HOME/.npm-global/bin:$PATH"

Environment Variables

OpenClaw Built-in Capabilities Used

These are standard OpenClaw agent tools — not external dependencies. They require no separate installation; they are available to any OpenClaw agent with the appropriate tool policies enabled.

No additional credentials or API tokens are needed for these built-in tools — they use whatever channels and connectors the user has already configured in their OpenClaw instance.