Index of every page on this site: llms.txt
All skills
matisolina avatar

/purchases

@3dd91e1
by Mati Solinamatisolina/busy98 stars
14
Run it yourself

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.

  • 1 file
  • 3.1 KB
  • Updated 2 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/matisolina/busy/purchases

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈57 tokens for metadata: the name and description. ≈742 when used: this file.

Description uses 2.8% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈227 characters, or 2.8%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 3dd91e1. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 2 weeks ago

README badge

README badge for matisolina/busy/purchases