Skill

dominos

Order pizza, browse menus, optimize deals, and track delivery from your terminal — with a local SQLite store that powers reorder, price comparison, and deal stacking no other Domino's tool offers.

Verified: 2026-05-13 (printing-press-ingest-2026-05-13+enrich-capability-skill)

When to use dominos

Choose if

You're driving a real Domino's order from an agent loop and want the full transactional surface (template replay with --dry-run safety, cross-store price comparison, deal stacking, live tracker stream) plus a local SQLite history for spend analysis. The alternative — building against Domino's undocumented consumer API directly — gives you no template replay, no deal optimizer, and no exit-code semantics.

Avoid if

You need pizza from any chain other than Domino's, or you're outside the Domino's USA footprint — the README scopes coverage to the Domino's consumer API only. Also avoid if your workload can't tolerate the ~1-hour token TTL or the lack of any offline fallback when Domino's API is down.

Risk Flags

  • MEDIUM auth Authentication relies on harvesting a Domino's bearer token from sessionStorage into ~/.config/dominos-pp-cli/config.toml. Token TTL is ~1 hour; agents must re-auth frequently or accept exit code 4 mid-flow.
  • MEDIUM scope Coverage is the Domino's USA consumer API only. International Domino's franchises, third-party aggregators (Uber Eats, DoorDash), and other pizza chains are out of scope — README makes no promise beyond Domino's.
  • LOW data_quality Menu rotations can invalidate replayed templates; the CLI offers FTS-substitute fallback but the agent must verify the substituted item is acceptable before confirming the order.

Cost

Type: Unknown

Install

Default

npx -y @mvanhorn/printing-press install dominos

Setup docs →

Estimated time to first success: ~10 min

Dependencies

Minimum runtime: Node.js (npx) or Go 1.26.3+ for source install

Distribution

Repository
https://github.com/mvanhorn/printing-press-library
License
MIT