AC gp-invalid-bid-risk-radar
政采无效投标风险雷达——专攻政府采购项目（公开招标/邀请招标/竞争性谈判/竞争性磋商/询价/单一来源）中的无效投标条款、资格性/符合性审查硬性要求、政策性合规陷阱及隐性风险点提取。触发词："政采风险检查""政府采购废标""无效投标""资格性审查""符合性审查""87号令检查""政采合规""中小企业声明函""节能清单""信用核查""政采风险雷达""这个标能不能投""帮我看看有没有坑""投标前检查""审查资格性条款""无效投标筛查"。当用户明确要求对政府采购招标文件做专项风险筛查时触发。输出结构化检查清单，便于审核人员逐项核对。不适用：工程招标（适用《招标投标法》→引导至"废标风险雷达"招投标版）、政采合同履约纠纷、质疑函/投诉书撰写、评分策略与报价建议、招标文件全文解读（非风险导向）。
政采无效投标风险雷达——专攻政府采购项目（公开招标/邀请招标/竞争性谈判/竞争性磋商/询价/单一来源）中的无效投标条款、资格性/符合性审查硬性要求、政策性合规陷阱及隐性风险点提取。触发词："政采风险检查""政府采购废标""无效投标""资格性审查""符合性审查""87号令检查""政采合规""中小企业声明函""节能清单"…
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 "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. 45 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3006 tokens
- 100Running it twice. No mutating operations
- low The response is described with custom markup (4 tags): a typed call is more reliable
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
- -229 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 10 example trigger phrases
- +3Description length 346: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 45 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.