← 返回 Skills 市场
331
总下载
0
收藏
2
当前安装
4
版本数
在 OpenClaw 中安装
/install kuaidi-query
功能描述
Query logistics tracking information via Track123 API
使用说明 (SKILL.md)
快递查询 (kuaidi-query)
快速查询国内国际主流快递公司的物流信息。基于 Track123 API,支持 200+ 家快递公司。
快速开始
# 1. 配置 API Key
cp config.example.json config.json
# 编辑 config.json,填入你的 Track123 API Key
# 2. 查询快递
node scripts/query.js sf SF1234567890123
支持的快递公司
国内快递
顺丰速运、圆通速递、中通快递、韵达速递、申通快递、邮政 EMS、京东快递、极兔速递、菜鸟直送等。
国际快递
DHL、FedEx、UPS、TNT、顺丰国际等。
使用方法
基本查询
node scripts/query.js \x3C快递公司代码> \x3C运单号>
自动识别
node scripts/query.js auto \x3C运单号>
查看所有支持的快递公司
node scripts/query.js carriers
命令选项
| 选项 | 说明 | 默认值 |
|---|---|---|
| `--format \x3Ctext | json | compact>` |
--cache |
使用缓存 (1 小时内) | true |
--no-cache |
强制刷新缓存 | false |
| `--lang \x3Czh | en | ru>` |
--debug |
开启调试模式 | false |
快递公司代码
| 代码 | 快递公司 | 代码 | 快递公司 |
|---|---|---|---|
sf |
顺丰速运 | yto |
圆通速递 |
zto |
中通快递 | yunda |
韵达速递 |
sto |
申通快递 | ems |
邮政 EMS |
jd |
京东快递 | jt |
极兔速递 |
dhl |
DHL | fedex |
FedEx |
ups |
UPS | tnt |
TNT |
auto |
自动识别 | carriers |
显示所有快递公司 |
输出示例
文本格式
node scripts/query.js sf SF1234567890123
输出:
📦 顺丰速运 SF Express
运单号:SF1234567890123
状态:运输中
🚚 物流轨迹:
2024-03-14 08:30:00 已发出,下一站【上海转运中心】
📍 北京转运中心
2024-03-13 22:15:00 已到达【北京转运中心】
📍 北京转运中心
JSON 格式
node scripts/query.js sf SF1234567890123 --format json
输出:
{
"tracking_number": "SF1234567890123",
"carrier": {
"code": "sf",
"name": "顺丰速运",
"nameEn": "SF Express"
},
"status": "002",
"status_description": "运输中",
"origin": "北京市朝阳区",
"destination": "上海市浦东新区",
"weight": null,
"signed_by": null,
"tracks": [
{
"checkpoint_time": "2024-03-14 08:30:00",
"tracking_detail": "已发出,下一站【上海转运中心]",
"location": "北京转运中心"
},
{
"checkpoint_time": "2024-03-13 22:15:00",
"tracking_detail": "已到达【北京转运中心]",
"location": "北京转运中心"
}
]
}
Compact 格式(简洁模式)
node scripts/query.js sf SF1234567890123 --format compact
输出:
📦 SF1234567890123 (顺丰速运) - 运输中
最新:2024-03-14 08:30:00 已发出,下一站【上海转运中心】
配置
1. 复制配置模板
cp config.example.json config.json
2. 填写 API Key
在 Track123 注册账号获取 API Key。
⚠️ 重要:下面的示例值(your_api_key_here)需要替换为你真实的 API Key!
{
"track123": {
"app_key": "your_api_key_here",
"api_secret": "your_api_key_here"
},
"cache_duration": 3600000,
"debug": false
}
3. 完整配置示例
# 复制配置模板
cp config.example.json config.json
# 编辑 config.json,填入你的 API Key
# 例如(❌ 下面的值只是示例格式,不是真实可用的 API Key):
# {
# "track123": {
# "app_key": "your_real_api_key",
# "api_secret": "your_real_api_key"
# },
# "cache_duration": 3600000,
# "debug": false
# }
# 验证配置
node scripts/query.js carriers
4. 安全提示
⚠️ API Key 是私密凭证,不应该公开分享!
- 不要将
config.json提交到公共仓库 - 使用
.gitignore排除config.json - 如果 API Key 泄露,请立即在 Track123 控制台重置
参考文档
注意事项
- API 配额: 免费额度 100 次/天
- 缓存机制: 相同运单号 1 小时内自动缓存
- 错误处理: 查询失败会显示具体原因
- 隐私保护: 不要将
config.json提交到公共仓库
错误码
| 错误码 | 说明 |
|---|---|
400 |
请求参数错误 |
401 |
API Key 无效 |
429 |
请求过于频繁 |
500 |
服务器错误 |
版本: 1.0.1
作者: josh
安全使用建议
This skill appears to do what it says (query Track123) but the repository includes a populated config.json with an API key-like value — contradicting its own advice to create your own config and keep keys private. Before installing or running: (1) Treat the bundled config.json as potentially sensitive/active and do not assume it is a harmless placeholder. Replace it with your own Track123 credentials (from a secure location) or remove it. (2) Do not commit any API keys to public repos. (3) Review the script's network calls (it posts to api.track123.com) and run in a sandbox if you are concerned about using an unknown credential. (4) Note documentation/code mismatches (app_key vs api_secret, v2.1 vs v2); verify behavior against Track123 documentation or test with your own key. If you need high assurance that the included key is inert, ask the publisher to confirm it is a dummy key and to remove it from the package.
功能分析
Type: OpenClaw Skill
Name: kuaidi-query
Version: 1.0.3
The skill bundle is a legitimate utility for querying logistics tracking information via the Track123 API. Analysis of `scripts/query.js` shows that it correctly implements API calls to `api.track123.com` for carrier detection and tracking queries, with no evidence of data exfiltration, unauthorized file access, or malicious command execution. Although `config.json` contains a hardcoded API key and `package-lock.json` references a non-existent version of `axios` (1.13.6), these appear to be development artifacts or generation errors rather than intentional indicators of malice.
能力评估
Purpose & Capability
Name/description align with included code: the script calls Track123 endpoints to query tracking info and lists supported carriers. However the package ships a populated config.json containing an API key/secret. The README instructs users to create their own config.json from config.example.json, so bundling a populated config.json is inconsistent and unnecessary for the stated purpose.
Instruction Scope
SKILL.md instructions are narrowly scoped to configuring an API key and running the Node script. They do not ask for unrelated files or system data. But there is a contradiction: docs show fields named app_key/app_secret and API v2.1 endpoints, while scripts use api_secret and a v2 base path and send a Track123-Api-Secret header. That mismatch could cause confusion or unexpected credential use.
Install Mechanism
No install spec; this is an instruction+script skill that depends on axios (standard). All dependencies are from npm (package-lock present). No arbitrary remote downloads or extract-from-URL operations were found.
Credentials
The skill does not request environment variables, which is fine, but the repository includes a ready-made config.json with what appears to be Track123 credentials (app_key/api_secret). Shipping a populated secret in the repo is disproportionate and risky: it may be a real/active credential allowing usage (and rate/ billing) under someone else's account or exposing that account if the key is valid.
Persistence & Privilege
The skill runs as a normal CLI script, writes/reads a local .cache.json in the skill directory to implement caching, and does not request elevated or cross-skill persistence. always is false and it does not modify other skills or global agent settings.
如何使用
- 确保已安装 OpenClaw(本地或 Docker 部署)
- 在对话框中输入安装命令:
/install kuaidi-query - 安装完成后,直接呼叫该 Skill 的名称或使用
/kuaidi-query触发 - 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v1.0.3
- Added _meta.json, config.json, and package-lock.json files.
- No changes to code or documentation content.
- Version update to 1.0.3.
v1.0.2
文档更新:1) 配置示例明确说明示例值需要替换;2) 添加 JSON 格式输出示例;3) 添加 Compact 格式输出示例
v1.0.1
- Added a top-level YAML header (name, description, version, author, license) to SKILL.md.
- Updated configuration instructions in SKILL.md: changed key from "app_key" to "api_secret" and clarified API Key usage and security tips.
- Incremented version to 1.0.1 and updated documentation accordingly.
v1.0.0
kuaidi-query v1.0.0 - 首发版
- 支持 200+ 国内外主流快递公司物流信息查询
- 基于 Track123 API,实现运单追踪和自动识别
- 提供文本、JSON、紧凑等多种输出格式
- 内置缓存机制,减少重复查询
- 支持查询快递公司列表及多语言返回(中文、英文、俄文)
- 完善的命令行参数和配置说明
元数据
常见问题
Kuaidi Query 是什么?
Query logistics tracking information via Track123 API. 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 331 次。
如何安装 Kuaidi Query?
在 OpenClaw 或 Claude Code 对话框中运行命令「/install kuaidi-query」即可一键安装,无需额外配置。
Kuaidi Query 是免费的吗?
是的,Kuaidi Query 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。
Kuaidi Query 支持哪些平台?
Kuaidi Query 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。
谁开发了 Kuaidi Query?
由 Djttt(@djttt)开发并维护,当前版本 v1.0.3。
推荐 Skills