BD logistics
物流管理技能,提供提单生成、报关单据生成、物流跟踪等功能。支持 OKKI 客户数据同步和自动化文档处理。
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
ReferenceLogistics 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:34High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…e38+6NQZ…HmC+T7k8LvA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:109High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…pjs+EVnW…hE7+ZyY8…tdA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:139High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…uyQ+a1ko…Tn4+E0Ti6C2AA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:193High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…FSj+bWLt…2sH/Kn8E…h6w==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:392High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…pjs+EVnW…hE7+ZyY8…tdA==",
detector
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 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 (logistics) differs from the folder (ssa-logistics-manager)
- 100Tools and files. No external tools needed
- 100Steps. 8 steps
- 100Execution cost. Instruction body is 185 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 52: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- -32 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Structure: 8 headings
- +3Step-by-step instructions: 8 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.
External checks
ClawHub: suspicious
The skill is mostly aligned with logistics management, but it includes broad unauthenticated record, notification, CRM-sync, file, and subprocess capabilities that need review before use.
LLM: suspicious (high) · VirusTotal: · 29 May 2026