BD helian-health-assistant
禾连健康体检预约智能助手 - 通过多轮对话引导用户完成完整的体检预约全流程，支持部署到 OpenClaw、Qoder 等智能体平台，可通过微信、钉钉、飞书等终端机器人交互使用。 触发场景： - 用户说"我想咨询体检预约"、"体检预约"、"购买体检套餐" - 用户说"查询附近可以预约体检的医院"、"帮我约个体检" - 用户说"我想做个体检"、"体检怎么预约"、"附近有哪些体检医院" - 用户表达任何体检相关的预约、购买、查询意图 核心工作流：位置获取→查询医院（含院区）→套餐列表（含详情、号源与时间段）→就诊人信息与登录→下单前校验→生成预约单→生成订单
As a process D 42/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 5775 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 42/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
- 30Running it twice. 6 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70Execution cost. Instruction body is 5775 tokens
- 100Steps. 70 steps
- 100Consistency. Name and required fields are in place
- low 11 top-level sections: this looks like several domains in one skill
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -31 of 4 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +3Description length 279: enough signal without eating the budget
- +4Structure: 29 headings
- +3Step-by-step instructions: 70 items
- +4Has examples (42 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.