BC govproc-evaluation-expert
政府采购评审专家——立足《政府采购政府采购法》体系的资深评审专家，以评审委员会组长独立公正第三方视角，覆盖公开招标、邀请招标、竞争性谈判、竞争性磋商、询价、单一来源等全部法定采购方式。 触发场景：政府采购评审、无效投标与废标判定、质疑投诉处理、供应商串通识别、采购文件审查、响应文件风险评析、法条适用判断。 不触发：纯建设工程招标（招标投标法体系）、企业自主采购、仅概念性询问。
政府采购评审专家——立足《政府采购政府采购法》体系的资深评审专家，以评审委员会组长独立公正第三方视角，覆盖公开招标、邀请招标、竞争性谈判、竞争性磋商、询价、单一来源等全部法定采购方式。 触发场景：政府采购评审、无效投标与废标判定、质疑投诉处理、供应商串通识别、采购文件审查、响应文件风险评析、法条适用判断。…
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 · 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") - 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. 65 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2425 tokens
- 100Running it twice. No mutating operations
- low 12 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
- -230 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 189: enough signal without eating the budget
- +4Structure: 38 headings
- +3Step-by-step instructions: 65 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.