Free OpenClaw Skill for Food Trucks: Dispatch and Catering Agent (Download)

What this skill does for your food trucks

• Triages catering inquiries from Roaming Hunger, Truckster, and your inbox, drafts the BEO with menu, guest count, service window, and per-person pricing.
• Builds the weekly location calendar across breweries, office parks, and event slots, with traffic and weather adjustments suggested two days out.
• Tracks every mobile food unit permit (county health, fire suppression, propane) with expiration alerts 30 days out.
• Calculates propane runtime against the day's menu and prep load, flags refill stops before the truck rolls.
• Routes the per-event sales recap from Square or Toast Go into a weekly digest so the operator sees which lot, which day, which menu item is actually paying the truck.

What's inside this OpenClaw skill

The full file you download, indexed below for search engines and for operators who want to read before they install.

---
name: food-truck-dispatch-and-catering
description: Daily location dispatch, catering BEO drafting, mobile food unit permit tracking, and propane runtime alerts for food trucks. Integrates with Square, Toast Go, Roaming Hunger, Truckster.
version: 1.0.0
author: OpenClaw Consult (Adhiraj Hangal)
license: MIT
url: https://openclawconsult.com/skills/food-trucks
---

# OpenClaw Skill: Food Truck Dispatch and Catering Agent

## Overview

This skill turns the OpenClaw agent into the dispatch, catering-inbox, and
permit-tracking layer for a food truck operation. It owns the daily location
calendar, catering inquiry triage with BEO drafting, mobile food unit permit
tracking, and the per-event sales recap from the POS.

It is designed for single-truck and small-fleet operations (1 to 4 trucks),
with 30 to 80 catering events per month and 4 to 6 lot-service days per week,
on Square for Restaurants or Toast Go.

## What this skill does

1. Triages catering inquiries from Roaming Hunger, Truckster, and direct inbox
2. Drafts the BEO in your standard template with menu, count, pricing, COI ask
3. Builds the weekly location calendar across breweries, office parks, events
4. Tracks every mobile food unit permit with 30-day expiration alerts
5. Calculates propane runtime against the day's menu and prep load
6. Rolls per-event POS sales into a weekly digest

## Triggers

```yaml
triggers:
  - type: heartbeat
    schedule: "0 7 * * *"           # Daily 7am
    action: prep_today_dispatch_and_propane_check

  - type: heartbeat
    schedule: "0 8 * * *"           # Daily 8am
    action: triage_catering_inbox

  - type: heartbeat
    schedule: "0 9 * * 0"           # Sundays 9am
    action: compile_weekly_sales_digest

  - type: heartbeat
    schedule: "0 10 1 * *"          # 1st of month 10am
    action: check_permit_expirations

  - type: on_event
    event: roaming_hunger.new_inquiry
    action: triage_and_draft_beo

  - type: on_event
    event: truckster.new_inquiry
    action: triage_and_draft_beo
```

## Workflow: catering inquiry triage and BEO

When a catering inquiry arrives from Roaming Hunger, Truckster, or the
direct inbox, the agent:

1. Classifies into one of: corporate lunch, wedding, rehearsal dinner,
   birthday or private party, brewery or venue pop-up, festival booking,
   street fair
2. Pulls guest count, date, location, service window from the inquiry
3. Picks the matching menu tier from your published catering menus
4. Calculates per-person pricing using the rate card
5. Calculates travel fee using the zone or per-mile rule
6. Adds the standard COI (Certificate of Insurance) request line
7. Adds the propane and water access questions if the venue is unknown
8. Drafts the BEO and routes to the operator for sign-off

For events over 100 guests, multi-day festival bookings, and any request
needing a private-event waiver, the skill routes to a human. The autonomous
template allowlist defaults to the 25-100 guest standard-menu BEOs.

## Workflow: weekly location calendar

The skill maintains a recurring location calendar with these slot types:

- Brewery slots: typically 4-7pm or 5-9pm weekday and weekend
- Office park slots: 11:30am-1:30pm weekday lunch
- Event slots: festivals, farmers markets, school events
- Private catering: blocks the truck out of the lot calendar

Two days out, the agent suggests adjustments based on:

- Weather forecast (rain at an outdoor brewery slot is a red flag)
- Traffic (event day in the area, parade route closures)
- Sales history at this lot on this day-of-week

Operator approves the adjusted calendar; the skill posts to the truck's
public schedule on Instagram, the website, and the Truckster profile.

## Workflow: mobile food unit permit tracking

The skill tracks every permit the truck holds:

- County health permit (or state health, depending on jurisdiction)
- Fire suppression certification (Class K, ANSUL or equivalent, hood
  certification)
- Propane tank inspection certification
- Commissary letter (the licensed kitchen the truck operates from)
- Special event permits (per-event, per-jurisdiction)
- Business license (city, county)
- Sales tax permit

Each permit has an expiration date stored in memory. The skill fires alerts
at 30 days, 14 days, and 3 days before expiration. The truck does not roll
on a lapsed permit. The skill blocks dispatch if any required permit has
expired.

