wacli
Send WhatsApp messages to other people or search/sync WhatsApp history via the wacli CLI (not for normal user chats).
79
Quality
72%
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 ./openclaw/skills/wacli/SKILL.mdQuality
Discovery
57%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 adequately identifies the tool (wacli CLI) and platform (WhatsApp) with reasonable specificity, creating good distinctiveness. However, it lacks an explicit 'Use when...' clause and could benefit from more natural trigger terms that users would actually say when needing this functionality.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to automate WhatsApp messaging, retrieve message history, or interact with WhatsApp programmatically.'
Include additional natural trigger terms users might say, such as 'WhatsApp automation', 'bulk messages', 'message logs', or 'WhatsApp API'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (WhatsApp) and lists some actions (send messages, search/sync history), but lacks comprehensive detail about specific capabilities like message formatting, attachment handling, or conversation management. | 2 / 3 |
Completeness | Describes what it does (send messages, search/sync history via wacli) but lacks an explicit 'Use when...' clause. The parenthetical '(not for normal user chats)' hints at when NOT to use it but doesn't clearly state when TO use it. | 2 / 3 |
Trigger Term Quality | Includes 'WhatsApp', 'messages', 'wacli', and 'history' which are relevant, but misses common variations users might say like 'text', 'chat history', 'message log', or 'WhatsApp automation'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'WhatsApp' and 'wacli CLI' creates a clear, distinct niche. The clarification '(not for normal user chats)' further distinguishes it from general chat skills, making conflicts unlikely. | 3 / 3 |
Total | 9 / 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 well-crafted, concise skill that provides clear CLI commands with realistic examples. The safety section appropriately establishes guardrails for messaging operations. The main weakness is the lack of an explicit workflow showing the confirm-before-send step integrated into the send process.
Suggestions
Add an explicit send workflow showing: 1) Confirm recipient exists via `wacli chats list`, 2) Show user the recipient + message for confirmation, 3) Only then execute `wacli send`
Consider adding error handling guidance (e.g., what to do if send fails or recipient JID is invalid)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what WhatsApp is or how CLIs work. Every line provides actionable information Claude needs. | 3 / 3 |
Actionability | Provides complete, copy-paste ready commands for every operation (auth, sync, search, send). Includes specific examples with realistic phone numbers and message text. | 3 / 3 |
Workflow Clarity | Commands are clearly listed but the send workflow lacks explicit validation steps. The 'confirm recipient + message before sending' instruction is mentioned but not integrated into a clear sequence with verification. | 2 / 3 |
Progressive Disclosure | For a simple CLI skill under 50 lines, the content is well-organized with clear sections (Safety, Auth, Find, Send, Notes). No external references needed for this scope. | 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
- trpc-group/trpc-agent-go
- Commit
8763418
- 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.