SKILLEMALL.ai

BD Meituan Bike

美团单车(原摩拜单车)出行助手:扫码用车流程、计费结构解读、骑行卡划算性测算、还车与调度费避坑。Meituan Bike (formerly Mobike) assistant: rental flow, pricing structure, ride-pass cost analysis, and parking-fee pitfalls for China's leading bike-sharing service.

ClawHub Hermes author: zhangifonly v1.1.0 MIT-0 2 files body ≈ 190 tokens Open the sourceclawhub.ai analyzed 4 d ago

As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

AnalyzerInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
83/100
safety, quality, tests
Safety 60%
100
Quality 40%
57
Run on models
none yet
Process rating
D
49/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
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. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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 name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-long-hermes description is 213 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill

Process rating: all ten parameters 49/100

  • 0Result and completion. Does not say what the result is
  • 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
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (Meituan Bike) differs from the folder (meituan-bike)
  • 100Tools and files. No external tools needed
  • 100Steps. 15 steps
  • 100Execution cost. Instruction body is 190 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)
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 213: enough signal without eating the budget
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 15 items

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

External checks

ClawHub: clean
This is a simple informational Meituan Bike assistant with no code execution, credential handling, persistence, or hidden high-impact behavior.
LLM: benign (high) · VirusTotal: · 11 Jul 2026