BD bidding-compliance-advisor
投标人侧「投标文件合规检查」技能：对照招标文件系统检查投标文件的格式、资质、签字盖章、密封、份数、实质性响应等完整性，输出可打印打勾的四级结构化清单（🔴废标/🟡资质/🟢格式/⏰时间）与倒计时冲刺流程，提前发现废标风险；含输入预检、必查盲区强制校验、判定标尺、多轮状态管理、内置法条/案例库离线兜底。支撑招标文件合法性审查、法条问答、违规识别、异议投诉辅助。不适用于政府采购货物服务（财政部87号令体系）。触发词：检查投标文件合规性/投标前合规检查/审查招标文件合法性/投标文件废标风险自查。
投标人侧「投标文件合规检查」技能：对照招标文件系统检查投标文件的格式、资质、签字盖章、密封、份数、实质性响应等完整性，输出可打印打勾的四级结构化清单（🔴废标/🟡资质/🟢格式/⏰时间）与倒计时冲刺流程，提前发现废标风险；含输入预检、必查盲区强制校验、判定标尺、多轮状态管理、内置法条/案例库离线兜底。支撑招标文件合…
As a process D 49/100 · Unfinished process — 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: 3. 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 49/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
- 40Consistency. Frontmatter name (bidding-compliance-advisor) differs from the folder (bidding-compliance-advisor-1-3-1)
- 100Tools and files. No external tools needed
- 100Steps. 50 steps
- 100Execution cost. Instruction body is 1337 tokens
- 100Running it twice. No mutating operations
- low 15 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
- -258 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 248: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 50 items
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.