BC rus-chn05-analyzer
中华05骨龄分析 RUS-CHN05 —— 基于慧龄云®骨龄AI检测系统,采用中华05标准RUS-CHN05计分法,分析手腕X光片,评估3~18岁儿童青少年骨骼发育程度。 当用户上传手腕/手部X光片并请求骨龄分析、骨龄评估、生长发育评估、身高预测时触发。 完整流程:注册激活→密码登录→图片上传→AI骨龄推算→生成中文诊断报告。 支持两种调用路径:轻量路径(仅骨龄识别)和完整路径(骨龄+身高预测,中华05查表法+BCPE拟合法)。
中华05骨龄分析 RUS-CHN05 —— 基于慧龄云®骨龄AI检测系统,采用中华05标准RUS-CHN05计分法,分析手腕X光片,评估3~18岁儿童青少年骨骼发育程度。 当用户上传手腕/手部X光片并请求骨龄分析、骨龄评估、生长发育评估、身高预测时触发。…
As a process C 53/100 · Has gaps — 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
read-dotenvREADME.md:28Reads a .env filecp .env.example .env
Files scanned: 8. 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") - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "triggers" - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 53/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
- 100Tools and files. No external tools needed
- 100Steps. 49 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1686 tokens
- 100Running it twice. No mutating operations
- low 10 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
- +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
- -222 emoji in the instructions: noise for the model
- +2Single-language instructions
- +3Description length 216: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 49 items
- +4Has examples (11 code blocks)
- +4Reference files are cited in the instructions (1 of 2)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.