BC bid-post-award-compliance-reviewer
标后履约合规审查官（Post-Award Compliance Reviewer）。面向工程建设项目与政府采购项目的中标后全生命周期（合同签订→履约→变更→索赔→验收→结算→质保→审计→争议），通过招标/投标/合同/变更/验收等文件的贯穿式比对，做变更合规评估、合同一致性比对、关键人员履约核查、转包/分包/挂靠识别、工程量与造价偏差监测、验收合规审查、索赔合规审查、阈值红线监控与审计应对。内置招投标法体系与政府采购法体系双轨知识基座、2024–2026新规与阈值红线表，每个风险点给出合规/灰区/违规明确判定并附证据链。触发词：标后履约、履约合规、变更合规评估、合同一致性比对、关键人员履约、项目经理到岗、转包分包挂靠识别、工程量偏差、验收合规、索赔合规、结算审计、阈值监控、超概算、未批先建、补充合同超10%、中标后合同怎么签、履约风险审查。当用户需要在中标后做合规比对、阈值管控、人员核查、转包识别或审计应对时使用。
标后履约合规审查官（Post-Award Compliance…
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: 12. 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")
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. 39 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1317 tokens
- 100Running it twice. No mutating operations
- low 10 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
- +1No license
- +2Single-language instructions
- +3Description length 412: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 39 items
- +4Reference files are cited in the instructions (8 of 8)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.