AD supplier-qualification-checker
供应商资质与履约能力核查助手。当用户（采购方/招标人/总包/甲方）给出一个公司主体，想审查供应商资质、评估履约能力、核验业绩真实性时，必须使用此SKILL：供应商审查、供应商准入核查、履约能力评估、业绩核验（自称做过的项目是否真的中过标）、分包商考察、投标单位背景核查、同类项目经验盘点、大客户与合作历史、公开涉诉与行政处罚排查。基于全网招投标数据输出报告：履约实力用中标记录证明、合作关系是真实合同关系、风险信息逐条附来源。支持单公司深度报告与两家候选供应商对比。即使用户没有提到「资质」，只要想核实一家供应商/合作方的真实履约能力，都应使用本SKILL。注意边界：若用户给出一个具体的招标项目做该不该投的决策分析，使用 zlbx-bid-decision SKILL；若用户想主动挖掘商机/销售线索，使用 zlbx-opportunity-radar SKILL；若用户只是搜索/查询招中标公告数据，使用 zlbx-bidding SKILL。
供应商资质与履约能力核查助手。当用户（采购方/招标人/总包/甲方）给出一个公司主体，想审查供应商资质、评估履约能力、核验业绩真实性时，必须使用此SKILL：供应商审查、供应商准入核查、履约能力评估、业绩核验（自称做过的项目是否真的中过标）、分包商考察、投标单位背景核查、同类项目经验盘点、大客户与合作历史、公开涉诉与行…
As a process D 46/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: 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")
Process rating: all ten parameters 46/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
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 40 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1987 tokens
- 100Running it twice. No mutating operations
- low 13 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
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +3Description length 424: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 40 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.