ClawHub

Wacli Gilles

v1.0.0

Send WhatsApp messages to other people or search/sync WhatsApp history via the wacli CLI (not for normal user chats).

⭐ 0· 277·3 current·3 all-time
by@gillescv·duplicate of @mohdalhashemi98-hue/mh-wacli

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for gillescv/wacli-gilles.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Wacli Gilles" (gillescv/wacli-gilles) from ClawHub.
Skill page: https://clawhub.ai/gillescv/wacli-gilles
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required binaries: wacli
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install wacli-gilles

ClawHub CLI

Package manager switcher

npx clawhub@latest install wacli-gilles
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The skill is an instruction-only wrapper around the wacli CLI. The registry requires the wacli binary (and provides plausible install options via a brew formula and a Go module), which directly matches the described purpose of sending and searching WhatsApp messages.
ℹ
Instruction Scope
SKILL.md stays on-topic: it only instructs use of wacli commands (auth, sync, search, send, backfill). It does reference the local store directory (~/.wacli) and recommends using --json for parsing output; these are expected for a CLI-based WhatsApp tool but imply local persisted session data and phone access via QR auth. The instructions do not ask the agent to read unrelated files or environment variables.
✓
Install Mechanism
Install options are a brew formula (steipete/tap/wacli) and a Go module from GitHub (github.com/steipete/wacli). Both are typical distribution methods for this project and are proportionate. As with any third-party binary, users should verify the upstream project and tap/module before installing.
ℹ
Credentials
The skill declares no required environment variables or config paths, which is consistent with the CLI-centric design. SKILL.md does mention the store directory (~/.wacli) but the registry metadata does not list any required config paths — a minor mismatch worth noting because the tool will persist session data locally and may create files under the user's home directory.
✓
Persistence & Privilege
The skill does not request always:true and is user-invocable. It does not request elevated or cross-skill privileges. Normal autonomous invocation is allowed by platform default but the skill itself does not demand permanent presence or extra privileges.
Assessment
This skill is a thin wrapper around the wacli command-line tool and appears coherent with that purpose. Before installing, verify the upstream project (https://wacli.sh and the GitHub repo) and the brew tap/module authors to ensure you trust the binary. Be aware that wacli will: (1) require QR login and sync with your phone, (2) persist session data under ~/.wacli by default, and (3) be capable of sending messages to third parties — so only allow the agent to use it when the user explicitly requests messaging others. If you want tighter control, review the wacli source yourself or restrict the agent's ability to call the skill autonomously.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

📱 Clawdis
Binswacli

Install

Install wacli (brew)
Bins: wacli
brew install steipete/tap/wacli
Install wacli (go)
Bins: wacli
go install github.com/steipete/wacli/cmd/wacli@latest
latestvk97ey0aghtb7a3se1xty2yf45n83mxrs
277downloads
0stars
1versions
Updated 1mo ago
v1.0.0
MIT-0
@gillescv
latest
Download

wacli

Use wacli only when the user explicitly asks you to message someone else on WhatsApp or when they ask to sync/search WhatsApp history. Do NOT use wacli for normal user chats; OpenClaw routes WhatsApp conversations automatically. If the user is chatting with you on WhatsApp, you should not reach for this tool unless they ask you to contact a third party.

Safety

  • Require explicit recipient + message text.
  • Confirm recipient + message before sending.
  • If anything is ambiguous, ask a clarifying question.

Auth + sync

  • wacli auth (QR login + initial sync)
  • wacli sync --follow (continuous sync)
  • wacli doctor

Find chats + messages

  • wacli chats list --limit 20 --query "name or number"
  • wacli messages search "query" --limit 20 --chat <jid>
  • wacli messages search "invoice" --after 2025-01-01 --before 2025-12-31

History backfill

  • wacli history backfill --chat <jid> --requests 2 --count 50

Send

  • Text: wacli send text --to "+14155551212" --message "Hello! Are you free at 3pm?"
  • Group: wacli send text --to "1234567890-123456789@g.us" --message "Running 5 min late."
  • File: wacli send file --to "+14155551212" --file /path/agenda.pdf --caption "Agenda"

Notes

  • Store dir: ~/.wacli (override with --store).
  • Use --json for machine-readable output when parsing.
  • Backfill requires your phone online; results are best-effort.
  • WhatsApp CLI is not needed for routine user chats; it’s for messaging other people.
  • JIDs: direct chats look like <number>@s.whatsapp.net; groups look like <id>@g.us (use wacli chats list to find).

Comments

Loading comments...