wacli
Send WhatsApp messages to other people or search/sync WhatsApp history via the wacli CLI (not for normal user chats).
84
80%
Does it follow best practices?
Impact
96%
2.00xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/wacli/SKILL.mdQuality
Discovery
72%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is reasonably effective with good trigger terms and a clearly distinct niche around WhatsApp CLI operations. Its main weaknesses are the lack of an explicit 'Use when...' clause and somewhat limited enumeration of specific capabilities beyond send/search/sync.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to send a WhatsApp message, look up WhatsApp conversation history, or sync WhatsApp data.'
Expand the list of specific actions to be more comprehensive, e.g., 'Send WhatsApp messages to contacts or groups, search conversation history by keyword or date, sync message archives via the wacli CLI.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (WhatsApp) and some actions (send messages, search/sync history), but doesn't list comprehensive specific actions like formatting options, group messaging, media handling, etc. | 2 / 3 |
Completeness | Describes what it does (send messages, search/sync history via wacli) and includes a negative scope clarification ('not for normal user chats'), but lacks an explicit 'Use when...' clause with trigger guidance, which caps this at 2. | 2 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'WhatsApp', 'messages', 'search', 'sync', 'history', and the tool name 'wacli'. Users would naturally say 'send a WhatsApp message' or 'search WhatsApp history'. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — WhatsApp messaging via a specific CLI tool (wacli). The clarification 'not for normal user chats' further narrows scope and reduces conflict risk with general chat or messaging skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, concise skill that provides fully actionable CLI commands with clear scope boundaries and safety guardrails. Its main weakness is the lack of an explicit sequenced workflow with validation checkpoints for the send operation, which is a potentially destructive action involving messaging third parties. The organization and token efficiency are excellent.
Suggestions
Add an explicit step-by-step send workflow: 1) Look up recipient with `wacli chats list`, 2) Confirm recipient + message with user, 3) Send, 4) Verify delivery status—this would add a feedback loop for the most critical operation.
Remove the duplicate note about wacli not being needed for routine user chats (appears in both the intro and Notes section) to tighten further.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. Every section serves a purpose—scope boundaries, safety rules, and concrete commands. The repeated note about not using wacli for normal chats is slightly redundant (appears in intro and Notes) but overall token usage is excellent. | 3 / 3 |
Actionability | Every command is fully concrete and copy-paste ready with real flags, example arguments, and realistic values (phone numbers, JIDs, date ranges). No pseudocode or vague descriptions. | 3 / 3 |
Workflow Clarity | The safety section establishes a confirm-before-send checkpoint, which is good. However, the commands are listed as a reference catalog rather than a sequenced workflow. For a destructive operation like sending messages to third parties, an explicit step-by-step flow (lookup recipient → confirm → send → verify) with validation/feedback loops would strengthen this. | 2 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized into clearly labeled sections (Safety, Auth, Find, Send, Notes) that are easy to scan and navigate. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Repository
- qsimeon/openclaw-engaging
- Commit
4467e04
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.