Agent skill · data analytics · davila7
doordash-order-ledger
Accountability layer for agent-driven DoorDash ordering. Works with the doordash-audit-log hook (which appends every dd-cli invocation to an append-only audit log) and the /doordash-report command to answer "what has my AI been ordering and what did it cost" from data instead of memory. Use when the user asks about their DoorDash spending, ordering patterns, what the agent did in past sessions, or wants jq recipes for querying the audit log. Covers log schema, query patterns, rotation, and privacy guidance.
Why this skill is useful
Provides specific jq query patterns and log schema for analyzing DoorDash ordering data that the AI wouldn't reliably generate on its own.
What it needs
Requires jq installed locally. About 2k tokens when loaded. Last updated 2026-08-06. 30,138 stars on the source repository.
What this skill does
DoorDash Order Ledger Every dd-cli command the agent runs is recorded by the doordash-audit-log hook in ~/.claude/dd-guard/audit.jsonl — one versioned JSON line per event. This skill teaches you to answer questions from that log instead of guessing. Install the bundle: hook doordash/doordash-audit-log (the recorder), command /doordash-report (reconciled summaries), this skill (querying). Composes with doordash-spend-guard (shares the ~/.claude/dd-guard/ state directory) but runs standalone. Line schema (v1) Commands are secret-stripped before persisting and truncated to 500 chars. The v field guards future schema changes — check it before assuming fields. Query recipes (jq) Answer from data, not memory: When the user asks a money question ("how much this week?"), prefer /doordash-report — it reconciles against real dd-cli order history and labels intent-only numbers honestly. Raw checkouturl counts are intents: the human may have abandoned the payment page. Honest semantics checkouturl ≠ purchase. It records that a link was issued. Only reconciliation against order history confirms money moved. Subtotals (when present via doordash-spend-guard's ledger) are pre-fee. The log records what went through Claude Code's Bash tool — orders placed by the human directly in a terminal or app are invisible to it. Maintenance Rotation: when audit.jsonl exceeds ~5 MB, rotate: mv audit.jsonl audit-$(date +%Y%m).jsonl && gzip audit-.jsonl (keep the gzips; they are the history). Never edit lines — append-only is the audit property. Corrections go in reports, not in the log. Privacy: this is a plaintext record of eating habits and schedules. Keep ~/.claude/dd-guard/ out of repos and backups you share. Mention this to the user the first time you query the log in a session.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills davila7/doordash-order-ledger