BF esign-contract
e签宝电子签名技能 — 支持 AI 生成任意类型的合同/协议并排版为 PDF， 上传已有文件发起电子签署，返回签署链接。 触发场景：用户要求生成、起草、撰写任何类型的合同或协议（如"写个借款合同"、 "帮我拟一份保密协议"、"起草租赁合同"），或要求对已有合同文件发起签署、 查询签署进度、撤销签署、下载签署文件、验证电子签名。 触发词：写合同、生成合同、起草合同、拟合同、合同排版、合同草稿、 发起签署、电子签名、签署进度、撤销签署、下载签署文件、验签、 验证签名、签署链接、e签宝、esign 不触发场景：用户仅询问合同法律条款含义、咨询签署平台选型、或讨论与 e签宝无关的其他电子签名产品。
As a process F 35/100 · Will not run — References files that are not bundled: scripts/.venv/bin/python3, scripts/.venv/Scripts/python.exe
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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: 11. 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") - warning
missing-refreference to a missing file: scripts/.venv/bin/python3 - warning
missing-refreference to a missing file: scripts/.venv/Scripts/python.exe
Process rating: all ten parameters 35/100
- 0Tools and files. 2 referenced file(s) missing: scripts/.venv/bin/python3, scripts/.venv/Scripts/python.exe
- 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
- 100Steps. 39 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1015 tokens
- 100Running it twice. No mutating operations
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 tags): a typed call is more reliable
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
- -33 of 4 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 298: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 39 items
- +4Has examples (8 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.