BC bidding-tracker
军政采招投标商机管理专用工具。负责项目登记/标书采购/封标/开标/结果录入/中标统计/胜算评估,不处理合同履约、发票、报销或其他非招投标事务。
As a process C 50/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.
For the model run — optional
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
read-dotenvREADME.md:25Reads a .env filecp .env.example .env
Files scanned: 33. 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 50/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
- 75Steps. 3 steps
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1200 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 71: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 15 headings
- +3Step-by-step instructions: 3 items
- +4Has examples (13 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.
External checks
ClawHub: suspicious
This bidding tracker is not plainly malicious, but it needs Review because it handles sensitive procurement data with broad local file access and weak access boundaries in some query/script paths.
LLM: suspicious (high) · VirusTotal: · 29 May 2026