BC beijing-jifen-consult
北京积分落户测算与咨询：优先打开随包 HTML 可视化模拟器完成填分、解释与规划；环境无法打开时，由用户选择手动打开页面或使用文本引导模式。 触发：用户想算积分、查资格、问填法/规则、做未来规划或咨询积分落户。 未确认资料不得计算；文本模式不替代页面计算；只做本地模拟与咨询，不承诺官方结果。
北京积分落户测算与咨询：优先打开随包 HTML 可视化模拟器完成填分、解释与规划；环境无法打开时，由用户选择手动打开页面或使用文本引导模式。 触发：用户想算积分、查资格、问填法/规则、做未来规划或咨询积分落户。 未确认资料不得计算；文本模式不替代页面计算；只做本地模拟与咨询，不承诺官方结果。
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
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: 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")
Process rating: all ten parameters 57/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
- 50When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 53 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 810 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
- +2Single-language instructions
- +3Description length 146: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 53 items
- +4Reference files are cited in the instructions (2 of 2)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.