pp-forkable

<!-- GENERATED FILE — DO NOT EDIT. This file is a verbatim mirror of library/food-and-dining/forkable/SKILL.md, regenerated post-merge by tools/generate-skills/. Hand-edits here are silently overwritten on the next regen. Edit the library/ source instead. See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". --> # 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.5 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. ## 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. ## 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. **meal management (writes)** — place real orders and spend; **dry-run by default**, pass `--confirm` to apply. - `forkable-pp-cli meal set <deliveryId> --item <id> --menu <id> [--modifier <modifierId>:<optionId>] [--replace-piece <uuid>] [--note <text>] [--confirm]` — Override the auto-picked meal for one delivery day (`replacePiece`). `--replace-piece` takes the current piece's UUID (from `deliveries` or `served-history`). - `forkable-pp-cli meal set-all --deliveries <id,id> --item <id> --menu <id> [--modifier <modifierId>:<optionId>] [--confirm]` — Apply one meal item across several delivery days (`replaceAllPieces`). - `forkable-pp-cli meal confirm <deliveryId> [--unconfirm] [--confirm]` — Confirm (or `--unconfirm`) a delivery day (`confirmDelivery`). - `forkable-pp-cli meal skip <deliveryId> [--confirm]` — Skip / cancel one or more delivery days (`removeDelivery`); `--deliveries <id,id>` skips several. - `forkable-pp-cli reorder <fromDate> --onto <deliveryId> [--replace-piece <uuid>] [--confirm]` — Repeat the meal you had on a past date onto an upcoming delivery day. **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 <modifierId>:<optionId>[,<optionId>...]` (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 <uuid> --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 "<capability in your own words>" ``` `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. ## 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`) are dry-run by default and only mutate the account 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": <data> } ``` 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 <dir>` for one invocation, or set `FORKABLE_HOME=<dir>` 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. - Stored secrets live in `credentials.toml` under the data dir. Existing legacy `config.toml` secrets are read for compatibility and leave `config.toml` on the first auth write. - Run `forkable-pp-cli doctor --fail-on warn` to surface path and credential-location warnings. `agent-context` exposes a schema v4 `paths` block for agents that need the resolved dirs. - For MCP, pass relocation through the MCP host config. The MCP binary does not inherit CLI flags: ```json { "mcpServers": { "forkable": { "command": "forkable-pp-mcp", "env": { "FORKABLE_HOME": "/srv/forkable" } } } } ``` Fleet precedence: an inherited per-kind env var overrides an explicit `--home` for that kind. Use `FORKABLE_HOME` or per-kind vars as durable fleet levers, and use `--home` only for a single invocation. Relocation is not reversible by unsetting env vars; move files manually before clearing `FORKABLE_HOME`, or `doctor` will not find credentials left under the former root. ## Automatic learning This CLI ships a self-capturing learning loop. The CLI does its own bookkeeping: every invocation is journaled locally, a failed flag followed by a corrected retry auto-derives a `flag_alias` candidate, and a `teach` on a query family without a playbook auto-synthesizes a `playbook_candidate` from the session's journal. Your job is judgment only: `recall` first, act on surfaced candidates, `teach` the final answer, `playbook amend` when you observe a correction. You never record failures by hand. ### Step 1: `recall` before any discovery Before list/search/drill commands on a new user question, run: ```bash forkable-pp-cli recall "<user's question>" --agent ``` The response envelope: ```json { "query": "...", "normalized": "<normalized form>", "query_entities": ["..."], "found": true | false, "match_score": 0.0, "results": [ { "resource_id": "...", "resource_type": "...", "venue": "...", "confidence": 2, "entity_match": "exact|partial|unknown", "source": "taught|preseed|pattern", "warnings": ["..."] } ], "mismatches": [ /* only when --debug-mismatches */ ], "warnings": [ /* top-level */ ], "candidates": [ { "id": 12, "class": "flag_alias | playbook_candidate", "summary": "...", "sightings": 3, "last_seen": "...",