BD buyer-hw-sw-contract-review
从买方（甲方）视角审核软硬件买卖合同（含安装部署服务）：识别不利条款、 交付与验收风险、价款与发票、质保维保、知识产权与许可、数据合规与违约 责任等，并输出分级问题清单与可谈判修订要点；强制对照甲方付款分档与 先票后款标准（货物/软硬件 13% 专票、安装部署等服务 6% 专票）。适用于 用户上传/粘贴采购合同、技术附件、SLA、订单或框架协议，或明确要求 “甲方审核”“买方视角”“软硬件买卖合同审查”。最终以带修订痕迹的 .DOCX 交付。
从买方（甲方）视角审核软硬件买卖合同（含安装部署服务）：识别不利条款、 交付与验收风险、价款与发票、质保维保、知识产权与许可、数据合规与违约 责任等，并输出分级问题清单与可谈判修订要点；强制对照甲方付款分档与 先票后款标准（货物/软硬件 13% 专票、安装部署等服务 6% 专票）。适用于…
As a process D 41/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: 6. 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 41/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 (buyer-hw-sw-contract-review) differs from the folder (buyer-side-contract-review)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 91 steps
- 100Execution cost. Instruction body is 1610 tokens
- 100Running it twice. No mutating operations
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
- +2Single-language instructions
- +3Description length 223: enough signal without eating the budget
- +4Structure: 29 headings
- +3Step-by-step instructions: 91 items
- +4Has examples (1 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.