什么是 快递追踪器？

快递追踪器是专为 Openclaw Skills 生态系统设计的专业工具，旨在简化包裹管理和物流监控。它通过读取专用 Markdown 文件并根据单号模式自动识别 USPS、FedEx 和 DHL 等承运商，实现物流信息的集中管理。

该技能为开发者提供了一个统一界面，使其无需离开编码环境即可监控订单。通过将其集成到 Openclaw Skills 中，用户可以在保持所有活跃货运的清晰、版本控制记录的同时，利用结合了直接 HTTP 请求与先进浏览器提取技术的混合追踪方案。

下载入口:https://github.com/openclaw/skills/tree/main/skills/pfrederiksen/shipment-tracker

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

快递追踪器 应用场景

• 直接在开发者工作区监控业务硬件交付或电子商务订单。
• 自动检测代理聊天中提供的原始追踪号码所属的承运商。
• 为早会或简报生成综合物流状态报告。
• 在单个文件中管理亚马逊、OnTrac 和 LaserShip 等多种承运商的多个包裹。

1. 用户将追踪号码和项目描述添加到 Markdown 文件中，通常位于 memory/shipments.md。
2. 该技能执行 Python 脚本来解析文件，并通过针对主要供应商的正则模式匹配来检测承运商。
3. 启动混合状态检查，首先通过轻量级 HTTP 请求从承运商页面提取基本状态数据。
4. 如果承运商网站包含大量 JavaScript 或使用机器人防护，该技能会提供 browser-use 命令进行深度提取。
5. 结果将返回给 CLI 或代理界面的用户，允许在送达后更新或删除文件记录。

快递追踪器 配置指南

要开始使用 Openclaw Skills 的这项快递追踪功能，请确保您已安装 Python 3.10+ 并按照以下步骤操作：

# 创建追踪目录和文件
mkdir -p memory
touch memory/shipments.md

# （可选）安装高级追踪所需的依赖项
pip install browser-use

请确保您的 memory/shipments.md 遵循所需的表格格式，以便该技能能够正确解析您的包裹数据。

快递追踪器 数据架构与分类体系

该技能依赖于工作区内结构化的 Markdown 表格来维护所有活跃包裹的状态。

所有元数据都存储在本地的 memory/shipments.md 中，确保您的 Openclaw Skills 数据保持可访问且可版本化。

name: shipment-tracker
description: "Track packages across carriers (USPS, UPS, FedEx, DHL, Amazon, OnTrac, LaserShip). Use when: user asks about package status, adds a tracking number, wants delivery updates, or mentions shipments. Reads a markdown shipments file, auto-detects carrier from tracking number patterns, and checks status. Hybrid approach: tries direct HTTP first, recommends browser-use for JS-heavy carrier pages. ?? Privacy: browser-use fallback sends tracking data to cloud services."

Shipment Tracker

Track packages across multiple carriers from a markdown shipments file. Auto-detects carrier from tracking number patterns. Hybrid status checking: tries direct HTTP first, falls back to recommending browser-use for full tracking details.

Shipments File Format

The skill reads a markdown file with a table of active shipments:

# Active Shipments

| Order | Item | Carrier | Tracking | Link | Added |
|-------|------|---------|----------|------|-------|
| Acme #1234 | Widget | USPS | 9449050899562006763949 | [Track](https://...) | 2026-02-19 |

• Carrier and Link are optional — auto-detected from tracking number pattern
• Remove entries once delivered to keep the file clean
• Default location: memory/shipments.md in the workspace

Usage

# Check all active shipments
python3 scripts/shipment_tracker.py memory/shipments.md

# JSON output for integrations
python3 scripts/shipment_tracker.py memory/shipments.md --format json

# Detect carrier from a tracking number
python3 scripts/shipment_tracker.py --detect 9449050899562006763949

Carrier Detection

Automatically identifies carrier from tracking number patterns:

Status Checking (Hybrid)

1. Direct HTTP — Attempts to extract status from carrier tracking pages via urllib. Works for basic status on USPS and some other carriers.
2. Browser-use fallback — When HTTP fails or carriers use JS-heavy pages, the script provides the exact browser-use command to run.

When the script output includes needs_browser_use: true, it will provide a complete browser-use command:

python3 -c "
import asyncio
from browser_use import Agent, Browser, ChatBrowserUse
async def main():
    browser = Browser(use_cloud=True)
    llm = ChatBrowserUse()
    agent = Agent(
        task='Go to  and extract the current tracking status, delivery date, and location',
        llm=llm, browser=browser
    )
    result = await agent.run(max_steps=10)
    print('TRACKING:', result)
asyncio.run(main())
"

This ensures reliable tracking across all carriers, even those with aggressive bot detection.

When browser-use is needed:

• UPS, FedEx, Amazon (heavily JS-based tracking pages)
• USPS when basic parsing fails (complex status updates)
• Any carrier with CAPTCHA or bot detection
• Sites that require user interaction or form submission

Workflow

1. User provides a tracking number → run --detect to identify carrier
2. Add to memory/shipments.md with order details
3. Morning briefing or on-demand: run the script to check all shipments
4. For shipments needing browser-use:
   • Non-sensitive packages: Use the provided browser-use command
   • Privacy-sensitive packages: Manual browser check instead (data stays local)
5. When delivered: remove from the shipments file

Privacy guidance: For medical supplies, personal items, or confidential orders, consider manual tracking to avoid sending shipment details to cloud services.

System Access

Direct skill execution:

• File reads: One markdown file (path provided as argument)
• Network: HTTPS GET to carrier tracking pages (e.g., tools.usps.com) — read-only, no authentication
• No file writes, no subprocess calls, no shell execution

Browser-use fallback (privacy implications): When the skill recommends browser-use commands, external data transmission occurs:

• Tracking numbers and order information sent to cloud browser service
• Package details processed by external LLM (ChatBrowserUse)
• Carrier tracking URLs accessed via cloud infrastructure

Privacy consideration: Browser-use fallback involves third-party services that may log or process shipment data. For sensitive packages, consider manual browser tracking instead of the provided browser-use commands.

Requirements

• Python 3.10+
• Outbound HTTPS access to carrier tracking sites
• browser-use (optional, for full tracking on JS-heavy sites)