Qfc Order
ReviewAudited by ClawScan on May 10, 2026.
Overview
This is a coherent QFC grocery-ordering automation skill, but it needs review because it can act through your logged-in Chrome/QFC session and its final scheduling/post-order steps are not clearly specified.
Use this only if you are comfortable letting an agent control your logged-in QFC tab. Before proceeding, require it to show the exact items, quantities, substitutions, store, pickup slot, total, and any final submit/place-order action, and close the browser relay afterward.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent could make or advance order-related changes in a logged-in QFC session without the provided instructions clearly requiring a final explicit approval at every high-impact step.
The skill is intended to perform high-impact cart, pickup, and post-order actions, but the provided artifact delegates these final steps to an undefined prior version. That leaves the exact approval, submission, update, and rollback boundaries unclear.
### 6. Schedule Pickup Slots (same as v2) ### 7. Final Review & Post-Order (same, update lists)
Define the slot-selection and final-order flow explicitly, including a final review of store, slot, items, substitutions, fees, total, and payment impact, and require a separate user confirmation before any submit/place-order action or grocery-list update.
Actions taken by the agent on QFC are performed as the logged-in user and can affect that account's cart, pickup slot, and order state.
The skill does not ask for stored credentials, but it uses the user's authenticated browser session, which gives it delegated authority over the QFC account/cart in that tab.
Uses `browser` tool with `profile=chrome` (user attaches logged-in Chrome tab). No credentials stored—user handles login.
Attach only the intended QFC tab, keep watching the session, and disconnect the browser relay when finished.
Incorrect list entries could lead to wrong cart additions, and order details may remain on disk after use.
The workflow is driven by persistent local grocery-list data and stores order details locally. This is purpose-aligned, but stale or edited state can affect what gets ordered and may retain shopping details.
glist = read(path="skills/grocery-list/grocery-list.json")
items = glist.items.filter(item => !item.checked)
...
`skills/qfc-order/qfc-state.json` | Order state: `{store, cart_items: [], scheduled_slot, order_id?, total?}`Review the proposed items and final cart carefully, keep the state files private, and clear qfc-state.json if you do not want order details retained.