--- name: pp-forkable description: "A CLI and MCP server for your Forkable office-lunch program, with a local database and history, spend, and preference queries the web app cannot answer, plus commands to set, confirm, and skip meal orders (dry-run by default; --confirm to apply). Trigger phrases: `what have I eaten on forkable`, `forkable lunch spend this month`, `which forkable venues do we use most`, `did my forkable meals match my dietary preferences`, `forkable week ahead`, `set my forkable meal`, `skip forkable tomorrow`, `use forkable`, `run forkable`." author: "Allen Lew" license: "Apache-2.0" argument-hint: " [args] | install cli|mcp" allowed-tools: "Read Bash" metadata: openclaw: requires: bins: - forkable-pp-cli install: - kind: go bins: [forkable-pp-cli] module: github.com/mvanhorn/printing-press-library/library/food-and-dining/forkable/cmd/forkable-pp-cli --- # Forkable — Printing Press CLI ## Prerequisites: Install the CLI This skill drives the `forkable-pp-cli` binary. **You must verify the CLI is installed before invoking any command from this skill.** If it is missing, install it first: 1. Install via the Printing Press installer. It defaults binaries to `$HOME/.local/bin` on macOS/Linux and `%LOCALAPPDATA%\Programs\PrintingPress\bin` on Windows: ```bash npx -y @mvanhorn/printing-press-library install forkable --cli-only ``` 2. Verify: `forkable-pp-cli --version` 3. Ensure the reported install directory is on `$PATH` for the agent/runtime that will invoke this skill. If the `npx` install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer). This installs into `$GOPATH/bin` (default `$HOME/go/bin`), so add that directory to `$PATH` instead: ```bash go install github.com/mvanhorn/printing-press-library/library/food-and-dining/forkable/cmd/forkable-pp-cli@latest ``` If `--version` reports "command not found" after install, the runtime cannot see the binary directory on `$PATH`. Do not proceed with skill commands until verification succeeds. Forkable exposes no public API. This CLI reverse-engineers the my-account app's GraphQL surface into a Go binary with clean read commands and agent-native output. On top of the raw reads it adds longitudinal views the product never shows — served-meal history, preference-vs-served drift, spend trends, allowance utilization, venue rotation, and a week-ahead digest — all fetched live from Forkable. It also exposes the my-account app's own meal-management mutations as meal set, meal set-all, meal confirm, meal skip, and reorder; these are dry-run by default and only place, confirm, or skip real orders when you pass --confirm. A fifth meal command, `meal feedback`, reports a problem with a delivered meal to Forkable via whichever of two real mechanisms actually handles it (both discovered by static analysis of the app's JS bundle, not documented anywhere): `addMemberReportedIssue`, a real GraphQL mutation for missing-item/missing-side reports with refund/credit resolution tracking and a same-day cutoff, or the REST "Contact Support" endpoint for everything else; see the Command Reference below. ## When to Use This CLI Use this CLI when an agent or script needs to query a Forkable office-lunch program from the terminal: what meals were served, how much was spent, which venues rotate, and whether served meals match stated dietary preferences. It is the only programmatic surface for Forkable and the only way to get longitudinal history the web app does not aggregate. It can also set, confirm, and skip upcoming meal deliveries on the user's behalf — those commands are dry-run by default and require `--confirm` to apply. All commands fetch live from Forkable (no local sync step). ## Anti-triggers Do not use this CLI for: - Do not place, change, or cancel meal orders without explicit user intent — the `meal set`, `meal set-all`, `meal confirm`, `meal skip`, and `reorder` commands mutate the real account and require `--confirm`; run them dry-run first and confirm the printed mutation before adding `--confirm`. - Do not use this CLI to add or remove club members or manage billing — use the Forkable web app. - Do not use this CLI for real-time delivery tracking notifications — those come via Forkable's email/Slack/SMS. - Do not run `meal feedback ... --confirm` without explicit user intent — like the four mutation commands above, it is a real, one-way action: it files an actual report or support request with Forkable and cannot be un-sent. Preview it first (the default, no-`--confirm` behavior) and confirm the printed request before adding `--confirm`. - Do not use `--category missing-item`/`missing-side` after Forkable's same-day cutoff (`reportMissingItemCutoff`, typically 1pm local restaurant time) — the mutation is server-side rejected past it. The CLI checks this proactively and fails fast with the cutoff time; fall back to `--category quality`/`other` to reach Forkable support through the always-available contact form instead. ## Unique Capabilities These capabilities aren't available in any other tool for this API. ### Local history that compounds - **`served-history`** — See every meal actually served to you over time, with date, venue, price, and dietary level. _Reach for this when an agent needs a longitudinal view of what a person has eaten, not just the current delivery._ ```bash forkable-pp-cli served-history --since 90d --agent ``` - **`preference-drift`** — Flag served meals that violate your stated dislikes or dietary restrictions, or miss your likes. _Use this to audit whether auto-selection is actually honoring dietary preferences over time._ ```bash forkable-pp-cli preference-drift --since 60d --agent ``` - **`venue-rotation`** — Rank venues by how often they've served you and how recently. _Use this to spot venue fatigue or under-used favorites across the whole synced window._ ```bash forkable-pp-cli venue-rotation --since 120d --agent ``` ### Making the opaque legible - **`why-picked`** — Explain why a delivery's meal was auto-selected by ranking candidate items and their scores. _Pick this to explain a single day's auto-selected meal; use preference-drift for aggregate conformance._ ```bash forkable-pp-cli why-picked --delivery 1219480 --agent ``` ### Finance and allowances - **`spend-trend`** — Bucket lunch spend into per-week or per-month totals with CSV export. _Reach for this when finance needs a time series of lunch cost, not a single delivery receipt._ ```bash forkable-pp-cli spend-trend --since 6mo --by month --csv ``` - **`allowance-burn`** — Show granted-vs-consumed allowance utilization per club, including multi-club comparison. _Use this to see which teams are over- or under-using their lunch budget._ ```bash forkable-pp-cli allowance-burn --by club --csv ``` ### Agent-native plumbing - **`upcoming-digest`** — One agent-shaped line per upcoming day: date, venue, auto-selected item, price, allowance headroom. _Pick this for a quick 'what's coming this week' summary an agent can read in one shot._ ```bash forkable-pp-cli upcoming-digest --agent ``` ## Command Reference **account** — - `forkable-pp-cli account` — Show the authenticated Forkable user: profile, roles, dietary preferences (likes/dislikes/restrictions), companies **buffet_addresses** — - `forkable-pp-cli buffet-addresses` — List your buffet delivery addresses (street, city, postal code, coordinates, club). **clubs** — - `forkable-pp-cli clubs` — List meal clubs (teams/offices) you belong to or manage, with delivery address, delivery days, allowances **csrf** — - `forkable-pp-cli csrf` — Fetch a CSRF token. Read-only. **deliveries** — - `forkable-pp-cli deliveries in-progress-ids` — List IDs of deliveries currently in progress. - `forkable-pp-cli deliveries list` — List your meal deliveries from a given date forward, including per-delivery orders, chosen menu items, receipts **meal_scores** — - `forkable-pp-cli meal-scores` — Show meal auto-selection scores (menuId, itemId, score) for a delivery and user across candidate menus. **menus** — - `forkable-pp-cli menus` — Get menu(s) with venue, sections, items, prices, dietary levels, ratings, and modifiers. **notifications** — - `forkable-pp-cli notifications` — List account notifications shown in the my-account app (title, description, links, publish window). **venue_usage** — - `forkable-pp-cli venue-usage` — Get per-venue usage keyed by venue id over a date range. Requires venue ids and from/to dates inlined in the query. **Stale default dates on `deliveries list` and `venue-usage`.** These two raw GraphQL passthrough commands ship a default `--query` with an example date baked directly into the query text. Running either with no flags can silently return an empty or misleading result (e.g. `deliveries list` with no overrides returns `{"count":0}` even when real deliveries exist) rather than an error. Always override the date argument with a real date — today's date for forward-looking reads, or a far-past date (e.g. `2000-01-01`, as `served-history`/`allowance-burn` already do internally) for full-history reads — before trusting a zero/empty result from either command. Other passthrough reads (`menus`, `meal-scores`) instead ship placeholder ids that need replacing — see each command's own entry above. **meal management (writes)** — place real orders and spend; **dry-run by default**, pass `--confirm` to apply. - `forkable-pp-cli meal set --item --menu [--modifier :] [--replace-piece ] [--note ] [--confirm]` — Override the auto-picked meal for one delivery day (`replacePiece`). `--replace-piece` takes the current piece's UUID (from `deliveries list`). - `forkable-pp-cli meal set-all --deliveries --item --menu [--modifier :] [--confirm]` — Apply one meal item across several delivery days (`replaceAllPieces`). - `forkable-pp-cli meal confirm [--unconfirm] [--confirm]` — Confirm (or `--unconfirm`) a delivery day (`confirmDelivery`). - `forkable-pp-cli meal skip [--confirm]` — Skip / cancel one or more delivery days (`removeDelivery`); `--deliveries ` skips several. - `forkable-pp-cli reorder --onto [--replace-piece ] [--confirm]` — Repeat the meal you had on a past date onto an upcoming delivery day. - `forkable-pp-cli meal feedback --category [--note ] [--piece ] [--item ] [--venue ] [--request-refund|--request-credit] [--confirm]` — Report a problem with a delivered meal to Forkable, via whichever real mechanism actually handles the category (see below). Dry-run by default like the four mutations above. - `forkable-pp-cli meal feedback list [--limit N]` — Lists this CLI's own local record of past attempts. `forkable-pp-cli meal feedback list --delivery ` instead fetches Forkable's own `myReportedIssues` live for that delivery — the real ground truth for missing-item/missing-side reports (resolution, refund/credit status), bypassing the local ledger. **`meal feedback` uses two real mechanisms, picked by `--category` — neither is a GraphQL "mutation" in the everyday sense of the four above, and neither is documented anywhere.** 1. `--category missing-item`/`missing-side` → **`addMemberReportedIssue`**, a real GraphQL mutation (same `mutation ($input: ...!) {...}` wire shape as the four above) backing the my-account app's per-meal "Report Missing Item" widget. Discovered in the SPA bundle's module 372 (`MealReportIssue` component). Requires `--piece` (the piece/meal UUID from `deliveries list`/`served-history`); the order id is resolved automatically by looking up which order contains that piece. Ties into the courier's Onfleet delivery photos and supports `--request-refund`/`--request-credit` resolution tracking via a `myReportedIssues` field on the delivery. **Time-gated**: Forkable enforces a same-day cutoff (`delivery.reportMissingItemCutoff`, confirmed live as 1pm local restaurant time) — a submission after it is rejected server-side with a payload-level error. This CLI checks the cutoff proactively before attempting the mutation and fails fast with the exact time if it's already passed, rather than spending a live call on a doomed request. 2. `--category wrong-item`/`quality`/`late`/`other` → **`POST /submit_contact_form`**, a plain REST call (not GraphQL) behind the generic "Contact Support" modal, with `{name, email, subject, message, market_id}`. Discovered in the SPA bundle's module 29822 (`getSubjectOptions()`/`submitContactForm()`) — its own copy for "Other Issues" says outright "please use Forkable Support", i.e. Forkable's own UI routes here too for anything the dedicated missing-item flow doesn't cover. `--category` maps to Forkable's subject list (`wrong-item`/`quality`→"Report Issue", `late`→"Delivery Status", `other`→"General Inquiry"); delivery id/venue/item/piece have no dedicated field on this form, so they're folded into the message text alongside `--note`. Not time-gated — always available, including as a fallback once the missing-item cutoff has passed. Building an accurate preview for either mechanism touches the network even without `--confirm` (mechanism 1 resolves the order id from `--piece`; mechanism 2 resolves your name/email and the delivery's market id) — unlike the four mutations above, which preview fully offline. Every `--confirm` attempt (submitted or rejected by Forkable, either mechanism) is also appended to a local `meal-feedback.jsonl` ledger under the CLI's data dir — a preview-only run makes no live-writing attempt, so it is not logged. This ledger is separate from the top-level `feedback` command (which is for friction with this *CLI*, not with a *meal*). **`--replace-piece` is effectively always required for `meal set` and `reorder`.** Forkable auto-selects a candidate meal for every delivery day before you ever touch it — in practice there is no delivery day with a genuinely empty slot, so omitting `--replace-piece` is a rare/theoretical path, not the default case. **Dry-run mode does not validate this.** A dry-run without `--replace-piece` renders a plausible-looking mutation preview and only fails at `--confirm` time, with a raw GraphQL error (`oldPieceId ... Expected value to not be null`). Before running `--confirm`, always look up the target delivery's current piece id via `deliveries list` (its `orders[].pieces[].id`) and pass it with `--replace-piece`. `meal set-all` has no `--replace-piece` flag — `replaceAllPieces` takes no old-piece id at all, so this caveat doesn't apply to it. **Required item options — `--modifier`.** An item with a required option group (e.g. "Choose Protein", `min: 1`) is rejected by Forkable unless you send a selection. Pass `--modifier :[,...]` (repeatable) — the CLI builds the `selectionsHash` (`{"16":[10]}`) the `replacePiece` mutation needs. Find modifier and option ids under each item's `modifiers` in the `menus` output. Example: `forkable-pp-cli meal set 12345 --item 678 --menu 90 --modifier 16:10 --replace-piece --confirm`. ### Finding the right command When you know what you want to do but not which command does it, ask the CLI directly: ```bash forkable-pp-cli which "" ``` `which` resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code `0` means at least one match; exit code `2` means no confident match — fall back to `--help` or use a narrower query. ## Recipes ### What have I eaten this quarter ```bash forkable-pp-cli served-history --since 90d --agent --select date,venue,name,price ``` Longitudinal list of served meals, narrowed to the high-signal fields to keep agent context small. ### Audit dietary conformance ```bash forkable-pp-cli preference-drift --since 60d --json ``` Flags any served meal that conflicts with your stated dislikes or restrictions. ### Monthly lunch spend for finance ```bash forkable-pp-cli spend-trend --since 6mo --by month --csv ``` Per-month spend totals exported as CSV for a budget close. ### Which teams are burning their allowance ```bash forkable-pp-cli allowance-burn --by club --csv ``` Granted-vs-consumed allowance utilization per club, side by side. ### This week's lunch at a glance ```bash forkable-pp-cli upcoming-digest --agent ``` One compact line per upcoming day for a quick agent-readable briefing. ### Flag a problem with today's meal ```bash forkable-pp-cli meal feedback 12345 --category missing-item --note "Rice was missing, that was pictured" --piece --confirm forkable-pp-cli meal feedback list --delivery 12345 --agent ``` Files a real "Missing Meal" report with Forkable before the same-day cutoff (dry-run without `--confirm` — preview it first), then checks its live resolution status. Find the `deliveryId`/`--piece` via `upcoming-digest` or `deliveries list`. Past the cutoff, use `--category quality`/`other` instead to reach Forkable support through the always-available contact form. ## Auth Setup Forkable authenticates with a browser session cookie plus a per-request CSRF token fetched from /api/v2/csrf_token. Log in to forkable.com in Chrome, then run 'forkable-pp-cli auth login --chrome' to import your session. There is no API key. Run `forkable-pp-cli doctor` to verify setup. ## Agent Mode Add `--agent` to any command. Expands to: `--json --compact --no-input --no-color --yes`. - **Pipeable** — JSON on stdout, errors on stderr - **Filterable** — `--select` keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs: ```bash forkable-pp-cli buffet-addresses --query example-value --agent --select id,name,status ``` - **Previewable** — `--dry-run` shows the request without sending - **Safe writes** — read commands query Forkable; the write commands (`meal set`, `meal set-all`, `meal confirm`, `meal skip`, `reorder`, `meal feedback`) are dry-run by default and only mutate the account (or, for `meal feedback`, submit a real support request) when invoked with `--confirm` - **Live fetch** — commands query Forkable directly over GraphQL; there is no local sync/cache step - **Non-interactive** — never prompts, every input is a flag ### Response envelope Commands that read from the local store or the API wrap output in a provenance envelope: ```json { "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."}, "results": } ``` Parse `.results` for data and `.meta.source` to know whether it's live or local. A human-readable `N results (live)` summary is printed to stderr only when stdout is a terminal AND no machine-format flag (`--json`, `--csv`, `--compact`, `--quiet`, `--plain`, `--select`) is set — piped/agent consumers and explicit-format runs get pure JSON on stdout. ## Paths and state Agents should treat the CLI's path resolver as part of the runtime contract: - Use `--home ` for one invocation, or set `FORKABLE_HOME=` to relocate all four path kinds under one root. - Use per-kind env vars only when a specific kind must diverge: `FORKABLE_CONFIG_DIR`, `FORKABLE_DATA_DIR`, `FORKABLE_STATE_DIR`, `FORKABLE_CACHE_DIR`. - Resolution order is per-kind env var, `--home`, `FORKABLE_HOME`, XDG (`XDG_CONFIG_HOME`, `XDG_DATA_HOME`, `XDG_STATE_HOME`, `XDG_CACHE_HOME`), then platform defaults. - `config` contains settings like `config.toml` and profiles. `data` contains `credentials.toml`, `data.db`, cookies, and auth sidecars. `state` contains persisted queries, jobs, and `teach.log`. `cache` contains regenerable HTTP/cache files. -