SKILLEMALL.ai
RU Sign in

BC wacli

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

ClawHub Agent Skills author: rafay0313 v1.0.0 2 files body ≈ 398 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

As a process C 61/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency

IntegrationWhatsAppInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
64
Run on models
none yet
Process rating
C
61/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: wacli (ClawHub)

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 61/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 5 mutating operations with no state check
  • 40Consistency. Frontmatter name (wacli) differs from the folder (tt)
  • 60Failures and branches. 2 branches
  • 100Tools and files. No external tools needed
  • 100Steps. 18 steps
  • 100When it triggers. States when to use and when not to
  • 100Execution cost. Instruction body is 398 tokens
  • low The response is described with custom markup (3 tags): a typed call is more reliable

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +3Description length 117: 120–800 characters recommended
  • +4Structure: 1 headings, hard to scan
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Step-by-step instructions: 18 items

Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.

External checks

ClawHub: clean
This skill transparently enables WhatsApp sending and history search through wacli, with user confirmation required before sending.
LLM: benign (high) · VirusTotal: suspicious · 10 Sept 2026