BF i-logistics-skill
京东国际物流数据查询技能 核心能力:支持物流轨迹追踪、国际运营指标查询、跨境小包体验指标查询三大功能模块。 1.国际物流轨迹追踪技能 功能描述:查询国际物流单号的实时物流轨迹信息。 支持的单号类型: - FS 开头的京东订单号 - JDW 开头的京东运单号 - 客户运单号 - 承运商运单号 核心能力: - 实时查询物流轨迹 2.供应链运营指标查询 功能描述:可按多种维度查询、对比分析供应链运营指标数据 支持查询如下指标: - 海外仓入库下单件数 - 海外仓入库及时率 - 头程在途体积 - 海外仓入库下单sku数 - 海外仓入库体积 - 海外仓实际出库重量 - 发货及时率 - 海外仓入库重量 - 海外仓入库单量 - 海外仓出库及时率 - 退件件量 - 海外仓目标入库件数 - 海外仓库位合格率 - 海外仓高位拣选比例 - 海外仓蓝牙拣选使用率 - 海外仓入库sku数 - ATTSCAN及时率 - 海外仓配Ascan及时率 - 海外仓24H尾单关闭率 - 头程渗透率 - 海外仓机区D类库存占比 - 海外仓实际出库体积 - 海外仓上架准确率 - 海外仓目标出库单量 - 海外仓目标出库件数 - 海外仓实际出库单量 - 海外仓配Dscan及时率 - 海外仓入库下单量 - 海外仓入库件数 - 退件上架及时率 - 海外仓仓容利用率 - 收货准确率 - 海外仓实际出库件数 - 海外仓退货验收单量 - 全程履约率(供应链) - 全程履约率(跨境小包)
As a process F 34/100 · Will not run — weak spots: steps, result and completion, when it triggers
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 Secrets in code
secret-password-literalREADME.md:41Hard-coded password / key literal (may be an example)api_key=66Pi3xz*******yzNH…cJ4
Files scanned: 3. 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 34/100
- 0Steps. Prose only: no discrete steps
- 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 (i-logistics-skill) differs from the folder (i-logisitics-skill)
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 101 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)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 625: enough signal without eating the budget
- +4Structure: 3 headings
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.