القائمة
How to drive the swiggy-cli (a wrapper over the official Swiggy MCP servers) from inside an agent. Always run in machine mode, branch on stable error codes, and prefer the generic Layer B commands.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | swiggy-cli |
| description | How to drive the swiggy-cli (a wrapper over the official Swiggy MCP servers) from inside an agent. Always run in machine mode, branch on stable error codes, and prefer the generic Layer B commands. |
swiggy-cli is an unofficial community CLI over the three Swiggy MCP servers — Food, Instamart, Dineout. It exposes every upstream tool through one stable JSON envelope and consistent exit codes, making it safe to call from any agent loop.
Use this skill whenever the user asks an agent to:
If the user simply asks a factual question about Swiggy (e.g. "what cuisines do they have"), do not invoke the CLI — it requires a real authenticated account.
--json --no-interactive on every invocation.error.code, never on error.message. Codes are stable; messages aren't.place_food_order, book_table, checkout, flush_food_cart, clear_cart, delete_address exit with code 7 (CONFIRMATION_REQUIRED) without --yes. Escalate to the human, do not silently add --yes.swiggy schema <server> <tool> --json. Do not hard-code argument names.swiggy call <server> <tool> --input '<json>' is stable across upstream renames; the ergonomic Layer A verbs are sugar.swiggy servers --json # what servers exist
swiggy tools food --json # what tools the food server exposes
swiggy schema food search_restaurants --json # JSON Schema for one tool
swiggy call food search_restaurants --input '{"query":"biryani"}' --json
Success:
{ "ok": true, "server": "food", "tool": "search_restaurants", "data": <payload>, "meta": {} }
Failure:
{ "ok": false, "error": { "code": "AUTH_REQUIRED", "message": "...", "details": {} } }
| code | error.code | action |
|---|---|---|
| 0 | — | success |
| 2 | USAGE | fix arguments and retry |
| 3 | AUTH_REQUIRED | ask the human to run swiggy auth init |
| 4 | NOT_FOUND | tool not exposed; re-list with tools |
| 5 | NETWORK | retry once with backoff; then escalate |
| 6 | MCP_ERROR | inspect details; do not auto-retry mutations |
| 7 | CONFIRMATION_REQUIRED | ask the human; never auto-add --yes |
swiggy-search — search across food / instamart / dineoutswiggy-cart — read and mutate the food / instamart cartswiggy-checkout — place an order, with safety railsswiggy-dineout-booking — discover slots and book a tableswiggy-track — list / inspect / track ordersInspect or mutate the user's Swiggy food / Instamart cart through swiggy-cli. Use when the user says "add X to my cart", "what's in my cart", or "clear the cart".
Place a Swiggy food or Instamart order via swiggy-cli, with the right safety rails. Use only when the human has explicitly asked to checkout — not as a continuation of "add to cart".
Discover Swiggy Dineout restaurants, check available reservation slots, and book a table via swiggy-cli. Use when the user asks "book a table at X" or "is Y free at 8pm tomorrow".
Search restaurants, menu items, grocery products, or dineout venues on Swiggy via the swiggy-cli. Use when a user asks "find me X on Swiggy" or "what biryani places are open near me".
List, inspect, and live-track Swiggy food and Instamart orders via swiggy-cli. Use when the user asks "where's my order" or "what did I order yesterday".