Agent skill

Doordash Order Playbooks

by davila7 in davila7/claude-code-templates

Named, context-bound saved DoorDash orders ("post-gym", "late-night deploy") recalled through the DoorDash CLI (dd-cli) with a mandatory cart-diff before any checkout link is handed over.

MITAuto-check passed

Install Doordash Order Playbooks

skills CLI
$ npx skills add davila7/claude-code-templates --skill doordash-order-playbooks -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install davila7/claude-code-templates doordash-order-playbooks --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-tool/components/skills/doordash/doordash-order-playbooks .claude/skills/doordash-order-playbooks && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
doordash-order-playbooks
GitHub stars
33k
Token cost
~1.6k tokens
SKILL.md length
706 words
Files
1
Skills in repo
479
Repo updated
First seen
Licence
MIT

At a glance

Named, context-bound saved DoorDash orders ("post-gym", "late-night deploy") recalled through the DoorDash CLI (dd-cli) with a mandatory cart-diff before any checkout link is handed over.

  • Works in 3 steps: Run dd-cli order reorder --help and… → On the first real recall, after running… → Record the outcome in preflight.verified…
  • The user names a saved order (order my post-gym bowl
  • SKILL.md covers Why this exists, State, Preflight (first use only —… and Flow 1 — Recall (the main flow), plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Doordash Order Playbooks is an agent skill from davila7/claude-code-templates. Named, context-bound saved DoorDash orders ("post-gym", "late-night deploy") recalled through the DoorDash CLI (dd-cli) with a mandatory cart-diff before any checkout link is handed over. Use when the user names a saved order ("order my post-gym bowl", "the usual", "my Friday ramen"), wants to save the order they just placed as a playbook, or asks to list/remove saved orders. Persists name→order-uuid playbooks across sessions, catches silent menu/price drift on every recall, and self-heals stale playbooks when a…

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with macOS. The repository describes itself as: CLI tool for configuring and monitoring Claude Code. The licence is MIT.

When your agent uses it

  • The user names a saved order (order my post-gym bowl
  • My Friday ramen)
  • Wants to save the order they just placed as a playbook
  • Asks to list/remove saved orders

Example prompts

  • “post-gym”
  • “late-night deploy”
  • “order my post-gym bowl”
  • “/doordash-order-playbooks”

Requirements

  • Pre-approved tools (allowed-tools): Bash(dd-cli:*), Bash(command -v:*), Bash(mkdir:*), Bash(cat:*), Bash(jq:*), Read, Write, Edit

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Run dd-cli order reorder --help and dd-cli order checkout-url --help
  2. On the first real recall, after running reorder, confirm the output
  3. Record the outcome in preflight.verified (+ any format notes in

What it can do on your machine

Read from SKILL.md and the folder at commit c0ca7da. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(dd-cli:*)
    • Bash(command -v:*)
    • Bash(mkdir:*)
    • Bash(cat:*)
    • Bash(jq:*)
    • Read
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Doordash Order Playbooks loads about 1.6k tokens when it runs. Until then it costs about 156 tokens; SKILL.md has 706 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~156
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from davila7/claude-code-templates at commit c0ca7da, republished under its MIT licence (© davila7). 706 words, ~1,569 tokens.

Download SKILL.mdSave it as .claude/skills/doordash-order-playbooks/SKILL.md (or your agent's skills folder).
name
doordash-order-playbooks
description
Named, context-bound saved DoorDash orders ("post-gym", "late-night deploy") recalled through the DoorDash CLI (dd-cli) with a mandatory cart-diff before any checkout link is handed over. Use when the user names a saved order ("order my post-gym bowl", "the usual", "my Friday ramen"), wants to save the order they just placed as a playbook, or asks to list/remove saved orders. Persists name→order-uuid playbooks across sessions, catches silent menu/price drift on every recall, and self-heals stale playbooks when a restaurant's menu changes. Requires dd-cli (macOS Apple Silicon, waitlist-gated).
allowed-tools
Bash(dd-cli:*), Bash(command -v:*), Bash(mkdir:*), Bash(cat:*), Bash(jq:*), Read, Write, Edit
tags
DoorDash, Food Delivery, CLI, Saved Orders, Reorder, Automation

DoorDash Order Playbooks

Saved orders with names and contexts, recalled safely. A playbook maps a human name ("post-gym", "late-night deploy", "Friday ramen") to a concrete DoorDash order that can be rebuilt with dd-cli order reorder — plus enough stored detail to detect drift (menu changes, price hikes, substitutions) before the user is ever handed a checkout link.

Unofficial community skill built on DoorDash's doordash-oss/doordash-cli. dd-cli must be installed, on PATH, and logged in (dd-cli login).

Why this exists

dd-cli order history already lists past orders — but Claude has no cross-session memory of which order is "the post-gym one", and plain reordering silently accepts whatever the restaurant's menu says today: substituted items, missing items, higher prices. This skill stores the mapping AND makes a cart-diff against the stored baseline mandatory before emitting any checkout URL. Silent drift becomes a caught event.

State

Single JSON file: ~/.claude/dd-cli/playbooks.json

json
{
  "playbooks": {
    "post-gym": {
      "order_uuid": "<uuid from dd-cli order history>",
      "restaurant": "Sweetgreen",
      "items_summary": [
        { "name": "Harvest Bowl", "qty": 1, "price": 13.95 },
        { "name": "Lemonade", "qty": 1, "price": 3.5 }
      ],
      "baseline_total": 17.45,
      "tolerance_pct": 10,
      "contexts": ["post-gym", "gym", "workout"],
      "last_used": "2026-07-19",
      "times_used": 4
    }
  },
  "preflight": { "verified": false, "notes": "" }
}

Create the directory and file on first use (mkdir -p ~/.claude/dd-cli). Prices are pre-fee subtotals — say so when presenting totals.

Preflight (first use only — REQUIRED)

This skill assumes dd-cli order reorder --order-uuid Y returns a cart-uuid that cart show and order checkout-url accept. That handoff is load-bearing and must be verified empirically once per install:

  1. Run dd-cli order reorder --help and dd-cli order checkout-url --help to confirm flags.
  2. On the first real recall, after running reorder, confirm the output contains a cart-uuid and that dd-cli cart show --cart-uuid <it> works.
  3. Record the outcome in preflight.verified (+ any format notes in preflight.notes) so future sessions skip this step.

If the handoff does NOT work as assumed, fall back to rebuilding the cart manually (dd-cli search → cart add-items) and record that in preflight.notes.

Flow 1 — Recall (the main flow)

User says something like "order my post-gym bowl" / "the usual after the gym":

  1. Match: fuzzy-match the request against playbook names and contexts. Ambiguous → ask. No match → offer Flow 2 (capture) instead.

  2. Rebuild: dd-cli order reorder --order-uuid <stored uuid>. Capture the cart-uuid from the output.

  3. MANDATORY diff: run dd-cli cart show --cart-uuid <cart-uuid> and compare against the stored items_summary + baseline_total:

    StoredCurrent
    Harvest Bowl$13.95$14.95 ⬆
    Lemonade$3.50❌ missing
    Subtotal$17.45$14.95

    Present the diff table to the user. Never skip this step, even when everything matches — say "matches your baseline" explicitly.

  4. Gate: if items are missing/substituted, or the subtotal exceeds baseline_total by more than tolerance_pct, STOP and ask the user how to proceed (accept, edit cart via cart remove-item/cart add-items, or abort). Do NOT hand over a checkout link silently.

  5. Checkout: only after the diff is shown (and approved when the gate tripped): dd-cli order checkout-url --cart-uuid <cart-uuid>. Hand the URL to the user — payment always happens on the DoorDash page, by the human.

  6. Update: bump last_used / times_used; if the user accepted new prices, offer to refresh items_summary and baseline_total.

Show full SKILL.md (237 more words)Show less

Flow 2 — Capture

After ANY completed order (via playbook or bespoke), offer once — don't nag: "Want to save this as a playbook?" If yes:

  1. dd-cli order history — take the most recent order's uuid.
  2. Ask for a name and optional context words ("when should I suggest this?").
  3. Write the entry with items_summary and baseline_total from the cart that was just built (or from the history entry if it shows detail).
  4. Default tolerance_pct: 10.

Flow 3 — Staleness / self-heal

When order reorder fails or the diff shows the restaurant no longer offers the stored items:

  1. Tell the user the playbook is stale and why.
  2. dd-cli search --query "<restaurant name>" — confirm the restaurant still exists on DoorDash. Gone → offer to retire the playbook or find a replacement.
  3. Rebuild an equivalent cart (cart add-items, navigating with --help as needed), confirm with the user, and after a successful checkout-url handoff refresh the playbook's order_uuid from dd-cli order history.

Rules

  • Never emit a checkout URL without showing the diff first. This is the contract of the skill.
  • Read uuids from real command output; never fabricate or guess them.
  • One capture offer per order, max. Respect a "no".
  • Totals you can verify are pre-fee subtotals; final totals (fees, tip, tax) appear only on the DoorDash payment page. Say so.
  • If dd-cli reports auth/waitlist errors, stop and tell the user to run dd-cli login — don't retry in a loop.

© davila7, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in cli-tool/components/skills/doordash/doordash-order-playbooks of davila7/claude-code-templates.

Open the folder on GitHubat commit c0ca7da

Compare with similar skills

Doordash Order Playbooks next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Doordash Order Playbooks compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Doordash Order Playbooks this skilldavila7/claude-code-templates33k—~1.6kAutomated safety check: PassMIT
Site ArchitectureAvdLee/RocketSimApp80611 repos~3.3kAutomated safety check: PassCustom licence
Engine Whats Newflutter/flutter180k—~978Automated safety check: PassBSD-3-Clause
macOS Spm App PackagingDimillian/Skills4k5 repos~1.2kAutomated safety check: PassMIT
Openclaw Live Updateropenclaw/openclaw392k—~3.7kAutomated safety check: PassMIT
Orca iOS Simulator Controlstablyai/orca89k1 repos~584Automated safety check: PassApache-2.0

Similar skills

  • Site Architecture

    AvdLee/RocketSimApp

    When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking.

    806 GitHub starsUsed in 11 repos~3.3k tokens
    Marketing & SEOAuto-check passed
  • Engine Whats New

    flutter/flutter

    Generates the "what's new" release summary and diff file for changes in the Flutter engine (//engine/src/flutter) between two releases (e.g., 3.47 vs 3.44).

    180k GitHub stars~978 tokensUpdated today
    MobileAuto-check passed
  • macOS Spm App Packaging

    Dimillian/Skills

    Scaffold, build, and package SwiftPM-based macOS apps without an Xcode project.

    4k GitHub starsUsed in 5 repos~1.2k tokens
    MobileAuto-check passed
  • Openclaw Live Updater

    openclaw/openclaw

    Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.

    392k GitHub stars~3.7k tokensUpdated today
    DevOps & CloudAuto-check passed
  • iOS Simulator control from inside Orca, with the live device view in Orca's emulator pane. Use when driving a booted Apple Simulator on macOS: taps, gestures…

    89k GitHub starsUsed in 1 repo~584 tokens
    MobileAuto-check passed
  • A catalog of recurring bug shapes in the Mole Mac cleaner, used to review safety-sensitive diffs for deletion safety, unbounded commands, shell traps and weak tests.

    70k GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed

More from davila7/claude-code-templates

All 479 skills in this repo
  • Perplexity Web Search

    davila7/claude-code-templates

    Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.

    33k GitHub starsUsed in 11 repos~3.5k tokens
    Auto-check: notes
  • Neuropixels Data Analysis

    davila7/claude-code-templates

    Analyzes Neuropixels recordings from SpikeGLX or Open Ephys through preprocessing, drift correction, Kilosort4 spike sorting, quality metrics and curation.

    33k GitHub starsUsed in 9 repos~2.8k tokens
    Auto-check passed
  • Scientific Venue Templates

    davila7/claude-code-templates

    Supplies LaTeX templates and formatting rules for journals, conferences, posters, and grant proposals, then can check a draft against them.

    33k GitHub starsUsed in 9 repos~5.1k tokens
    Auto-check: notes
  • Brand Voice Content Creator

    davila7/claude-code-templates

    Analyzes a brand's existing writing to lock in a consistent voice, then builds SEO blog posts and platform-specific social content around it.

    33k GitHub starsUsed in 3 repos~1.9k tokens
    Auto-check passed
  • CAPA Officer

    davila7/claude-code-templates

    Guides corrective and preventive action (CAPA) work in a quality management system, from initiation and root cause analysis through effectiveness verification.

    33k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Fda Consultant Specialist

    davila7/claude-code-templates

    Senior FDA consultant and specialist for medical device companies including HIPAA compliance and requirement management.

    33k GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check passed

Works with

Questions about Doordash Order Playbooks

What does Doordash Order Playbooks do?

Named, context-bound saved DoorDash orders ("post-gym", "late-night deploy") recalled through the DoorDash CLI (dd-cli) with a mandatory cart-diff before any checkout link is handed over. Doordash Order Playbooks is an agent skill from davila7/claude-code-templates. Named, context-bound saved DoorDash orders ("post-gym", "late-night deploy") recalled through the DoorDash CLI (dd-cli) with a mandatory cart-diff before any checkout link is handed over.

When should I use Doordash Order Playbooks?

Doordash Order Playbooks fits situations like: the user names a saved order (order my post-gym bowl; my Friday ramen); wants to save the order they just placed as a playbook; asks to list/remove saved orders.

How do I install Doordash Order Playbooks in Claude Code?

Run `npx skills add davila7/claude-code-templates --skill doordash-order-playbooks -a claude-code`. Or copy the skill folder (cli-tool/components/skills/doordash/doordash-order-playbooks in davila7/claude-code-templates) into .claude/skills/doordash-order-playbooks in your project. Claude Code loads it when a task matches its description.

How do I install Doordash Order Playbooks in Codex?

Run `npx skills add davila7/claude-code-templates --skill doordash-order-playbooks -a codex`. Or copy the skill folder (cli-tool/components/skills/doordash/doordash-order-playbooks in davila7/claude-code-templates) into .agents/skills/doordash-order-playbooks in your project. Codex loads it when a task matches its description.

Can I use Doordash Order Playbooks in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davila7/claude-code-templates --skill doordash-order-playbooks -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/doordash-order-playbooks, .gemini/skills/doordash-order-playbooks, .github/skills/doordash-order-playbooks and .opencode/skills/doordash-order-playbooks in your project.

What does Doordash Order Playbooks need to run?

SKILL.md names no scripts, command-line tools or credentials: Doordash Order Playbooks is instructions for the agent only. Its frontmatter pre-approves these tools: Bash(dd-cli:*), Bash(command -v:*), Bash(mkdir:*), Bash(cat:*), Bash(jq:*), Read, Write, Edit.

Does Doordash Order Playbooks access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Doordash Order Playbooks safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Doordash Order Playbooks use?

Doordash Order Playbooks is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Doordash Order Playbooks use?

About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Doordash Order Playbooks?

Skills that share tags, products or a category with Doordash Order Playbooks: Site Architecture (AvdLee/RocketSimApp, 806 stars), Engine Whats New (flutter/flutter, 180k stars), macOS Spm App Packaging (Dimillian/Skills, 4k stars) and Openclaw Live Updater (openclaw/openclaw, 392k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Doordash Order Playbooks?

davila7 (a GitHub user) maintains it in davila7/claude-code-templates, which has 32,512 GitHub stars. The repository holds 479 skills in this directory. The repository was last updated on October 10, 2026.

Source: davila7/claude-code-templates on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.