BC upwork-bid-decision-assistant
分析 Upwork 工作是否值得投标、是否应使用 Boost、是否应接受邀请，以及客户与项目是否存在风险。适用于用户提供 Upwork 工作链接、页面截图、职位描述、客户历史、付款与评分、hire rate、total spent、proposal/interview/invite 数量、发布时间和 last viewed 等信息时。先提取证据，再综合判断；信息不足但足以判断时直接给结论，关键数据缺失时只追问会改变结论的字段。不要用于承诺接单结果、规避平台规则、操纵计时或基于国籍作歧视性判断。
分析 Upwork 工作是否值得投标、是否应使用 Boost、是否应接受邀请，以及客户与项目是否存在风险。适用于用户提供 Upwork 工作链接、页面截图、职位描述、客户历史、付款与评分、hire rate、total spent、proposal/interview/invite 数量、发布时间和 last…
As a process C 53/100 · Has gaps — 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: 21. 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 53/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
- 100Tools and files. No external tools needed
- 100Steps. 107 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 975 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
- +4No input/output examples
- +2Single-language instructions
- +3Description length 249: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 107 items
- +4Reference files are cited in the instructions (7 of 9)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.