SKILLEMALL.ai

BC wacli

Send third-party WhatsApp messages or sync/search WhatsApp history via wacli, not normal active chats.

ClawHub Agent Skills author: designecomsg v1.0.0 MIT-0 80 files body ≈ 400 tokens Open the sourceclawhub.ai analyzed 3 d ago

Send third-party WhatsApp messages or sync/search WhatsApp history via wacli, not normal active chats.

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

ProcedureWhatsAppFinancetype and topics are labelled automatically from the skill text
JSON
Technical rating
B
79/100
safety, quality, tests
Safety 60%
91
Quality 40%
60
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 · 9

✓ No critical or high findings

Medium and low: 9
  • low Secrets in code secret-high-entropy-token dist/call-tool-api.js:110
    High-entropy token-like string (may be an id, hash or a credential)
    async function reso…164(params) {
  • low Secrets in code secret-high-entropy-token dist/call-tool-api.js:167
    High-entropy token-like string (may be an id, hash or a credential)
    if (await reso…164({
  • low Secrets in code secret-high-entropy-token dist/session-DriaHt7V.js:11
    High-entropy token-like string (may be an id, hash or a credential)
    import { crea…ent, crea…ent, createNodeProxyAgent } from "openclaw/plugin-sdk/fetch-runtime";
  • low Secrets in code secret-high-entropy-token dist/session-DriaHt7V.js:164
    High-entropy token-like string (may be an id, hash or a credential)
    return proxyUrl ? crea…ent({ uri: proxyUrl }) : crea…ent();
  • low Secrets in code secret-high-entropy-token npm-shrinkwrap.json:122
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha512-j+gKEx…ahh+s1F2HZ+wAce…RkU++ZWQr…uoQ==",
    detector
  • low Secrets in code secret-high-entropy-token npm-shrinkwrap.json:140
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…NnL+gMRa…4kc+TTU3…RE0+dheE…XZg==",
    detector
  • low Secrets in code secret-high-entropy-token npm-shrinkwrap.json:167
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…rvP+yUUf…4tH/iSSo…tEA==",
    detector
  • low Secrets in code secret-high-entropy-token npm-shrinkwrap.json:179
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…52D+HWZh…0xI/GV7F…6Eg==",
    detector
  • low Secrets in code secret-high-entropy-token npm-shrinkwrap.json:185
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…eHn+j2Ss78lK4+G/8IYA…TAr/yAa5…lvw==",
    detector

Files scanned: 79. 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 (package)
  • 55Failures and branches. 1 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 400 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
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 102: 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
  • +3Step-by-step instructions: 18 items

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

External checks

ClawHub: suspicious
This artifact can run a full WhatsApp channel that monitors and replies to chats, while the reviewed skill presents itself as a narrower wacli helper.
LLM: suspicious (high) · 27 Aug 2026