CtrlK
BlogDocsLog inGet started
Tessl Logo

wacli

Send WhatsApp messages to other people or search/sync WhatsApp history via the wacli CLI (not for normal user chats).

87

2.00x
Quality

Does it follow best practices?

Impact

96%

2.00x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A well-organized, highly actionable CLI reference with executable commands and a real confirmation checkpoint for the risky send operation. The only blemish is redundancy around the "not for normal chats" guidance.

Suggestions

State the "not for normal user chats" rule once in the intro and drop the repeated restatement in the Notes section.

Consider a one-line "Find the JID first with `wacli chats list`" pointer inside the Send section so recipients are resolved before sending.

DimensionReasoningScore

Conciseness

The command bullets are lean, but the "not for normal user chats" guidance is repeated three times (intro lines 34-36 and Notes line 71), so it could be tightened.

2 / 3

Actionability

Commands like `wacli send text --to "+14155551212" --message "…"` and `wacli messages search "query" --limit 20 --chat <jid>` are concrete, executable, and copy-paste ready.

3 / 3

Workflow Clarity

Sections are ordered (auth → sync → find → send) and the outward-facing send step has an explicit "Confirm recipient + message before sending" validation checkpoint.

3 / 3

Progressive Disclosure

Under 50 lines with no bundle files to reference, and content is cleanly sectioned (Safety, Auth+sync, Find, Backfill, Send, Notes), which satisfies the simple-skill exception.

3 / 3

Total

11

/

12

Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A tight, concrete description that names real actions and natural trigger terms within a well-bounded niche. Its main weakness is the missing positive "Use when…" clause, leaving the trigger implicit via a negative constraint.

Suggestions

Add an explicit positive trigger clause, e.g. "Use when the user asks to message a third party on WhatsApp or to search/sync WhatsApp history."

Keep the "not for normal user chats" guard but pair it with the positive trigger so the when-condition is stated affirmatively.

DimensionReasoningScore

Specificity

"Send WhatsApp messages to other people or search/sync WhatsApp history" lists multiple concrete actions (send, search, sync), matching the multiple-specific-actions anchor.

3 / 3

Completeness

The WHAT is clear, but there is no positive "Use when…" trigger clause — only the negative guard "(not for normal user chats)", so completeness is capped at 2 per the guidelines.

2 / 3

Trigger Term Quality

"WhatsApp messages" and "WhatsApp history" are exactly the natural phrasings a user would say, giving good coverage for this narrow domain.

3 / 3

Distinctiveness Conflict Risk

The wacli/WhatsApp-messaging niche is distinct, and the "not for normal user chats" guard reduces collision with the auto-routed chat path.

3 / 3

Total

11

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

13

/

16

Passed

Repository
trpc-group/trpc-agent-go
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.