Agent skill

Doordash Group Orders

by davila7 in davila7/claude-code-templates

Group food ordering through the DoorDash CLI (dd-cli) from a persistent team roster.

MITAuto-check passedDevOps & Cloud

Install Doordash Group Orders

skills CLI
$ npx skills add davila7/claude-code-templates --skill doordash-group-orders -a claude-code

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

GitHub CLI
$ gh skill install davila7/claude-code-templates doordash-group-orders --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-group-orders .claude/skills/doordash-group-orders && 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-group-orders
GitHub stars
33k
Token cost
~1.3k tokens
SKILL.md length
546 words
Files
1
Skills in repo
479
Repo updated
First seen
Licence
MIT

At a glance

Group food ordering through the DoorDash CLI (dd-cli) from a persistent team roster.

  • Works in 7 steps: Roster check: load team-food.json;… → Restaurant: intersect hard constraints… → Per-member choice: use their favorites… → …
  • Ordering for multiple people — team lunch
  • SKILL.md covers State, Flow 1 — Build a round, Flow 2 — Paste-a-thread intake and Flow 3 — Edits by person, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Doordash Group Orders is an agent skill from davila7/claude-code-templates. Group food ordering through the DoorDash CLI (dd-cli) from a persistent team roster. One request ("lunch for the team") fans out into a single merged cart with every line attributed to its eater via a person-to-cart-item-id ledger, per-person cost split with fee proration, payer rotation history, and a checkout gate that re-derives allergen conflicts against the roster live. Use when ordering for multiple people — team lunch, incident-response food, "collect orders from the thread" — or for /whose-turn payer…

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

It sits in DevOps & Cloud, covering Incident response. It works with Slack. The repository describes itself as: CLI tool for configuring and monitoring Claude Code. The licence is MIT.

When your agent uses it

  • Ordering for multiple people — team lunch
  • Incident-response food
  • Collect orders from the thread —
  • For /whose-turn payer rotation questions

Example prompts

  • “lunch for the team”
  • “collect orders from the thread”
  • “/doordash-group-orders”

Requirements

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

Workflow steps

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

  1. Roster check: load team-food.json; missing members → quick
  2. Restaurant: intersect hard constraints (a vegetarian on the roster =
  3. Per-member choice: use their favorites when the restaurant matches;
  4. Build the cart: dd-cli cart add-items ... per member's items (via
  5. Review: show the cart grouped by person with per-person subtotals.
  6. Checkout: emit the checkout URL (through dd-guard if installed). The
  7. Close the round: after the human confirms they ordered, pull the

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 Group Orders loads about 1.3k tokens when it runs. Until then it costs about 163 tokens; SKILL.md has 546 words of instructions outside code blocks.

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

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). 546 words, ~1,342 tokens.

