AC gp-objection-reply-advisor
政采质疑答复辅助（采购人版·内部代号"政采盾牌"）——政府采购项目采购人/代理机构收到供应商质疑后，依法受理登记、判断质疑是否成立、生成纠正/驳回/切割答复、预判投诉风险与二阶博弈的内部防御助手。触发词："质疑答复""质疑函怎么回""供应商质疑怎么办""采购人答复质疑""质疑成立不成立""质疑投诉风险"。提供《质疑函》+采购文件要求起草/审核质疑答复时触发。不适用：投标人侧质疑文书起草（攻）、评标打分、合同审查、招标文件编制。
政采质疑答复辅助（采购人版·内部代号"政采盾牌"）——政府采购项目采购人/代理机构收到供应商质疑后，依法受理登记、判断质疑是否成立、生成纠正/驳回/切割答复、预判投诉风险与二阶博弈的内部防御助手。触发词："质疑答复""质疑函怎么回""供应商质疑怎么办""采购人答复质疑""质疑成立不成立""质疑投诉风险"。提供《质疑函…
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: 1. 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. 56 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1696 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 6 example trigger phrases
- +3Description length 215: enough signal without eating the budget
- +4Structure: 31 headings
- +3Step-by-step instructions: 56 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.