BD yiwu-trade
义乌.Skill - 深度蒸馏义乌30年原生外贸实战沉淀，聚焦小商品出海、产业带组货、1039市场采购合规、多式联运物流、全域获客、订单成交、支付结算、财务税务、数据决策
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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
-
medium Broad scope
meta-agent-memory-dumpagents/product-agent/SOUL.mdAgent memory / workspace files bundled with the skill (3) — likely a workspace dump with personal data or tokensagents/product-agent/SOUL.md, agents/sales-agent/SOUL.md, agents/service-agent/SOUL.md
Files scanned: 60. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 85 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - note
frontmatter-keyunknown frontmatter key "triggers"
Process rating: all ten parameters 49/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
- 40Consistency. Frontmatter name (yiwu-trade) differs from the folder (yiwu-trade-skill)
- 100Tools and files. No external tools needed
- 100Steps. 10 steps
- 100Execution cost. Instruction body is 181 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 85: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -414 reference files, but SKILL.md never points to them: the model will not open them
- -32 of 2 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +4Structure: 4 headings
- +3Step-by-step instructions: 10 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 52.