Download SKILL.mdSave it as .claude/skills/doordash-group-orders/SKILL.md (or your agent's skills folder).
name
doordash-group-orders
description
Group food ordering through the DoorDash CLI (dd-cli) from a persistent team roster. One request ("lunch for the team") fans out into a single merged cart with every line attributed to its eater via a person-to-cart-item-id ledger, per-person cost split with fee proration, payer rotation history, and a checkout gate that re-derives allergen conflicts against the roster live. Use when ordering for multiple people — team lunch, incident-response food, "collect orders from the thread" — or for /whose-turn payer rotation questions. Handles paste-a-thread intake: paste a Slack/chat thread and it builds the order ledger from it.
allowed-tools
Bash(dd-cli:*), Bash(command -v:*), Bash(mkdir:*), Bash(cat:*), Bash(jq:*), Read, Write, Edit
tags
DoorDash, Team Lunch, Group Orders, Cost Split, CLI, Coordination

DoorDash Group Orders

Coordinating N people's food is exactly the cross-session state Claude drops: who's vegetarian, who hates cilantro, which cart line is Bob's, whose turn it is to pay. This skill keeps a roster, attributes every cart line to its eater, splits costs with fees prorated, and remembers payer history.

Unofficial community skill built on DoorDash's doordash-oss/doordash-cli. Note: dd-cli orders under ONE account — the account owner pays DoorDash; the split is for reimbursement (Venmo/transfer), not split payment.

State

  • team-food.json (project dir or ~/.claude/dd-cli/ — committable if the team shares a repo): the roster.
json
{
  "members": {
    "dani":  { "hard": ["vegetarian"], "allergens": [{ "name": "peanut", "severity": "anaphylaxis" }], "favorites": ["Veggie burrito bowl"], "dislikes": ["cilantro"] },
    "bob":   { "hard": [], "allergens": [], "favorites": ["Spicy chicken sandwich"], "dislikes": [] }
  }
}
  • .dd/round-<date>.json — the active round's ledger:
json
{
  "date": "2026-07-19",
  "cart_uuid": "...",
  "restaurant": "...",
  "orders": {
    "dani": [{ "item": "Veggie bowl", "cart_item_id": "41", "price": 12.5 }],
    "bob":  [{ "item": "Spicy chicken sandwich", "cart_item_id": "42", "price": 11.0 }]
  }
}
  • .dd/rounds.jsonl — history, one line per completed round: {"date": "...", "order_uuid": "...", "payer": "dani", "split": {"dani": 14.1, "bob": 12.4}}

Flow 1 — Build a round

"Order lunch for the team":

  1. Roster check: load team-food.json; missing members → quick interview (hard constraints, allergens + severity, a favorite, dislikes).
  2. Restaurant: intersect hard constraints (a vegetarian on the roster = only places with real vegetarian options). dd-cli search --query "..." → shortlist of 2-3 → let the human pick.
  3. Per-member choice: use their favorites when the restaurant matches; otherwise ask ONE question per member (or take answers from a pasted thread — Flow 2). Never guess for someone with allergens.
  4. Build the cart: dd-cli cart add-items ... per member's items (via the dd-guard wrapper when doordash-spend-guard is installed). After each add, run dd-cli cart show --cart-uuid <X> and record which cart-item-id belongs to whom in .dd/round-<date>.json. This ledger is what makes "quita lo de Bob" resolvable later.
  5. Review: show the cart grouped by person with per-person subtotals.
  6. Checkout: emit the checkout URL (through dd-guard if installed). The group gate hook independently re-checks allergens (see below).
  7. Close the round: after the human confirms they ordered, pull the order_uuid from dd-cli order history, compute the split, append to .dd/rounds.jsonl, and print a share-ready split table.
Show full SKILL.md (243 more words)Show less

Flow 2 — Paste-a-thread intake

The user pastes a Slack/chat thread ("who wants what"). Parse it into the round file: person → requested items. Unknown people → ask if they should join the roster. Ambiguous requests ("something spicy") → one clarifying question, or their favorite if the restaurant matches. Then continue Flow 1 from step 4.

Flow 3 — Edits by person

"Bob canceló" / "cambia lo de Sam": look up the person's cart_item_ids in the round ledger, dd-cli cart remove-item --cart-uuid X --cart-item-id N for each, update the ledger, re-show the grouped cart.

Cost split

  • Item subtotals per person from the round ledger.
  • Fees/tip/tax are only final on the payment page: split the known subtotal now, and offer the post-payment fallback — "tell me the final total and I'll prorate the difference by each person's share."
  • split = per-person items + prorated share of (final_total − subtotal) when provided.

/whose-turn

Read .dd/rounds.jsonl: sum what each member has paid vs. consumed across rounds; the next payer is the member with the largest (consumed − paid) balance. Show the balances so the answer explains itself.

Rules

  • Anyone with an anaphylaxis allergen gets the same vetting the doordash-allergy-shield skill applies — check their items against hidden-source synonyms, and never guess their order.
  • cart-item-ids come only from real cart show output.
  • The round ledger is the source of truth for attribution — keep it updated on every cart mutation, or person-level edits break.
  • Add .dd/ to .gitignore unless the team explicitly wants round history committed (it reveals eating habits).

© 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-group-orders of davila7/claude-code-templates.

Open the folder on GitHubat commit c0ca7da

Compare with similar skills

Doordash Group Orders 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 Group Orders compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Doordash Group Orders this skilldavila7/claude-code-templates33k—~1.3kAutomated safety check: PassMIT
Axiom SRE Investigatoropenclaw/clawhub9.5k—~7.1kAutomated safety check: PassMIT
Alerting Irmgrafana/skills2821 repos~1.9kAutomated safety check: PassApache-2.0
Oncall Irmgrafana/skills282—~1.4kAutomated safety check: PassApache-2.0
Vercel Incident Runbookjeremylongshore/tons-of-skills-marketplace2.8k—~2kAutomated safety check: PassMIT
Slack Incident Workflowautomateyournetwork/netclaw676—~2.1kAutomated safety check: PassApache-2.0

Similar skills

  • Axiom SRE Investigator

    openclaw/clawhub

    Investigates incidents and production problems with hypothesis-driven debugging, queries Axiom observability data when available, and keeps secrets out of commands and output.

    9.5k GitHub stars~7.1k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Alerting Irm

    grafana/skills

    Official

    Configure Grafana Alerting, Incident Response Management (IRM), and SLOs end-to-end — provisions Grafana-managed and data-source-managed alert rules, contact points (Slack/PagerDuty/email/webhook)…

    282 GitHub starsUsed in 1 repo~1.9k tokens
    DevOps & CloudAuto-check passed
  • Oncall Irm

    grafana/skills

    Official

    Route alerts, run on-call rotations, and drive incidents in Grafana IRM / OnCall — integrations (Alertmanager / Grafana Alerting / generic webhook / PagerDuty), Jinja2 routing + grouping templates…

    282 GitHub stars~1.4k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed
  • Vercel Incident Runbook

    jeremylongshore/tons-of-skills-marketplace

    Vercel incident response procedures with triage, instant rollback, and postmortem.

    2.8k GitHub stars~2k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Slack Incident Workflow

    automateyournetwork/netclaw

    Manage network incident response workflows in Slack - incident channels, status updates, escalation, resolution tracking, and post-incident review coordination.

    676 GitHub stars~2.1k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Slack User Context

    automateyournetwork/netclaw

    Leverage Slack user profiles, presence, DND status, and workspace context to personalize responses, route escalations, and coordinate team operations.

    676 GitHub stars~1.5k tokensUpdated yesterday
    DevOps & CloudAuto-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

Categories

Questions about Doordash Group Orders

What does Doordash Group Orders do?

Group food ordering through the DoorDash CLI (dd-cli) from a persistent team roster. Doordash Group Orders is an agent skill from davila7/claude-code-templates. Group food ordering through the DoorDash CLI (dd-cli) from a persistent team roster.

When should I use Doordash Group Orders?

Doordash Group Orders fits situations like: ordering for multiple people — team lunch; incident-response food; collect orders from the thread —; for /whose-turn payer rotation questions.

How do I install Doordash Group Orders in Claude Code?

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

How do I install Doordash Group Orders in Codex?

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

Can I use Doordash Group Orders 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-group-orders -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-group-orders, .gemini/skills/doordash-group-orders, .github/skills/doordash-group-orders and .opencode/skills/doordash-group-orders in your project.

What does Doordash Group Orders need to run?

SKILL.md names no scripts, command-line tools or credentials: Doordash Group Orders 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 Group Orders 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 Group Orders 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 Group Orders use?

Doordash Group Orders 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 Group Orders use?

About 1.3k tokens (SKILL.md is roughly 5.4k 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 Group Orders?

Skills that share tags, products or a category with Doordash Group Orders: Axiom SRE Investigator (openclaw/clawhub, 9.5k stars), Alerting Irm (grafana/skills, 282 stars), Oncall Irm (grafana/skills, 282 stars) and Vercel Incident Runbook (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Doordash Group Orders?

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.