sonichi/sutando/skills/whatsapp/SKILL.md
Send WhatsApp messages, list chats, and search history via wacli (local CLI backed by a synced store at ~/.wacli). Use after the user has run `wacli auth` to pair the device.
Decision brief
Send messages, list chats, and search history using wacli — a local CLI that syncs a WhatsApp Web session into /.wacli/. No third-party service, no API key; the auth flow is a QR-code scan from the user's phone.
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/sonichi/sutando --skill "skills/whatsapp"Inspect the Agent Skill "whatsapp" from https://github.com/sonichi/sutando/blob/6a8f0fccd32e5aa620a3572c8885544f144bb6fe/skills/whatsapp/SKILL.md at commit 6a8f0fccd32e5aa620a3572c8885544f144bb6fe. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
The user asks to send a WhatsApp message, list chats, or search WhatsApp history.
steipete/tap is a third-party Homebrew tap (not Homebrew-core), and wacli stores a WhatsApp Web session locally at /.wacli/. Review the tap source before installing if security-sensitive.
Phone numbers are in E.164 (+countrycode...). For groups, pass the JID returned by wacli chats list instead of a phone number.
Always confirm message content with the user before sending. Matches the iMessage / SMS / X-post pattern in CLAUDE.md. The confirmation flow lives in the agent / bridge that calls wacli send — this skill itself has no c…
wacli: not authenticated → user must run wacli auth (QR-code flow). One-time per Mac.
Permission review
The documentation includes network, browsing, or remote request actions.
# See wacli's docs (https://github.com/steipete/wacli) for the full platform-string list.Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 78/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 359 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Send messages, list chats, and search history using wacli — a local CLI that syncs a WhatsApp Web session into ~/.wacli/. No third-party service, no API key; the auth flow is a QR-code scan from the user's phone.
wacli auth has completed on this Mac. Probe with wacli chats list --limit 1; if it errors "not authenticated," tell the user to run wacli auth (QR-code pairing from their phone).brew install steipete/tap/wacli # one-time install (3rd-party tap, NOT Homebrew-core)
wacli auth # opens a QR for the user to scan from WhatsApp → Linked Devices
steipete/tap is a third-party Homebrew tap (not Homebrew-core), and wacli stores a WhatsApp Web session locally at ~/.wacli/. Review the tap source before installing if security-sensitive.
The session lives at ~/.wacli/. Stays signed in across reboots until the user revokes the linked device from their phone.
Optional .env settings (label shown in WhatsApp's Linked Devices screen on the user's phone):
WACLI_DEVICE_LABEL=Sutando # any string; appears next to the device in WhatsApp → Linked Devices
WACLI_DEVICE_PLATFORM=CHROME # default per wacli is DESKTOP; CHROME is the fallback if an invalid value is set.
# See wacli's docs (https://github.com/steipete/wacli) for the full platform-string list.
wacli send text --to "+14155551234" --message "Hello!" # send
wacli send text --to "+14155551234" --message "$(cat draft.txt)" # multi-line via stdin / file
wacli chats list --limit 20 # recent chats
wacli messages search "keyword" --limit 10 # search history
wacli messages list --chat "+14155551234" --limit 20 # read a thread
Phone numbers are in E.164 (+countrycode...). For groups, pass the JID returned by wacli chats list instead of a phone number.
wacli send — this skill itself has no confirm step. Treating the SKILL.md as the confirmation surface would skip the check entirely on direct CLI invocations./tmp/wa-*.txt and pass via --message "$(cat /tmp/wa-X.txt)" — avoids shell-escape issues with quotes and emoji.wacli send text returning success means the message hit WhatsApp's servers, not that the recipient has read it.wacli: not authenticated → user must run wacli auth (QR-code flow). One-time per Mac.wacli: linked device revoked → user revoked the session from their phone. Re-run wacli auth.wacli: rate limited → WhatsApp is throttling. Back off ~30s and retry.+ prefix.Synthesizes the proposal in PR #180 by @priyansh4320 (stale + conflicts, never landed) and the wacli reference already documented in CLAUDE.md's "Built-in capabilities" section. Issue #179 (asking for WhatsApp support) was closed 2026-05-16 noting the capability had landed as inline doc.