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).

62

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/wacli/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A tight, highly actionable reference: every operation has an executable command with concrete arguments, and the structure suits a simple single-file skill. The only notable issues are repetitive restatement of the do-not-use-for-chats boundary and the absence of an explicit error-recovery loop around sending.

DimensionReasoningScore

Conciseness

The body is lean and command-first, but the "not for normal user chats" point is repeated roughly four times ("Use wacli only when...", "Do NOT use wacli for normal user chats", "If the user is chatting with you...", and again in Notes), which is trimming-level redundancy.

4 / 5

Actionability

Every section provides copy-paste-ready commands with realistic arguments — `wacli send text --to "+14155551212" --message "Hello!"`, date-range message search, and concrete JID formats — fully covering the common cases.

5 / 5

Workflow Clarity

The sequence (safety → auth → sync → find chat → send) is clear with an explicit confirm-recipient-before-send checkpoint and `wacli doctor` for diagnostics, but there is no explicit fail-then-diagnose-then-retry loop for sends or backfills, leaving a minor validation gap rather than level 5's feedback loops.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, has no bundle files requiring external references, and is organized into clearly labeled sections (Safety, Auth + sync, Find chats, Send, Notes), so the simple-skill exception for a 5 applies.

5 / 5

Total

18

/

20

Passed

Description

65%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, concrete, and clearly differentiated, with a useful negative boundary. Its main weakness is the missing explicit 'Use when...' trigger clause and incomplete capability coverage, which hold specificity and completeness to the midpoint.

Suggestions

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

Broaden capability coverage in one phrase, e.g. "send text, group, and file messages" to lift specificity toward level 4.

Include one or two natural user phrasings such as "message someone on WhatsApp" to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

"Send WhatsApp messages to other people or search/sync WhatsApp history" names the domain and two concrete actions, but capabilities like file/group sending, backfill, and auth are absent, matching '1-2 concrete actions, not comprehensive' rather than the 'several specific actions' of level 4.

3 / 5

Completeness

The 'what' is clear, but the 'when' exists only as the negative exclusion "(not for normal user chats)" with no explicit 'Use when...' trigger clause, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural terms users would say — "WhatsApp", "send", "messages", "search", "sync", "history" — are present, but common variations like "message someone" or the tool name as a trigger are missing, so coverage is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

A clear niche — third-party WhatsApp messaging and history sync via the wacli CLI — with an explicit exclusion of normal user chats gives it distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

15

/

20

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.

Validation — 13 / 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
Bitterbot-AI/bitterbot-desktop
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.