BF gp-review-expert-caselaw
评审专家"判例法"即时指引——评审委员会（组长/成员）在评审环节出现争议（如对"★"条款认定、异常低价判断、实质性参数/品牌认定）时，即时查询全国5万+投诉处理决定中同类问题的财政部门判定规则，告知"若如此认定、未来被投诉后通常如何纠偏"，并提示是否启动澄清程序要求供应商提供客观佐证。触发词："专家争议""★条款怎么认定""异常低价怎么评""成本认定""品牌认定""参数倾向性""需要澄清吗""评审判例法""这类参数凭承诺函能过吗""客观参数佐证"。不适用：投标人侧投诉预判（路由至投诉胜诉率预判）、采购人/代理机构被质疑后的防御答复（路由至政采质疑类案智库/政采盾牌）、工程招投标评审（法域不同）。
评审专家"判例法"即时指引——评审委员会（组长/成员）在评审环节出现争议（如对"★"条款认定、异常低价判断、实质性参数/品牌认定）时，即时查询全国5万+投诉处理决定中同类问题的财政部门判定规则，告知"若如此认定、未来被投诉后通常如何纠偏"，并提示是否启动澄清程序要求供应商提供客观佐证。触发词："专家争议""★条款怎么…
As a process F 35/100 · Will not run — References files that are not bundled: references/review-dispute-taxonomy.md, references/expert-guidance-methodology.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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: 0. 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
missing-refreference to a missing file: references/review-dispute-taxonomy.md - warning
missing-refreference to a missing file: references/expert-guidance-methodology.md - note
frontmatter-keyunknown frontmatter key "display_name" - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 35/100
- 0Tools and files. 2 referenced file(s) missing: references/review-dispute-taxonomy.md, references/expert-guidance-methodology.md
- 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
- 100Steps. 56 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1521 tokens
- 100Running it twice. No mutating operations
- 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
- +1No license
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +3Description length 301: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 56 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.