BD 重大疾病距离模拟器
AI驱动的个性化"疾病距离"可视化工具。用户说一句"帮我看看我离重大疾病有多远"，Agent通过自然对话逐步解析用户画像（性别、年龄、地域、生活习惯、职业、家族史等），结合最新精算表+癌症统计+流行病学数据，生成"你的重大疾病还有多远"的动态时间轴报告。 输出形式：2段式教育报告 —— ①距离可视化（预警期时间轴）②身体信号+缓解行动清单。 数据底座：中国精算师协会《人身保险业重大疾病经验发生率表（2020）》+《经验生命表(2025)》+ 国家癌症中心统计 + GBD流行病学数据，通过RAG实时查询。 触发词：离重大疾病有多远、疾病距离、健康生命线、重大疾病风险、健康预警、疾病模拟器。
As a process D 49/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.
- 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-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "update_reason" - note
frontmatter-keyunknown frontmatter key "update_notes"
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 (重大疾病距离模拟器) differs from the folder (disease-distance-simulator)
- 100Tools and files. No external tools needed
- 100Steps. 30 steps
- 100Execution cost. Instruction body is 1435 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 300: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.