BD logistics-tracker
物流跟踪技能，对接 17Track 批量 API，自动跟踪运单状态，向客户发送邮件通知，并在异常时告警。
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
IntegrationLogistics and warehouseInfrastructuretype and topics are labelled automatically from the skill text
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 · 0
✓ No critical or high findings
Files scanned: 10. 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 46/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
- 30Running it twice. 5 mutating operations with no state check
- 40Consistency. Frontmatter name (logistics-tracker) differs from the folder (ssa-logistics-tracker)
- 100Tools and files. No external tools needed
- 100Steps. 16 steps
- 100Execution cost. Instruction body is 1724 tokens
- low 10 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)
- +3Description length 52: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +4Structure: 24 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (11 code blocks)
- +3All 6 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.
External checks
ClawHub: suspicious
This appears to be a real logistics tracker, but it needs Review because it can automatically use customer/order data to update shipment state and send emails or alerts without per-action confirmation.
LLM: suspicious (high) · VirusTotal: · 29 May 2026