SKILLEMALL.ai
GitHub ↗ RU Sign in

BB waimai

Waimai takeout decision assistant. Input cuisine, budget, location constraints, merchant candidates, or a takeout link; compare delivery fee, minimum order, discounts, meal fit, timing, and merchant risk. Safe boundary: no login, no order submission, no payment.

ClawHub Agent Skills author: haidong v1.1.0 MIT-0 5 files body ≈ 763 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process B 66/100 · Nearly there — weak spots: inputs and preconditions

ProcedureFinancePeople and hiringCommercetype 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
89/100
safety, quality, tests
Safety 60%
99
Quality 40%
75
Run on models
none yet
Process rating
B
66/100
Nearly there
Inputs and preconditions w 11
0
Failures and branches w 10
55
Tools and files w 18
60
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.
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Exfiltration intent-browser-credential-store SKILL.md:75
    Accesses a browser credential / cookie store (negated — the text forbids it)
    - store cookies or user data
    negated

Files scanned: 5. 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")

Process rating: all ten parameters 66/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 55Failures and branches. 1 branches
  • 60Tools and files. Uses tools (node) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70When it triggers. States when to use, but not when not to
  • 85Steps. 28 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 763 tokens
  • 100Running it twice. No mutating operations
  • 100Progress reporting. Reports progress

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)
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 262: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 28 items
  • +3Output format is stated explicitly
  • +4Reference files are cited in the instructions (3 of 3)

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

External checks

ClawHub: clean
This is a markdown-only takeout comparison skill that stays focused on public decision support and explicitly avoids login, checkout, payment, and data persistence.
LLM: benign (high) · VirusTotal: · 17 Jun 2026