BB smart-procurement-navigator-international
Smart Procurement Navigator (International Edition). A dual-track procurement system covering the full procurement lifecycle across China and international frameworks.
Smart Procurement Navigator (International Edition).
As a process B 67/100 · Nearly there — weak spots: failures and branches, execution cost, progress reporting
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Secrets in code
secret-high-entropy-tokenagent.yaml:111High-entropy token-like string (may be an id, hash or a credential)- ZC04…tor
-
low Secrets in code
secret-high-entropy-tokenagent.yaml:122High-entropy token-like string (may be an id, hash or a credential)- ZC15…tor
-
low Secrets in code
secret-high-entropy-tokenskills/procurement_skills.yaml:20High-entropy token-like string (may be an id, hash or a credential)- id: ZC04…tor
-
low Secrets in code
secret-high-entropy-tokenskills/procurement_skills.yaml:86High-entropy token-like string (may be an id, hash or a credential)- id: ZC15…tor
Files scanned: 22. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: All mapping items must start at the same column at line 7, column 1: contact: "email: yinjianheng@foxmail.com / wechat: YJH-yinjianheng" email: yinjianheng@foxmail.com ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 21211 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "language" - note
frontmatter-keyunknown frontmatter key "contact"
Process rating: all ten parameters 67/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 10Execution cost. Instruction body is 21211 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 60Steps. 229 steps, 9 vague phrases
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 32 top-level sections: this looks like several domains in one skill
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)
- +2Single-language instructions
- +3Description length 167: enough signal without eating the budget
- +4Structure: 115 headings
- +3Step-by-step instructions: 229 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 54.
External checks
ClawHub: clean
This is a disclosed procurement-document assistant with expected handling of tender files and bid materials, with no executable payloads or hidden data-transfer behavior found.
LLM: benign (high) · VirusTotal: · 10 Jul 2026