---
name: purchases
description: Load before you buy, book, order, reserve, subscribe to, or pay for anything for the user, before shopping or booking starts and not only at checkout, and whenever the user offers, sends, or mentions a payment card.
title: purchases
canonical_url: https://skilld.dev/gh/matisolina/busy/purchases
last_updated: 2026-11-12T03:00:58.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install matisolina/busy/purchases`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/purchases`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/matisolina/busy/purchases) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/purchases`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/purchases --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/purchases --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Purchases and payments

You can shop, book and check out for the user on your own computer's browser. You never spend on your own: every purchase needs the user's explicit yes for that exact order.

## Before checkout

1. Pin down what the user wants: the item or service, quantity, size or variant, dates, delivery address, and any budget. Use what the user told you and memory; ask only for what is really missing.
2. Find it and compare when that helps. Share options as Markdown links with prices, using the exact URLs you found.
3. Sign in or create accounts following the `sign-in` skill.

## Confirm the total

1. Go through checkout up to, but not including, the final pay/submit button.
2. Read the real numbers from the page: item, merchant, quantity, shipping, taxes, fees, total and currency, delivery or booking dates, and the cancellation or refund terms when shown.
3. Ask for an explicit yes with `ask_user`: a short question stating merchant, item and the exact total, with a primary option to place the order and a second option to cancel. Never assume a yes from an earlier message, from "just order it" before you knew the total, or from a routine.
4. If anything changes after the yes (price, total, dates, item), stop and ask again.

## Card details

- Enter a card only through `request_form` at the live checkout page: one field per input the page shows (card number, expiry, security code, name on card, billing postcode), naming the site. The hub fills the page directly; you never see the values. If the form can't fill a field (some embedded card frames), use `request_login` so the user types it on the screen.
- A bank verification step (a code by SMS, an app approval, a 3-D Secure page) goes to `request_form` for a code or `request_login` for anything else.
- If the user sends card details in chat anyway, use them for this checkout only. Never repeat them, never save them to memory, files, skills or routine prompts, and never type them anywhere except the merchant's payment fields.
- Don't lecture the user about how to pay.

## Place the order

1. Click the final pay/submit button only after the user's explicit yes.
2. Wait for the confirmation page.
3. Save proof: a PDF or screenshot of the confirmation page in /data/out, and send it with `send_file`. Tell the user the order or booking number, the total charged, and what happens next (delivery date, check-in time).
4. If a confirmation email arrives in a connected inbox, mention it.

## When something fails

- After an error, timeout, or a page that hangs after you clicked pay, **don't click pay again**. First check whether the order went through: the confirmation page, the account's order history, or a confirmation email. Retry only once you know it didn't, and with the user's yes.
- A declined card or a failed verification goes back to the user; don't try another card on your own.
- A purchase the user declined is final; don't ask again for the same order.
