wolt-cli
PassAudited by ClawScan on May 10, 2026.
Overview
This is a coherent Wolt CLI helper, but it relies on an external local binary and can use Wolt credentials to read or change account/cart data, so users should trust the CLI and confirm mutations.
Before installing, make sure you trust the external `wolt` CLI and know where its local profile credentials are stored. Use explicit Wolt profiles, keep payment outputs masked, avoid sharing verbose diagnostic logs, and require a clear confirmation before any cart, address, favorite, or credential-configuration change.
Findings (4)
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.
If the local CLI or repository is not trusted, it may handle Wolt credentials and account requests outside what this skill package can verify.
The skill delegates setup and execution to an external repository/local binary that is not included in the reviewed artifacts.
Tool repository: https://github.com/mekedron/wolt-cli Open the repository for setup/build details, then use the local `wolt` binary
Review or pin the Wolt CLI source/version, confirm the `wolt` binary path, and install it only from a trusted source before providing credentials.
Anyone controlling the agent or local CLI could access the connected Wolt account within the CLI's permissions.
The skill uses Wolt access/refresh tokens or cookies and stores/refreshed credentials in local profile configuration.
wolt configure --profile-name default --wtoken "<token>" --wrtoken "<refresh-token>" --overwrite ... Credential fallback ... Explicit flags (`--wtoken`, `--wrtoken`, `--cookie`) ... refreshed automatically and persisted back to local config.
Use explicit profile names, avoid sharing tokens/cookies, verify where credentials are stored, and remove or rotate credentials when no longer needed.
A mistaken or over-broad confirmed command could change the user's Wolt basket, favorites, addresses, or stored credentials.
The CLI can mutate cart, favorites, address book, and local credential configuration, but the skill explicitly requires confirmation before those actions.
Request explicit confirmation before mutating commands: - `cart add`, `cart remove`, `cart clear` - `profile favorites add`, `profile favorites remove` - `profile addresses add`, `profile addresses update`, `profile addresses remove`, `profile addresses use` - `configure`
Confirm the exact command, profile, venue/item, and address before any mutation, and prefer read-only `show` or `preview` commands first.
The agent may display private order history, payment metadata, and related account details in conversation or logs.
The documented workflows read authenticated Wolt order and payment/profile information.
wolt profile orders --profile default --limit 20 --format json wolt profile orders show <purchase-id> --profile default --format json wolt profile payments --profile default --mask-sensitive --format json
Request only the specific account data needed, keep `--mask-sensitive` for payments, and avoid sharing verbose outputs or profile data unnecessarily.