SKILLEMALL.ai
GitHub ↗ RU Sign in

BF whatsapp-style-guide-free

WhatsApp消息格式化规范指南,涵盖核心语法规则与常见模式速查

ClawHub Agent Skills author: 天轰穿 v1.0.0 MIT-0 2 files body ≈ 2 044 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

WhatsApp消息格式化规范指南,涵盖核心语法规则与常见模式速查

As a process F 33/100 · Will not run — References files that are not bundled: url

IntegrationWhatsAppSoftware developmentAI and agentstype 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
82/100
safety, quality, tests
Safety 60%
100
Quality 40%
56
Run on models
none yet
Process rating
F
33/100
Will not run
References files that are not bundled: url
Tools and files w 18
0
Result and completion w 14
0
When it triggers w 12
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
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-short description under 40 chars: too little signal for triggering
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: url

Process rating: all ten parameters 33/100

Will not run. References files that are not bundled: url
  • 0Tools and files. 1 referenced file(s) missing: url
  • 0Result and completion. Does not say what the result is
  • 0When it triggers. No condition that starts the skill
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 100Steps. 28 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2044 tokens
  • 100Running it twice. No mutating operations

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 33: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Structure: 43 headings
  • +3Step-by-step instructions: 28 items
  • +4Has examples (15 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
This looks like a WhatsApp formatting guide, but it asks for command execution and contains unrelated or inconsistent capability text that should be reviewed before use.
LLM: suspicious (high) · 22 Jul 2026