ClawHub

India Food Ordering - Swiggy, Zomato etc

v1.0.2

Unified food ordering assistant for India that supports Swiggy and Zomato workflows with strict pre-order confirmation, cart preview, address checks, and ven...

⭐ 0· 106·0 current·0 all-time
byASP@anugotta
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description match the instructions: all files describe multi-vendor ordering workflows, confirmation prompts, and fallback logic. The skill requests no env vars, binaries, or installs that would be unrelated to food ordering.
ℹ
Instruction Scope
SKILL.md stays largely within ordering workflow boundaries (search, build cart, confirm, place order). It assumes existence of external 'connectors' and asks the agent to execute order commands and to use user context (saved addresses, prior orders). That is expected for an ordering skill, but the wording is somewhat high-level/vague (e.g., 'Execute order command', 'reconstruct likely cart from user message/context'), which grants the agent discretion in how to act—ensure connector behavior and agent permissions are tightly controlled.
✓
Install Mechanism
Instruction-only; no install spec, no downloads, and no code execution artifacts. This is the lowest-risk install surface.
✓
Credentials
The skill declares no required environment variables, credentials, or config paths. References to logging and saved addresses are optional/operational and are proportionate to an ordering assistant, but you should confirm connectors handle payment credentials separately and securely.
✓
Persistence & Privilege
always:false and no install behavior. The skill does not request persistent system presence or modify other skills/config; it relies on separate connectors for auth and order execution.
Assessment
This skill is a documentation/workflow guide (no code, no installs, no secrets requested) and appears internally consistent. Before enabling it for live ordering: (1) verify the actual Swiggy/Zomato connectors the agent will use—confirm they require and store credentials securely and that you trust those connectors; (2) test in 'dry run' mode so the agent builds carts and prompts but cannot place real orders until you confirm; (3) confirm the agent cannot bypass the explicit confirmation step or access payment methods without an additional user gesture; and (4) review connector logging/retention settings for addresses and order history if you are concerned about privacy. If you want, I can list concrete checks to run against the connectors or simulate the confirmation prompt flow.

Like a lobster shell, security has layers — review code before you run it.

latestvk97d4m74n28kvd7ntr4ph22xk1836n7r

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

🍽️ Clawdis

Comments