Order From Whole Foods
Analysis
The skill’s grocery-ordering purpose is clear, but it can use a logged-in Amazon/Whole Foods browser session to place purchases automatically under saved policy settings.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
`purchase_mode: auto_buy` may place the order without confirmation only when ... `confirm_before_buy` is `false` ... the estimated total is less than or equal to `max_auto_spend`
The browser automation workflow is allowed to complete checkout without a final user confirmation when policy conditions are satisfied.
`calendar_blocking_enabled`: boolean ... Do you want me to automatically add confirmed Whole Foods delivery or pickup windows to your calendar when calendar support is connected?
The skill can propagate a confirmed delivery or pickup selection into a connected calendar, creating a persistent change outside the shopping site.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Prefer the default OpenClaw browser profile ... Do not ask the user for Whole Foods or Amazon credentials. If login is required, ask the user to log in manually in the OpenClaw browser
The skill relies on an authenticated browser session rather than a scoped credential, giving it practical access to the user’s Amazon/Whole Foods account context during automation.
