WhatsApp router: history/search/read/send; wacrawl read, wacli live.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/whatsapp/SKILL.md

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with concrete, executable commands and lean organization, and it routes clearly between the two tools with strong safety guardrails. Its main gap is the absence of explicit validation/verification checkpoints for destructive operations, which caps workflow clarity.

Suggestions

Add an explicit validation checkpoint before any send/mutation, e.g. confirm the resolved JID and account with the user (or a dry-run) before executing `wacli ... send`.

Consider moving the lengthy Common Commands catalog into a reference file under ./references/ and keeping only the highest-frequency commands inline.

Tighten introductory phrasing ('Use this as the first stop...', 'Keep the source boundary sharp:') to earn back conciseness headroom.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence, organized into tight sections of routing rules and copy-paste commands with little concept explanation; minor intro phrasing like 'Keep the source boundary sharp' could be trimmed, placing it just below the lean anchor 5.	4 / 5
Actionability	It provides fully executable, copy-paste-ready bash commands across the common cases (status, unread triage, search, sync, send) with flag-level detail, matching the 'fully executable; copy-paste ready; covers common cases' anchor.	5 / 5
Workflow Clarity	Routing rules and safety guardrails are sequenced, but the skill governs destructive operations (sending, reactions, group/channel mutations) with no explicit validation or verification checkpoint before mutation, so the destructive-operations cap holds it at 3 rather than 4.	3 / 5
Progressive Disclosure	The body is well-structured into Routing, Safety, Common Commands, Comparisons, and Repo Pointers with clear one-level pointers to the wacrawl/wacli skills; no bundle files exist to verify, and the inline Common Commands section is somewhat lengthy, keeping it just below the well-split anchor 5.	4 / 5
	Total	16 / 20 Passed

Description

66%Weight 40%Scale 1-5

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 concise and names concrete actions plus a clear tool split, but it omits any 'Use when...' trigger guidance, which caps its completeness. It is specific and fairly distinct but would benefit from explicit trigger phrasing.

Suggestions

Add an explicit 'when' clause, e.g. 'Use when working with WhatsApp messages, chats, history, or sending via WhatsApp.'

Broaden trigger terms to include natural synonyms like 'messages', 'chats', and 'media' that users actually say.

Mention the destructive/sending boundary briefly in the description so the skill does not trigger for casual WhatsApp mentions.

Dimension	Reasoning	Score
Specificity	Names the WhatsApp domain and lists several concrete actions ('history/search/read/send') plus a tool split, but the action list is terse and not fully comprehensive (omits media, reactions, group mutations), fitting the 'several specific actions; minor gaps' anchor rather than the comprehensive anchor 5.	4 / 5
Completeness	It clearly states what the skill does ('WhatsApp router: history/search/read/send; wacrawl read, wacli live') but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3; it is not a 2 because the 'what' is concrete, and not a 4 because 'when' is absent rather than merely weak.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('WhatsApp', 'history', 'search', 'read', 'send') with good coverage, but misses common variations like 'messages', 'chats', or 'media' and leans on tool jargon ('wacrawl', 'wacli'), so it sits at 'good keyword coverage; a few natural terms missing' rather than the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	The WhatsApp-specific niche plus two named tools ('wacrawl', 'wacli') make it mostly distinct with only minor overlap risk against closely related messaging skills; it falls short of anchor 5 because the terse phrasing does not give fully distinct, explicit trigger phrases.	4 / 5
	Total	15 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: steipete/agent-scripts
Path: skills/whatsapp/SKILL.md
Commit: dc4f583

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.