wacli WhatsApp
AdvisoryAudited by Static analysis on May 5, 2026.
Overview
No suspicious patterns detected.
Findings (0)
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 used incorrectly, the agent could send a message or file to the wrong WhatsApp recipient, but the instructions require explicit user direction.
The skill can send WhatsApp messages and files, which is an external action, but it includes explicit permission and ambiguity-handling instructions.
Only send when the user explicitly provided (a) recipient and (b) message/file content and asked to send.
Confirm the recipient and content before sending, especially for files or sensitive messages.
Authorizing wacli gives the local CLI access to act through the user’s WhatsApp account.
The skill requires WhatsApp account authentication via the external wacli tool. This is expected for a WhatsApp CLI integration, but it grants account-level messaging capability.
Login (shows QR) and bootstrap initial sync: - `wacli auth`
Only authenticate wacli on a trusted machine and revoke the WhatsApp Web session if you no longer use it.
The safety of the actual WhatsApp CLI depends on the external wacli package source, which was not included in the reviewed artifacts.
The skill does not package or pin the CLI itself; it directs the user to install an external Homebrew tap.
If missing, suggest: - `brew install steipete/tap/wacli`
Review the Homebrew tap and wacli project before installing, and keep it updated from a trusted source.
WhatsApp chat history or identifiers may be available locally to the CLI and could be surfaced in agent context during searches.
The skill can search synced WhatsApp history and stores local WhatsApp-related data. This is purpose-aligned, but the data may be private.
Search messages: - `wacli messages search "<QUERY>"` ... Default store is `~/.wacli` on macOS; override with `--store DIR` or `WACLI_STORE_DIR`.
Search only when needed, avoid exposing private chat content unnecessarily, and use a controlled store directory if desired.
Background syncing may keep WhatsApp data current locally beyond the immediate message-sending task.
The skill recommends a long-running background sync process. This appears disclosed and purpose-related, but users should know it may continue operating until stopped.
Keep syncing in the background (recommended so messages/IDs resolve): - `wacli sync --follow`
Run background sync only when needed and stop it when finished if you do not want ongoing synchronization.