## Workflow: propane runtime calculation

The skill maintains an equipment-and-burn-rate model:

- Flat-top: typical hourly burn rate
- Fryer: typical hourly burn rate
- Charbroiler: typical hourly burn rate
- Oven: typical hourly burn rate
- Hot-hold: typical hourly burn rate

For each day's dispatch, the agent:

1. Pulls the day's menu and the equipment the menu requires
2. Estimates burn rate per hour of service
3. Reads the current tank count and fill percentage from the operator's
   morning check
4. Calculates projected runtime
5. Flags a refill stop if projected runtime drops below 1.5x the planned
   service window

The operator enters the morning tank check; the skill does not auto-read
tanks. The model improves as the operator logs actual consumption over time.

## Workflow: weekly sales digest

Every Sunday morning the agent compiles the digest:

- Per-lot sales: which lot, which day, which truck-style
- Per-menu-item sales: which items moved, which sat
- Per-event recap for the week's catering events
- Comp vs last week and same-week-last-year
- Top 3 wins and top 3 misses for the operator's review

The digest is the operator's Sunday-morning standup signal. Most operators
adjust the next week's calendar and menu prep off this.

## Memory keys

```yaml
memory:
  - key: truck.permit_state[{permit_id}]
    description: Permit tracking
    schema: { permit_type: string, jurisdiction: string, expires_date: date, last_renewed: date, status: enum }

  - key: truck.location_calendar[{date}]
    description: Daily location assignment
    schema: { location: string, service_window: string, slot_type: enum, weather_flag: bool, sales_history_avg: number }

  - key: truck.catering_beo[{beo_id}]
    description: Catering BEO state
    schema: { client_name: string, event_date: date, guest_count: int, menu_tier: string, total_price: number, status: enum }

  - key: truck.propane_state[{date}]
    description: Daily propane runtime check
    schema: { tank_count: int, total_fill_pct: number, projected_runtime_hours: number, refill_needed: bool }

  - key: truck.sales_log[{date}]
    description: Per-event POS sales recap
    schema: { date: date, location: string, gross_sales: number, top_items: list, customer_count: int }
```

## Message templates

```yaml
templates:
  catering_beo_corporate_lunch:
    channel: email
    subject: "BEO for your {company_name} lunch on {event_date}"
    body: |
      Hi {contact_first_name},

      Thanks for reaching out. Here is the BEO for the lunch service we
      discussed.

      Event date: {event_date}
      Service window: {service_window}
      Load-in: {load_in_time}
      Location: {event_location}
      Guest count: {guest_count}

      Menu (Tier {menu_tier_number}):
      {menu_items_list}

      Service style: {service_style}

      Per-person rate: {per_person_rate}
      Subtotal: {subtotal}
      Travel fee: {travel_fee}
      Tax: {tax}
      Total: {total}

      Two things we will need from your team:
      1. Certificate of Insurance listing {truck_legal_name} as additional
         insured (if your venue requires it; we can issue if your venue
         needs ours)
      2. Propane access confirmation: do we run off our tanks, or does the
         venue have a hookup?

      Payment: 50% to confirm, balance day-of.

      Reply yes to lock in and I will send the contract.

      {operator_first_name}
      {company_name}

  catering_beo_wedding:
    channel: email
    subject: "BEO for your wedding on {event_date}"
    body: |
      Hi {contact_first_name},

      Congratulations on the wedding. Here is the BEO for your reception
      service.

      Event date: {event_date}
      Load-in: {load_in_time}
      Service window: {service_window}
      Location: {event_location}
      Guest count: {guest_count}

      Menu:
      {menu_items_list}

      Allergen and dietary notes captured: {dietary_notes}

      Per-person rate: {per_person_rate}
      Subtotal: {subtotal}
      Travel fee: {travel_fee}
      Tax: {tax}
      Total: {total}

      A few things we will need from you:
      1. Certificate of Insurance (we issue, listing your venue as
         additional insured)
      2. Final guest count confirmed 7 days out
      3. Propane and water access at the venue

      Payment: 25% to hold the date, 50% at 30 days out, balance 7 days
      before the event.

      Reply yes to hold the date and I will send the contract.

      {operator_first_name}
      {company_name}

  dispatch_confirmation:
    channel: sms
    body: |
      Confirming tomorrow: {location}, {service_window}, load-in at
      {load_in_time}. Menu prep: {menu_prep_summary}. Propane status:
      {propane_status}. Forecast: {weather_summary}.

  permit_expiration_30d:
    channel: email
    subject: "{permit_type} expires in 30 days"
    body: |
      Heads up: your {permit_type} for {jurisdiction} expires on
      {expires_date} (30 days from today).

      Renewal portal: {renewal_url}
      Typical processing time: {processing_days} days
      Cost: {renewal_cost}

      I have set a follow-up reminder for 14 days out and a hard-block at
      3 days. Truck will not be dispatched on an expired permit.

  weekly_sales_digest:
    channel: email
    subject: "Weekly digest, week of {week_starting}"
    body: |
      Hi {operator_first_name},

      Week of {week_starting} recap:

      Total gross: {total_gross} ({comp_vs_last_week} vs last week)
      Catering: {catering_gross} across {catering_event_count} events
      Lot service: {lot_gross} across {lot_day_count} days

      Top 3 wins:
      1. {win_1}
      2. {win_2}
      3. {win_3}

      Top 3 misses:
      1. {miss_1}
      2. {miss_2}
      3. {miss_3}

      Suggested adjustments for next week:
      {next_week_suggestions}
```

