BF china-event-budget-dd
逐行审核并谈判中国境内大型线下活动、展会、展台、发布会及临时活动空间的预算或供应商报价，识别异常后给出可执行的第一口、成交红线、补件和谈判话术。适用于预算表、报价单、BOQ及结算表；不用于给承建商综合打分。
逐行审核并谈判中国境内大型线下活动、展会、展台、发布会及临时活动空间的预算或供应商报价，识别异常后给出可执行的第一口、成交红线、补件和谈判话术。适用于预算表、报价单、BOQ及结算表；不用于给承建商综合打分。
As a process F 35/100 · Will not run — References files that are not bundled: assets/offline-event-negotiation-playbook-sanitized.xlsx
The same skill appears in 1 more place: ClawHub
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: 7. 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: assets/offline-event-negotiation-playbook-sanitized.xlsx
Process rating: all ten parameters 35/100
- 0Tools and files. 1 referenced file(s) missing: assets/offline-event-negotiation-playbook-sanitized.xlsx
- 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. 24 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 651 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)
- +3Description length 103: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 10 headings
- +3Step-by-step instructions: 24 items
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.