openclaw - 💡(How to fix) Fix wacli skill: document messages show verification syntax [1 pull requests]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

The bundled wacli skill documents search, backfill, and send commands, but it does not show how to inspect or verify a single message after a send.

That gap makes it easy for agents to guess an invalid positional form such as:

wacli messages show "3EB0A9ADC55BDF882A36FF" --json --full

The real command requires both the chat JID and message ID as flags:

wacli messages show --chat "[email protected]" --id "3EB0A9ADC55BDF882A36FF" --json --full

Root Cause

The bundled wacli skill documents search, backfill, and send commands, but it does not show how to inspect or verify a single message after a send.

That gap makes it easy for agents to guess an invalid positional form such as:

wacli messages show "3EB0A9ADC55BDF882A36FF" --json --full

The real command requires both the chat JID and message ID as flags:

wacli messages show --chat "[email protected]" --id "3EB0A9ADC55BDF882A36FF" --json --full

Fix Action

Fixed

Code Example

wacli messages show "3EB0A9ADC55BDF882A36FF" --json --full

---

wacli messages show --chat "[email protected]" --id "3EB0A9ADC55BDF882A36FF" --json --full

---

wacli messages show "3EB0A9ADC55BDF882A36FF" --json --full

---

--chat and --id are required

---

wacli messages show --chat "[email protected]" --id "3EB0A9ADC55BDF882A36FF" --json --full
RAW_BUFFERClick to expand / collapse

Summary

The bundled wacli skill documents search, backfill, and send commands, but it does not show how to inspect or verify a single message after a send.

That gap makes it easy for agents to guess an invalid positional form such as:

wacli messages show "3EB0A9ADC55BDF882A36FF" --json --full

The real command requires both the chat JID and message ID as flags:

wacli messages show --chat "[email protected]" --id "3EB0A9ADC55BDF882A36FF" --json --full

Reproduction

  1. Send or locate a WhatsApp message with wacli.

  2. Try to verify it with only the message ID:

    wacli messages show "3EB0A9ADC55BDF882A36FF" --json --full
  3. The command fails with:

    --chat and --id are required
  4. Run the documented CLI shape from wacli messages show --help:

    wacli messages show --chat "[email protected]" --id "3EB0A9ADC55BDF882A36FF" --json --full
  5. The command succeeds.

Proposed fix

Add a compact verification/inspection section to skills/wacli/SKILL.md:

  • document wacli messages show --chat <jid> --id <message_id> --json --full
  • note that messages show does not accept a message ID as a positional argument
  • recommend verifying sent messages when formatting matters, especially multiline WhatsApp sends

Impact

This is a small skill-doc ergonomics fix. It reduces failed verification commands and helps agents confirm what was actually sent without guessing CLI syntax.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix wacli skill: document messages show verification syntax [1 pull requests]