WhatsApp router: history/search/read/send; wacrawl read, wacli live.
How do I install this agent skill?
npx skills add https://github.com/steipete/agent-scripts --skill whatsappIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill acts as a router for managing WhatsApp communications via two CLI tools, wacrawl and wacli. It defines safe boundaries between a local read-only archive and a live linked-device account for sending messages. The instructions include strong safety guidelines, such as requiring explicit user consent for any state mutation (sending messages) and preferring read-only flags for inspection.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
What does this agent skill do?
Use this as the first stop for WhatsApp work. Keep the source boundary sharp:
wacrawl: primary WhatsApp Desktop archive. Read-only, best local history, no network, no sending.wacli: linked-device accounts. Use for alt accounts, live sync, auth, sending, chat/group mutation, and WhatsApp Web protocol questions.
If the user names wacrawl or wacli repo work specifically, read that tool's own skill too.
Routing
- Primary WhatsApp reads/search/history: use
wacrawl. - Read/unread counts from WhatsApp Desktop: use
wacrawl; it has chat-level unread counts, not per-message read state. - Freshness-sensitive primary reads: check
wacrawl status; runwacrawl syncwhen asked or when current data matters. - Alt accounts such as
me,molty, or named stores: usewacli --account NAME. - Sending, reactions, presence, archive/pin/mute/mark-read, group/channel mutations: use
waclionly after explicit user intent. - Comparing coverage between sources: treat
wacrawlas Desktop archive truth for primary history, andwaclias linked-device/live coverage with protocol limits.
Safety
- Never send or mutate WhatsApp state unless explicitly requested.
- Prefer read-only
waclicommands for inspection: pass--read-onlyor setWACLI_READONLY=1. - Do not write into WhatsApp Desktop's app container.
- Do not edit
waclisession.dbdirectly. - Keep named
wacliaccounts isolated; do not merge stores. - Report source freshness, account name, and known gaps when answering from local stores.
Common Commands
Primary Archive
Freshness and status:
wacrawl status
wacrawl doctor
wacrawl sync
Unread triage:
wacrawl chats --limit 20
wacrawl unread --limit 20
wacrawl --json unread --limit 100
Search and slice messages:
wacrawl messages --after 2026-01-01 --limit 50
wacrawl messages --chat JID --asc --limit 100
wacrawl messages --has-media --limit 50
wacrawl --json search "query"
wacrawl search "query" --after 2026-01-01 --from-them
Archive media or backups, only when asked:
wacrawl import --copy-media
wacrawl backup status
wacrawl --sync never backup push
Alt/Live Accounts
Account discovery and read-only inspection:
wacli accounts list --json
wacli --account me auth status --read-only --json
wacli --account me chats list --read-only --json
wacli --account me messages list --read-only --json --limit 50
wacli --account me messages search --read-only --json "query"
Background live sync, only when requested. Prefer tmux for follow-mode:
wacli --account me sync --follow --events
wacli --account me sync --once --events
Media, sending, and live mutations, only when explicitly requested:
wacli --account me media download --chat JID --id MESSAGE_ID
wacli --account me send text --to JID_OR_NAME --message "message"
wacli --account me send file --to JID_OR_NAME --file ./file.jpg --caption "caption"
wacli --account me send text --to JID --reply-to MESSAGE_ID --message "reply"
Comparisons
When comparing wacrawl and wacli, compare both counts and overlap:
- message counts and date spans
- chat counts
- newest message timestamp
- overlap by
msg_id - overlap by
chat_jid + msg_idwhen JIDs are normalized enough - obvious gaps explained by linked-device history limits vs Desktop archive coverage
Repo Pointers
~/Projects/wacrawl: Desktop archive importer/search/backup.~/Projects/wacli: linked-device client/sync/send.- Global skill copies:
~/Projects/agent-scripts/skills/wacrawland~/Projects/agent-scripts/skills/wacli.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/steipete/agent-scripts/whatsapp">View whatsapp on skillZs</a>