/fun-nights
Agent 5: Night-Out Planner (the user's personal life)
Plans a night out that the next day survives: a legal-age check against person.md and the local drinking age, a named ride home from the last venue, and an enforced hard recovery block the following day, with every venue fact fetched and cited.
verified (fixture) 2026-09-07 · manual-fallback: the two venue slots are filled by a real run, not by the fixturev0.1.0
Its status above is the registry's own, with the date of the run that produced it.
What it is for
Contract A
- #5 — Fun / party time · rest day after drinking, enforced; drinking-age check; ride home
Example requests
- “plan a night out”
- “where should we go Friday”
- “birthday drinks for six”
- “somewhere with no alcohol”
- “night out”
What it needs, and what it hands back
Needs connected
- websearch
- webfetch
Better with: twilio.
Uses WebSearch, WebFetch, tools/notify.py, tools/connect.py, which exist in Claude Code. In the platform those steps come back as something for you to do, with the exact clicks.
Hands back
- clients/_me/schedule/fun-nights.md (the night AND the hard recovery block)
- clients/_me/plans/fun-nights/<date>-<slug>.md (gate table, sequence, ride home)
- clients/_me/status.md checklist + needs-me lines
Stops and asks
- a night running more than two hours past the sleep window
- the first live reminder once a notify adapter is connected
Steps it cannot do through an API, and hands you instead: inviting the group — this skill never contacts anyone but the owner; booking a table or a ride — it reserves and pays for nothing.
How it runs
These are the headings of its own written instructions — 312 lines you can read and change.
- Step 0 — Environment, profile, workspace
- Step 1 — The three gates, before any venue is looked at
- Step 2 — Find venues that actually fit
- Step 3 — Build the night as a sequence with times
- Step 4 — Book the ride home, in the plan
- Step 5 — Book the recovery day
- Step 6 — Deliver