BC gp-objection-caselaw
政采质疑类案智库（判例法辅助）——政府采购项目采购人/代理机构收到供应商质疑后，输入质疑核心诉求，从「政府采购投诉AI知识库」（5万+真实投诉处理决定）匹配全国高度相似的类案，比对"质疑成立"与"质疑不成立"的事实依据与法律适用，识别答复薄弱环节与被推翻风险（如仅以书面承诺函回应客观事实类★参数质疑），辅助撰写合规的质疑答复函。触发词："类案匹配""相似投诉处理决定""判例法参考""质疑答复参考案例""同类质疑怎么判""找相似案例""这个质疑成立吗 案例"。不适用：投标人侧质疑文书起草（攻）、评标打分、合同审查、招标文件编制；工程招投标异议（应路由至招投标异议答复辅助）。 Scope: PRC Government Procurement Law (MoF Order No.94) only; Chinese is the statutory working language, not an un-opted-in language forcing.
政采质疑类案智库（判例法辅助）——政府采购项目采购人/代理机构收到供应商质疑后，输入质疑核心诉求，从「政府采购投诉AI知识库」（5万+真实投诉处理决定）匹配全国高度相似的类案，比对"质疑成立"与"质疑不成立"的事实依据与法律适用，识别答复薄弱环节与被推翻风险（如仅以书面承诺函回应客观事实类★参数质疑），辅助撰写合规的…
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: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 3, column 14: description: 政采质疑类案智库（判例法辅助）——政府采购项目采购人/代理机构收到供应商质疑后，输入质疑核心诉求，从「政府采购投诉AI知识库」（5万… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "display_name" - 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. 63 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2030 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 5 example trigger phrases
- +3Description length 431: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 63 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (2 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.