purchases
Skill428 starsChanged 30 days agoMITView on GitHub
Buy things for the owner within the spend policy. Use when the owner asks to order, buy, reorder, or find the best price for a product, or when a trusted person asks for a purchase on the owner's behalf. Compare prices, build the cart, stop before payment for a takeover, get approval above the spend threshold, and record the spend.
In this repository14 other files it gives its agents.
- daily-briefSkill
- diningSkill
- email-triageSkill
- filesSkill
- maritime-computerSkill
- maritimeSkill
- nandaindexSkill
- onboardingSkill
- researchSkill
- ridesSkill
- schedulingSkill
- travelSkill
- trusted-networkSkill
- web-appsSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 52
Stop at the payment step every time.
- Very specific: line 54
If the takeover returns success: false, do not retry.
- Distinctive: line 55
Read the confirmation page.
- Distinctive: line 74
Do not enter card numbers, CVVs or gift card codes.
- Distinctive: line 75
Do not change saved payment methods or addresses on a merchant account.
- Distinctive: line 76
Do not place an order when the total differs from what the owner approved.
- Distinctive: line 77
Do not split one purchase into several to stay under a limit.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Purchases
Money moves here, so the policy guard is strict. Read the spend policy
(perActionUsd, perDayUsd, askAbove, neverWithoutAsk, merchant lists)
as the rules you work within. When unsure, ask.
Gather
What exactly, quantity, acceptable substitutes, delivery deadline, budget,
preferred merchants from memory (memory_read). Reorders: check the journal
and memory for the last order and offer to repeat it.
Compare
web_searchthe product plus "price".web_fetchtwo or three merchant pages. Prefer merchants the owner has used (memory) andallowedMerchants. SkipblockedMerchantswithout comment unless asked.- Record for each: price, shipping, tax if shown, delivery date, return policy. The number you report is the total to the door.
- Text the owner the best two in one message, lead with the total, say the trade-off, recommend one.
Agent: Two options for the Anker 737 power bank. Amazon $89.99 with free delivery Thursday, easy returns. Anker direct $79.99 with code, ships in 5 to 7 days. I'd go Amazon for Thursday unless the ten dollars matters. Which?
Approval
- Total under
askAboveand the owner asked for the purchase in this conversation: proceed, then report. - Total at or above
askAbove, or the item falls underneverWithoutAsk, or the requester is not the owner:ask_ownerwith merchant, item, total and delivery date. "Buy the Anker 737 from Amazon, $89.99 total, arrives Thu? Go ahead?" Wait. No answer means no. - Over
perActionUsdor pastperDayUsdfor today: tell the owner the limit and stop. The owner can raise it in words; that is a policy change the server records, not something you do silently.
Checkout
- Open the merchant on the desktop (skill
maritime-computer). Add the exact item and quantity. Verify the cart line by zooming on price and quantity. - Proceed to checkout. If a login is needed,
request_takeoverwith reason "Log in to Amazon for the Anker order". - Fill shipping from memory only if the owner stored an address and said you may use it. Confirm the address on screen.
- Stop at the payment step every time.
request_takeoverwith reason "Enter payment and place the Anker 737 order, $89.99". The owner places the order. If the takeover returnssuccess: false, do not retry; tell the owner. - Read the confirmation page. Zoom on order number and total.
Record
- The approval you obtained is what the audit uses for spend. In addition,
journal_appendone line: date, merchant, item, total, order number. memory_writeany new stable fact: a preferred merchant, a size, a brand to avoid.- Text the owner: what, where, total, delivery date, order number.
For other people
A partner asking for a purchase ("order Maria more coffee pods") is purchase
at ask: build the comparison, then the approval goes to the owner, not the
requester. Tell the requester you are checking. Family, friends and contacts
cannot trigger purchases at all; decline kindly and offer to pass the message.
Do not
- Do not enter card numbers, CVVs or gift card codes. Ever.
- Do not change saved payment methods or addresses on a merchant account.
- Do not place an order when the total differs from what the owner approved.
- Do not split one purchase into several to stay under a limit.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

