SKILLEMALL.ai

BA elm

Assisted 饿了么 ordering skill that turns a natural-language request plus delivery address, item name, requirements, and budget into a ready-to-pay cart: resume from a user-authenticated Ele.me session, search nearby merchants by address, compare real payable totals with visible coupons and discounts, and add the best basket to cart before handing off for payment.

ClawHub Agent Skills author: haidong v2.0.1 MIT-0 5 files body ≈ 1 719 tokens Open the sourceclawhub.ai analyzed 2 d ago

As a process A 85/100 · Runs to the end — weak spots: running it twice

ProcedureCommerceFinancetype and topics are labelled automatically from the skill text
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
60
Run on models
none yet
Process rating
A
85/100
Runs to the end
Running it twice w 4
30
Result and completion w 14
60
When it triggers w 12
70
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 · 0

✓ No critical or high findings

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

Against the Agent Skills spec

  • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 4, column 14: description: Assisted 饿了么 ordering skill that turns a natural-language request … ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "slug"

Process rating: all ten parameters 85/100

  • 30Running it twice. 2 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 70When it triggers. States when to use, but not when not to
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. No external tools needed
  • 100Steps. 76 steps
  • 100Failures and branches. 11 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1719 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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 363: enough signal without eating the budget
  • +4Structure: 15 headings
  • +3Step-by-step instructions: 76 items
  • +3Output format is stated explicitly

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

External checks

ClawHub: suspicious
The skill is mostly transparent and consent-gated, but its listing-level description understates that it can use a logged-in Ele.me account and add items to your cart.
LLM: suspicious (medium) · VirusTotal: benign · 14 May 2026