End-to-End Purchase Verification Is a Skill, Not a QA Wish
turns purchase-flow QA into a reusable agent skill for checkout, logging, metadata, and entitlement verification
The interesting bit here isn’t that an agent clicked through a checkout. It’s that Joel used an agent browser, a virtual credit card with a hard limit, and enough verification steps to prove the whole damn flow worked: purchase, logs, metadata, entitlements, the works.
That’s the difference between “the button works” and the business event happened correctly. A Google Ads campaign can send real buyers into a broken purchase path, and the bug might not be the visible checkout. It might be missing attribution, wrong metadata, no entitlement, bad logging, or a silent handoff failure after the money moves.
Joel’s Slack note names the useful frame: this is a skill issue. Not as an insult. As architecture. agent-browser plus gogcli plus a strong model like GPT-5.5 and a small instruction pack could make “verify the revenue path” a repeatable checklist instead of a heroic one-off.
This maps cleanly to joelclaw because the system already treats repeatable operator work as skills and workflows. The sharper version is a purchase-flow verification skill that knows how to buy safely, inspect receipts, check logs, validate entitlements, and leave receipts for the next agent.
Key Ideas
- Use browser automation to verify the customer-facing purchase path end to end, not just individual backend calls.
- Pair a virtual credit card with a hard dollar limit so agents can safely test real payment flows without creating an expensive little disaster.
- Treat checkout verification as a reusable skill: purchase, metadata, logging, entitlement, receipt, and rollback/cleanup.
- Google Ads infrastructure makes this more important because paid traffic turns hidden purchase bugs into cash leaks fast.
- gogcli can close the loop by checking email receipts, account messages, or other Google Workspace artifacts after purchase.
- The pattern fits agent loops as a reviewer-style gate: don’t mark the work done until a real browser proves the revenue path works.