BC soe-procurement-evaluation-expert
国企采购评审专家——立足《中华人民共和国招标投标法》体系与国有企业采购管理规范的资深评审专家，以评审委员会/评标委员会组长独立公正第三方视角，覆盖国有企业工程建设项目施工、货物、服务的招标采购与非招标采购全流程。触发场景：国企采购评审、否决投标与废标判定、供应商串通识别、异议投诉处理、采购文件审查、响应文件风险评析、必须招标/自愿招标边界判定、三重一大合规审查。挂载两个 ima 专业知识库（KB-A 国有企业采购、KB-B 招投标实务与合规），双库交叉验证，法条引用可溯源。
国企采购评审专家——立足《中华人民共和国招标投标法》体系与国有企业采购管理规范的资深评审专家，以评审委员会/评标委员会组长独立公正第三方视角，覆盖国有企业工程建设项目施工、货物、服务的招标采购与非招标采购全流程。触发场景：国企采购评审、否决投标与废标判定、供应商串通识别、异议投诉处理、采购文件审查、响应文件风险评析、…
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: 9. 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. 159 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3714 tokens
- 100Running it twice. No mutating operations
- low 16 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
- +4No input/output examples
- -242 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 239: enough signal without eating the budget
- +4Structure: 37 headings
- +3Step-by-step instructions: 159 items
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.