Content
82%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A tight, highly actionable command reference that respects the token budget and gives copy-paste-ready examples for every operation. The main weaknesses are cosmetic: a thrice-repeated routing caveat, section labels that aren't actual markdown headers, and the absence of error-recovery guidance for failed sends or stalled syncs.
Suggestions
State the 'not for normal user chats' routing rule once (the opening paragraph) and delete the duplicate in Notes to reclaim tokens.
Convert section labels (Safety, Auth + sync, Find chats + messages, History backfill, Send, Notes) into markdown headers (## Safety) so the structure renders and navigates properly.
Add a brief error-recovery loop, e.g. 'If a send fails or sync stalls: run wacli doctor, re-check auth, then retry once' — this would lift workflow clarity to the feedback-loop anchor.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and command-dense with no concept explanations Claude already knows, but the routing caveat 'not for normal user chats' is stated three times ("Do NOT use wacli for normal user chats", "If the user is chatting with you on WhatsApp...", and the Notes bullet "WhatsApp CLI is not needed for routine user chats"), which is a minor instance of repetition that could be trimmed. Not 5 because of this redundancy; well above 3 because everything else earns its place. | 4 / 5 |
Actionability | Every section gives copy-paste-ready commands with real flags and example values — "wacli send text --to "+14155551212" --message "..."", "wacli messages search "invoice" --after 2025-01-01 --before 2025-12-31", "wacli history backfill --chat <jid> --requests 2 --count 50" — covering the common cases (text, group, file, dated search, backfill). Fully executable with no pseudocode. | 5 / 5 |
Workflow Clarity | Sections sequence the workflow logically (auth → sync → find chats → backfill → send) and include an explicit pre-send validation checkpoint ("Confirm recipient + message before sending", "If anything is ambiguous, ask a clarifying question") plus "wacli doctor" for diagnostics. Not 5: there is no error-recovery feedback loop (e.g. what to do when send fails or sync stalls) — the cap-3 rule for destructive/batch ops is not triggered since a validation step is present and sends are single, confirm-guarded actions. | 4 / 5 |
Progressive Disclosure | At ~45 lines with no external references needed, the skill qualifies for the simple-skill exception, and content is appropriately split into labeled sections (Safety, Auth + sync, Find chats + messages, History backfill, Send, Notes). Not 5: those section labels are bare text lines rather than markdown headers, so the structure is not as clearly signaled or navigable as a well-headered layout. | 4 / 5 |
Total | 17 / 20 Passed |