secure-shopper
Asynchronous shopping research + checkout using secure-autofill (1Password-backed browser filling) with results recorded to workspace artifacts.
- License 许可
- MIT
- 最近更新
- 2026-06-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- secure-shopper
- metadata
- { "openclaw": { "emoji": "🛒" } }
- description
- Asynchronous shopping research + checkout using secure-autofill (1Password-backed browser filling) with results recorded to workspace artifacts.
03 SKILL.md 正文
secure-shopper 🛒
Find items across one or more shopping sites, summarize candidates, and (optionally) place the order using secure-autofill.
This skill is asynchronous: spawn a sub-agent for browsing so the main chat stays responsive.
Prerequisites
Required skills / plugin
- The secure-autofill skill exists at:
~/.openclaw/skills/secure-autofill/ - The secure-autofill plugin tools are available:
vault_suggestvault_fill
Inherit secure-autofill prerequisites
- A working non-headless Chrome (many shops block headless)
- Gateway environment has required env vars (per secure-autofill)
Concrete check:
command -v google-chrome || command -v google-chrome-stable
Configuration (portable)
Skill-local config files:
- Example (shareable, do not edit):
~/.openclaw/skills/secure-shopper/config.json.example - Real (machine-specific, written by onboarding):
~/.openclaw/skills/secure-shopper/config.json
Config keys:
goToSites[]: list of default shopping sites (e.g. Amazon, Walmart)location.ziporlocation.address: used for shipping/availability contextpreferences.priority: one of:relevancycheaperfasterreviews
preferences.maxCandidatesPerSite: cap per site (default 5)preferences.safeBrowsing: guardrails to avoid oversized pages / context overflow (applies to all sites)startFromSearch:true|false(default true) — prefer a site’s search results page over the homepage/product pagesmaxCandidatesPerPass: number (default 3) — extract a few items at a time (then paginate/scroll)snapshot: limits forbrowser.snapshotcompact: boolean (default true)depth: number (default 6)maxChars: number (default 12000)
fallback: what to do oncontext_length_exceededretryWithTighterSnapshot: boolean (default true)switchToSearchUrl: boolean (default true)
Initialization / installation / onboarding
Preferred (chat-first)
Ask Boss and then write config.json:
-
Go-to shopping website(s)
- Examples: Amazon, Walmart, Target
- Store into
goToSites[]
-
Zip code OR proximity address
- Store into
location.zipand/orlocation.address
- Store into
-
Preferences
- Ask for priority: relevancy vs cheaper vs faster delivery vs higher review scores
- Store into
preferences.priority(+ optional notes)
After collecting answers, update the real config file.
Optional helper (terminal):
node ~/.openclaw/skills/secure-shopper/scripts/onboard.mjs \
--sites 'Amazon=https://www.amazon.com|Walmart=https://www.walmart.com' \
--zip 46202 \
--priority cheaper
How it works (agent behavior contract)
0) Require a shopping description
The user must provide a description of their shopping task.
- If they didn’t: stop and ask for it.
1) Honor runtime user prompts
Runtime user instructions (the user’s message for this run) override stored config.
Examples of runtime overrides:
- “Use Target instead of Amazon.”
- “Only show Prime-eligible.”
- “Budget under $50.”
2) Login via secure-autofill (skip if already logged in)
- Use the configured go-to sites, unless the runtime prompt specifies a site.
- If the site session appears already authenticated: skip login.
- Otherwise, use secure-autofill login flow:
browser.snapshotto get refsvault_suggest/vault_fillto fill credentials
3) Make the browsing asynchronous
Immediately after accepting the task, respond with something like:
I’m en route to the stores. I’ll notify you when I find the best matches.
Then spawn a sub-agent so the main session is not interrupted.
Implementation note:
- Use
sessions_spawnwith a task that includes the shopping description and any runtime overrides.
4) Browse + identify candidates
The sub-agent browses each chosen site, searches, filters, and identifies candidates that fit the user description.
Context-safe browsing (ALL shopping sites)
Many shopping sites can produce extremely large pages/snapshots. To avoid context_length_exceeded failures:
- Prefer starting from a search results URL (or the site’s search box) rather than the homepage.
- Use small snapshots:
browser.snapshot(..., compact=true)- keep
depthmodest (e.g., 4–8) - set
maxCharsand/or target a specific container when possible
- Extract incrementally:
- grab top ~3 candidates, record them, then paginate/scroll and repeat until
maxCandidatesPerSiteis met
- grab top ~3 candidates, record them, then paginate/scroll and repeat until
- If a snapshot still overflows:
- retry with a tighter snapshot (smaller depth / smaller region)
- switch to a search URL (
/search?q=...) and re-extract
- Do not “reason through” massive dumps. If the page is huge, reduce the page slice first.
Record results to:
/home/miles/.openclaw/workspace/artifacts/secure_shopping/{timestamp}_shopping_task.json
JSON requirements:
- Record:
userPrompt(shopping description)startTimeendTimephase(required):candidates_found|awaiting_accept_deny|awaiting_checkout_confirm|ordered
candidates[]
- Candidates for the same request must live under the same parent task.
- Each candidate must include:
price(string)reviewScore(string/number)urlverdict(short)status:pending|accepted|denied|shopped
Suggested candidate shape:
{
"site": "Amazon",
"title": "...",
"price": "$39.99",
"reviewScore": "4.6 (12,345)",
"url": "https://...",
"verdict": "Best value under $50; good reviews; ships tomorrow",
"status": "pending"
}
Helper module (optional): scripts/task_io.mjs.
5) Notify user + REQUIRE accept/deny (hard gate)
When browsing is done, you must:
- Set JSON
phase = "awaiting_accept_deny". - Translate the JSON into a human-friendly summary.
- In the same message, require an ACCEPT/DENY decision. Do not end the turn without the prompt.
Mandatory message template (copy this structure):
- Recommended pick: <title> — <price> — <reviewScore> — <1-line why>
- Other options: (optional, 1–5 bullets)
- Choose: Reply with
A=accept/deny, B=accept/deny, ...(or “Accept A” / “Deny B”). - Next step: “If you accept one: do you want me to checkout, or stop at ready-to-buy?”
Hard rule:
- If you listed candidates/links but did not include an explicit Choose (ACCEPT/DENY) line, the output is invalid and must be rewritten before sending.
6) Apply accept/deny updates
Once the user replies:
- Update each candidate
statustoacceptedordenied. - Confirm the accepted candidate(s).
- Set JSON
phase:awaiting_checkout_confirmif at least one is accepted and checkout is not yet confirmed- keep
awaiting_accept_denyif the user’s response is ambiguous / incomplete
7) Checkout (only after explicit confirmation)
Before you click any “Place order” / “Submit” equivalent:
- Ask for a clear confirmation like: “Confirm checkout for A? (yes/no)”
- Set JSON
phase = "awaiting_checkout_confirm"until confirmed.
If the user confirms checkout:
- Navigate to the accepted candidate’s URL
- Add to cart / proceed to checkout
- Use secure-autofill to input payment/shipping info and submit
If secure-autofill reports an error:
- Do not guess.
- Pass the error back to the user.
8) Mark as shopped
If the order is successfully placed:
- update that candidate’s
statustoshopped - set JSON
phase = "ordered"
Notes / guardrails
- Never paste secrets.
- Checkout flows often require MFA / SMS verification; ask the user when needed.
- Prefer fewer high-quality candidates over a long list.
04 同仓库更多 Skills
crowd-prompting
A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.
ceaser
Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp <subcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir/UltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).
ceaser-send
Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp <subcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir/UltraHonk zero-knowledge proofs.
dilemm-ai
Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).
moldium
Post and manage content on the Moldium blog platform. Triggered by "post to Moldium", "write a blog post", "publish an article", etc.
arxiv-paper-reviews
Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date/category/interest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http://weakaccept.top:8000/.