Whats 1.0.0
v1.0.0Send WhatsApp messages to other people or search/sync WhatsApp history via the wacli CLI (not for normal user chats).
⭐ 0· 326·1 current·1 all-time
by@sieyer
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the required binary and commands: the skill only needs the wacli CLI to send messages, search/sync history, and the declared install options (homebrew formula or Go module) are appropriate for that purpose. Note: _meta.json ownerId/slug differ from registry metadata (minor metadata inconsistency to verify).
Instruction Scope
SKILL.md restricts use to explicit user requests and lists concrete wacli commands (auth, sync, send, search, backfill). It references the local store (~/.wacli) and recommends --json for parsing. This is expected for a CLI that holds WhatsApp auth/history, but the agent will gain access to message-sending when running these commands, so follow-the-user-confirmation safeguards in SKILL.md should be enforced.
Install Mechanism
Install options are a homebrew formula (steipete/tap/wacli) and a Go module (github.com/steipete/wacli/cmd/wacli). Both are standard, traceable install mechanisms (no arbitrary URL downloads or archive extraction).
Credentials
No environment variables or external credentials are requested by the skill, which is proportional. However, wacli itself performs QR auth and stores credentials/data under ~/.wacli; running the CLI grants access to account messages and the ability to send messages, which is expected but high-sensitivity — users should be aware.
Persistence & Privilege
always is false and the skill does not request persistent platform-level privileges or modify other skills. Autonomous invocation is allowed (platform default); consider requiring explicit user confirmation before any send actions (SKILL.md already recommends this).
Assessment
This skill is a straightforward wrapper for the wacli CLI and appears coherent. Before installing: 1) Confirm you trust the wacli upstream (review the homebrew formula and the GitHub module source if you can). 2) Understand that wacli requires QR-based auth and will store credentials and message history in ~/.wacli — anyone or any process that can run the CLI can access/send messages for that account. 3) Ensure the agent follows the SKILL.md safety steps (explicit recipient + message + confirmation) or restrict autonomous invocation for sending operations. 4) Note the small metadata mismatch in the included _meta.json (owner/slug); consider verifying the publisher identity if provenance matters.Like a lobster shell, security has layers — review code before you run it.
latestvk978n6m2630qjmhkmwy3shr7j5824v9a
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📱 Clawdis
Binswacli
Install
Install wacli (brew)
Bins: wacli
brew install steipete/tap/wacliInstall wacli (go)
Bins: wacli
go install github.com/steipete/wacli/cmd/wacli@latest