How do I install the Swiggy Checkout skill?

Run npx skillmds@latest add hktitan/swiggy-checkout in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Swiggy Checkout safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Swiggy Checkout?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Swiggy Checkout free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Swiggy Checkout?

HKTITAN (@hktitan) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Swiggy Checkout by hktitan — Agent Skill

Name: Swiggy Checkout
Author: HKTITAN

Swiggy Checkout

Place a Swiggy Food or Instamart order with swiggy-cli, choosing Cash, UPI or Swiggy Money and getting explicit consent first. Use only when the user has said to place/confirm the order — never as an automatic continuation of adding to cart.

HKTITAN Updated Sep 17, 2026

File contents

swiggy-checkout

checkout calls place_food_order / checkout upstream. Orders cannot be cancelled through the API (Swiggy customer care: 080-67466729), so this skill is strict about consent.

Pre-flight (all three, every time)

swiggy <server> cart --json --no-interactive — read the live cart. Show items, quantities and the payable total.
Confirm the delivery address by text (swiggy <server> addresses --json → addressLine). "Delivering to: ."
Ask one direct question: "Place this order for ₹ to , paying by ?" Wait for an explicit yes. "Go ahead" after a search is not consent to spend money; "yes, place it" is.

Payment decision

Did the user name a method?
├── "cash" / "COD"                        → --pay cash
├── "UPI" / "GPay" / "PhonePe" / "Paytm"  → is a specific app id in payment-options?
│      ├── yes                            → --pay upi:<id copied exactly>
│      └── no / desktop / unknown device  → --pay upi          (scan-or-tap link works everywhere)
├── "Swiggy Money" / "wallet"             → run payment-options; use --pay swiggypay ONLY if the server lists it
└── nothing                               → run payment-options and show the list; do not pick for them

swiggy <server> payment-options --json is the source of truth: offer only methods it returns. Never ask the user for a UPI ID/VPA (not supported, NPCI rule).

Run

# Cash: order is placed immediately, no payment leg
swiggy food checkout --pay cash --yes --json --no-interactive
swiggy instamart checkout --pay cash --yes --json --no-interactive

# UPI: one command that places, shares the pay link, polls and confirms (blocks up to Swiggy's cap, ~5 min)
swiggy food checkout --pay upi --wait --yes --json --no-interactive
# UPI in two steps (agent hands the link over, resumes later) — see swiggy-pay
swiggy food checkout --pay upi --yes --json --no-interactive

--note "<text>" (Food only) sends a note to the restaurant, e.g. "less spicy". It is not for delivery instructions.

Read the result

meta.payment.pending === false and data.status CONFIRMED/PLACED → placed. Quote meta.message verbatim (it carries Swiggy branding) and save data.orderId.
meta.payment.pending === true → not placed yet. Say "Complete the payment in your UPI app, I'll confirm once it succeeds", give meta.payment.bridgeUrl, then follow swiggy-pay using meta.payment.next.
exit 10 PAYMENT_FAILED → read error.hint; do not call checkout again blindly.
exit 6 MCP_ERROR → surface error.message; then run swiggy <server> orders --active --json before any retry, because a 5xx may have placed the order anyway.

Never

Add --yes without the question in Pre-flight step 3 being answered "yes" in this conversation.
Call checkout twice for the same cart.
Announce success on a PENDING_PAYMENT response.
Substitute another address if the one the user named is missing; ask.

---name: swiggy-checkoutdescription: Place a Swiggy Food or Instamart order with swiggy-cli, choosing Cash, UPI or Swiggy Money and getting explicit consent first. Use only when the user has said to place/confirm the order — never as an automatic continuation of adding to cart.license: MIT---# swiggy-checkout`checkout` calls `place_food_order` / `checkout` upstream. Orders cannot be cancelled through the API (Swiggy customer care: 080-67466729), so this skill is strict about consent.## Pre-flight (all three, every time)1. `swiggy <server> cart --json --no-interactive` — read the live cart. Show items, quantities and the payable total.2. Confirm the delivery address by text (`swiggy <server> addresses --json` → `addressLine`). "Delivering to: <addressLine>."3. Ask one direct question: "Place this order for ₹<total> to <address>, paying by <method>?" Wait for an explicit yes. "Go ahead" after a search is not consent to spend money; "yes, place it" is.## Payment decision```Did the user name a method?├── "cash" / "COD" → --pay cash├── "UPI" / "GPay" / "PhonePe" / "Paytm" → is a specific app id in payment-options?│ ├── yes → --pay upi:<id copied exactly>│ └── no / desktop / unknown device → --pay upi (scan-or-tap link works everywhere)├── "Swiggy Money" / "wallet" → run payment-options; use --pay swiggypay ONLY if the server lists it└── nothing → run payment-options and show the list; do not pick for them````swiggy <server> payment-options --json` is the source of truth: offer only methods it returns. Never ask the user for a UPI ID/VPA (not supported, NPCI rule).## Run```bash# Cash: order is placed immediately, no payment legswiggy food checkout --pay cash --yes --json --no-interactiveswiggy instamart checkout --pay cash --yes --json --no-interactive# UPI: one command that places, shares the pay link, polls and confirms (blocks up to Swiggy's cap, ~5 min)swiggy food checkout --pay upi --wait --yes --json --no-interactive# UPI in two steps (agent hands the link over, resumes later) — see swiggy-payswiggy food checkout --pay upi --yes --json --no-interactive````--note "<text>"` (Food only) sends a note to the restaurant, e.g. "less spicy". It is not for delivery instructions.## Read the result- `meta.payment.pending === false` and `data.status` `CONFIRMED`/`PLACED` → placed. Quote `meta.message` verbatim (it carries Swiggy branding) and save `data.orderId`.- `meta.payment.pending === true` → **not placed yet.** Say "Complete the payment in your UPI app, I'll confirm once it succeeds", give `meta.payment.bridgeUrl`, then follow `swiggy-pay` using `meta.payment.next`.- exit 10 `PAYMENT_FAILED` → read `error.hint`; do not call checkout again blindly.- exit 6 `MCP_ERROR` → surface `error.message`; then run `swiggy <server> orders --active --json` before any retry, because a 5xx may have placed the order anyway.## Never- Add `--yes` without the question in Pre-flight step 3 being answered "yes" in this conversation.- Call checkout twice for the same cart.- Announce success on a `PENDING_PAYMENT` response.- Substitute another address if the one the user named is missing; ask.

Frequently asked questions