多平台快递查询

v1.0.0

根据快递单号识别承运商，查询并解析物流轨迹，判断异常状态，提供准确的物流状况和处理建议。

⭐ 0· 135·1 current·1 all-time

by@zhili007

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for zhili007/express-query.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "多平台快递查询" (zhili007/express-query) from ClawHub.
Skill page: https://clawhub.ai/zhili007/express-query
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install express-query

ClawHub CLI

Package manager switcher

npx clawhub@latest install express-query

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Benign

high confidence

✓

Purpose & Capability

Name/description match the included scripts, rules, and data (identify.py, query.py, carriers references, official_sources). The code only builds identification and query plans/URLs; nothing requires unrelated credentials or system access.

ℹ

Instruction Scope

Runtime instructions stay within tracking: identify courier, open aggregator/official pages with browser/web_fetch, parse timeline, and apply anomaly rules. Note: the SKILL asks the agent to use browser/web_fetch and to prompt the user if verification is required (e.g., 'need phone last 4 digits', 'need login', 'captcha'), which is expected for some official queries but is a privacy-sensitive action — the skill itself does not instruct reading local files or env vars.

✓

Install Mechanism

No install spec; instruction-only plus included Python scripts. No downloads, package installs, or archive extraction are present.

ℹ

Credentials

The skill declares no required env vars or credentials (appropriate). It may ask the user for verification details (phone tail digits or login) as part of using official channels — this is plausible but privacy-sensitive; the skill does not request unrelated secrets or system credentials.

✓

Persistence & Privilege

always is false and there is no installation step altering agent/system config or requesting permanent presence. The default autonomous invocation setting is unchanged (normal).

Assessment

This skill appears to do what it says: identify carriers, build query plans, parse timelines, and apply anomaly rules. Before installing: (1) Note it uses browser/web_fetch to open aggregator or official pages — if you allow an agent to use a browser tool it will visit web pages; do not allow the agent to enter your full login credentials. (2) The skill may ask you to provide verification details (e.g., phone last 4 digits) to access some official queries — only share minimal, non-sensitive info you are comfortable disclosing. (3) There are no hidden network endpoints or required environment secrets in the package, but if you connect this skill to tools that can submit forms or sign in, review those tool permissions. If you want extra assurance, run the Python scripts locally to inspect behavior before granting the agent browser/web_fetch capabilities.

Like a lobster shell, security has layers — review code before you run it.

latestvk978d5sjxjqr9bmzvy2pw2ka1d838y1m

135downloads

0stars

1versions

Updated 1mo ago

v1.0.0

MIT-0

快递物流查询 Skill

目标

根据用户提供的快递单号，查询物流轨迹，识别承运商，判断物流状态，识别异常，并给出建议。

使用场景

用户说帮我查一下快递用户说快递到哪了用户说物流怎么还没更新

执行流程

第一步：识别承运商

运行 scripts/identify.py 识别快递公司或使用正则匹配，详见 references/carriers.md

第二步：查询物流

推荐路径按优先级：

第一选择是快递100聚合查询，打开浏览器访问 https://www.kuaidi100.com 输入单号查询

第二选择是官网查询，直接访问对应快递公司官网

第三选择是浏览器自动化，如果以上都失败，用 browser 工具打开查询页面

第三步：解析轨迹

从查询结果网页中提取以下信息：

第一步是找到物流轨迹区域，通常在页面中间位置

第二步是提取时间，格式为 YYYY.MM.DD HH:MM

第三步是提取地点和状态，描述中包含地点和状态信息

第四步是按时间倒序排列，最新的在前

第四步：异常判断

根据以下规则判断异常情况：

停滞规则是最新一条轨迹距离今天超过3天

滞留规则是轨迹中出现同一站点重复超过2次

派送异常规则是状态包含派送中且超过2天

签收未收到规则是状态显示已签收但用户说没收到

退件规则是状态包含退件、退回、拒收

第五步：生成回复

按以下结构输出：

第一行是快递公司和单号，用中文冒号分隔

第二行是状态，运输中或派送中或已签收

第三行是最新轨迹，时间地点状态用空格分隔

第四部分是物流时间线，用数字编号，每条一行

第五部分是异常判断，有问题时写具体问题，没问题时写正常

第六部分是建议动作，根据状态给出相应建议

回答原则

只信官方来源，优先使用快递100或官网数据

不编造轨迹，查不到就是查不到，不要编造

诚实告知，查不到、异常、无法判断都要诚实说

给出建议，异常时给用户具体的处理建议

技术实现

识别算法

详见 references/carriers.md

核心逻辑是步骤一前缀匹配、步骤二长度特征匹配、步骤三兜底判断

查询工具

browser 用于打开快递100或官网查询页面，是主要工具

web_fetch 用于抓取查询结果页面，是备用工具

脚本

scripts/identify.py 是单号识别脚本，测试命令 python3 identify.py SF1234567890

scripts/query.py 是查询主脚本，测试命令 python3 query.py 单号

测试样例

测试单号一：SF1234567890，预期识别为顺丰速运

测试单号二：JT12345678901，预期识别为极兔速递

测试单号三：JD0012345678901，预期识别为京东物流

测试单号四：781234567890，预期识别为中通快递

异常判断详细规则

规则一：停滞

判断方法是最新轨迹时间距离今天超过3天

处理方式是建议联系发件人核实或联系快递公司客服

规则二：滞留

判断方法是同一站点出现3次以上

处理方式是建议直接联系快递公司客服催办

规则三：派送中超时

判断方法是状态为派送中且超过48小时

处理方式是建议联系快递员或客服询问情况

规则四：已签收未收到

判断方法是状态显示已签收但用户说没收到

处理方式是建议先确认家人同事是否代收，然后联系快递员或客服投诉

规则五：退件

判断方法是状态包含退件、退回、拒收

处理方式是建议联系发件人确认原因

输出模板

标准输出格式如下：

快递公司：XXX 单号：XXX 状态：运输中/派送中/已签收/异常

最新轨迹： 2025.11.20 14:39 地点 - 状态描述

物流时间线：

2025.11.20 14:39 地点 - 状态描述
2025.11.20 12:26 地点 - 状态描述
2025.11.19 10:00 地点 - 状态描述

异常判断：正常 / 停滞3天 / 派送超时 / 签收未收到

建议动作：暂无 / 请联系客服催办 / 请确认是否代收 / 请联系发件人核实

版本：v0.3 最后更新：2026-03-20

Comments

Loading comments...