## Required integrations

| Integration            | Purpose                                       | Read | Write    |
|------------------------|-----------------------------------------------|------|----------|
| Square for Restaurants | POS sales data, per-event recap               | yes  | no       |
| Toast Go               | POS sales data, per-event recap               | yes  | no       |
| Roaming Hunger         | Catering and event inquiry inbox              | yes  | no       |
| Truckster              | Catering inquiry inbox, public schedule       | yes  | optional |
| County health portal   | Permit renewal tracking (read-only)           | yes  | no       |
| Instagram / website    | Public schedule posting                       | no   | optional |
| Twilio (or similar)    | Outbound SMS                                  | no   | yes      |
| Email provider         | Outbound email                                | no   | yes      |
| OpenClaw Memory        | Cross-run state                               | yes  | yes      |
| OpenClaw Heartbeat     | Scheduled cadence triggers                    | yes  | yes      |

Roaming Hunger and Truckster integration is read-only via email forwarding
in most cases; their APIs are limited for direct operator access. Public
schedule write-back is optional.

## Safety notes

The skill will not dispatch the truck on a lapsed permit. This is non-
configurable. The dispatch logic blocks the day's schedule if any required
permit has expired.

The skill will not promise BEO terms it cannot deliver (a menu item not in
the truck's repertoire, a guest count outside the truck's safe service
capacity, a service window the propane and water capacity will not support).
It routes ambiguous catering inquiries to a human.

## Configuration

```yaml
config:
  truck_name: "Your Food Truck"
  truck_legal_name: "Your LLC dba Your Food Truck"
  approval_mode: operator_approves_all   # or "autonomous_after_2_weeks"
  catering_menu_tiers:
    - tier: 1
      per_person: 18
      description: "Standard street-style"
    - tier: 2
      per_person: 22
      description: "Premium with two protein options"
    - tier: 3
      per_person: 28
      description: "Plated wedding or upscale"
  travel_fee_zones:
    - zone: "Zone 1 (under 15 mi)"
      fee: 100
    - zone: "Zone 2 (15-30 mi)"
      fee: 175
    - zone: "Zone 3 (30-60 mi)"
      fee: 295
  permits:
    - permit_type: "County Health Permit"
      jurisdiction: "Anytown County"
      expires_date: "2026-12-31"
    - permit_type: "Fire Suppression Cert"
      jurisdiction: "State Fire Marshal"
      expires_date: "2026-09-15"
    - permit_type: "Commissary Letter"
      jurisdiction: "Anytown Health"
      expires_date: "2026-11-20"
  equipment:
    - name: "Flat-top"
      burn_rate_per_hour: 0.5
    - name: "Fryer"
      burn_rate_per_hour: 0.75
    - name: "Charbroiler"
      burn_rate_per_hour: 1.0
  autonomous_beo_threshold_guests: 100
```

## Quick install

```bash
mkdir -p ~/.claude/skills
mv food-trucks.md ~/.claude/skills/food-truck-dispatch-and-catering.md
# Edit the config block to match your truck
```

Launch OpenClaw and the skill is live. Run `triage catering inbox`,
`prep today dispatch and propane check`, or `compile weekly sales digest`
to invoke it on demand, or wait for Heartbeat.

## Want it wired to your stack?

This SKILL.md is the starting point. If you want it plugged into your specific
POS, catering marketplaces, permit list, and menu pricing on a fixed-price
two-week clock, with the founder writing every line of the build, the door
is at https://www.adhirajhangal.com/work

Install in 60 seconds

1. 1

   Drop the file into your OpenClaw skills directory

   Save the downloaded food-trucks.md as ~/.claude/skills/food-truck-dispatch-and-catering.md (or scope it in your project-level .claude/skills/). OpenClaw picks up new skill files on next agent launch.

2. 2

   Connect Square, Toast Go, Roaming Hunger, and Truckster

   Edit the integrations block to point at Square or Toast Go for POS sales data, your Roaming Hunger and Truckster inboxes for catering and event inquiries, and your county health portal URL for permit tracking. Read access is enough to start.

3. 3

   Launch in approval mode, then move to autonomous on safe templates

   Run for two weeks with you approving every outbound BEO and dispatch confirmation. The skill's defaults route catering quotes over 150 guests, multi-day festival bookings, and any quote requiring a private-event waiver to a human. After two weeks, flip standard 25-100 guest BEOs to autonomous.

Example conversation

Common questions

Related free skills