Token导航 LogoToken导航

Agent Skill · 前端设计

shipment-tracking(货运追踪)

shipment-tracking 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

shipment-tracking 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 6,149。

总安装 546周安装 23GitHub Stars 19下载 191核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:shipment-tracking(货运追踪)
来源仓库:https://github.com/finsilabs/awesome-ecommerce-skills
仓库路径:skills/shipment-tracking
安装命令:
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill shipment-tracking
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill shipment-tracking

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

shipment-tracking 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。它可结合来源仓库、安装命令和原始 README 继续核验具体用法。

安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。适用于前端设计类任务,通过 npx skills add 命令从指定 GitHub 仓库安装。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/shipment-tracking

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill shi…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

shipment-tracking 怎么安装?

在终端执行 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill shipment-trac…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

shipment-tracking 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

shipment-tracking 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

shipment-tracking 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

shipment-tracking 用的人多吗?

公开数据是累计安装 546 次,近一周安装 23 次,下载 191 次,GitHub 19 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

shipment-tracking 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
shipment-tracking

货运追踪 · 本页

54619需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Shipment Tracking

Overview

Shipment tracking lets customers follow their package from warehouse to doorstep, and proactively notifies them at key milestones (shipped, out for delivery, delivered). Most platforms send tracking emails automatically when a label is created — but a branded tracking page and proactive exception alerts (lost packages, failed delivery) require a dedicated tracking app or service.

When to Use This Skill

  • When customers need real-time package tracking on their order detail pages
  • When building post-purchase notifications (email/SMS) triggered by shipping milestone events
  • When you need to detect delivery exceptions (lost packages, failed delivery attempts) and trigger customer service alerts
  • When aggregating tracking data across multiple carriers (UPS, FedEx, USPS, DHL) into a single interface
  • When integrating with a carrier aggregator like EasyPost or Shippo for unified tracking webhooks

Core Instructions

Step 1: Determine your platform and choose the right tracking tool

PlatformRecommended ToolWhy
ShopifyAfterShip or RouteAfterShip provides a branded tracking page, proactive email/SMS notifications, and exception alerts across all carriers
WooCommerceAfterShip for WooCommerce or Shipment Tracking by WooCommerceAfterShip integrates with all major carriers; the official WooCommerce extension handles basic carrier tracking
BigCommerceAfterShip (BigCommerce App Marketplace) or ShipStation trackingAfterShip has a native BigCommerce integration; ShipStation also provides tracking if you use it for label creation
Custom / HeadlessEasyPost Tracker API or Shippo tracking webhooksEasyPost and Shippo normalize tracking events across all carriers into a single webhook feed

Step 2: Set up carrier tracking notifications

Shopify

Shopify's built-in tracking (no extra app needed for basics):

  1. When you fulfill an order and add a tracking number, Shopify automatically sends the customer a "Your order is on its way" email with the tracking link
  2. The tracking link goes to the carrier's website (e.g., ups.com for UPS) — it's functional but not branded
  3. Customers can check their order status at yourstore.com/orders/[order-id]

AfterShip (recommended for branded tracking + proactive notifications):

  1. Install AfterShip from the Shopify App Store (free plan available)
  2. AfterShip automatically detects new fulfillments in Shopify and begins tracking the package
  3. In AfterShip → Notifications, configure email and SMS notifications at each milestone:

- "In transit" — when the package leaves your facility - "Out for delivery" — day of delivery - "Delivered" — confirmation - "Exception" — failed delivery attempt or package delay

  1. Customize the tracking page at AfterShip → Tracking Page with your logo, colors, and product recommendations
  2. AfterShip's branded tracking page is hosted at yourstore.aftership.com or you can embed it on your own domain

For Shopify Plus: Use Klaviyo to trigger shipping notification emails based on AfterShip tracking events via Klaviyo's AfterShip integration — this gives you full control over the email design and content.

WooCommerce

Using WooCommerce Shipment Tracking (official extension):

  1. Install from WooCommerce.com (or use the free community version on WordPress.org)
  2. When fulfilling an order, enter the tracking number and carrier in WooCommerce → Orders → [Order] → Add Tracking Number
  3. WooCommerce sends the customer an updated order email with the tracking link
  4. Customers see the tracking link in My Account → Orders

Using AfterShip for WooCommerce:

  1. Install the AfterShip plugin from WordPress.org
  2. AfterShip syncs WooCommerce orders and begins tracking when tracking numbers are added
  3. Configure notification emails in AfterShip dashboard → Notifications
  4. The branded tracking page works the same as the Shopify version

ShipStation tracking (if using ShipStation for fulfillment):

  • ShipStation automatically emails customers when a label is created with a tracking link
  • Go to ShipStation → Account Settings → Notifications to configure which carrier events trigger emails
BigCommerce
  1. Install AfterShip Returns Center or AfterShip from the BigCommerce App Marketplace
  2. AfterShip syncs with BigCommerce orders automatically
  3. Configure notifications and the branded tracking page in the AfterShip dashboard (same as above)

BigCommerce's built-in tracking:

  • BigCommerce automatically sends shipping confirmation emails with tracking links when an order is marked as "Shipped" with a tracking number
  • Go to Store Setup → Email Templates → Shipped Email to customize the email content

Step 3: Handle tracking exceptions

Delivery exceptions (lost packages, failed delivery attempts) need fast resolution to protect customer satisfaction.

Setting up exception alerts

AfterShip:

  1. Go to AfterShip → Notifications → Exceptions
  2. Enable email alerts to your team for these exception types:

- "Exception" — carrier-reported issue - "Failed Attempt" — delivery attempt failed, needs rescheduling - "Returned to Sender" — package coming back

  1. AfterShip can trigger Slack or email alerts to your ops team alongside the customer notification

Shopify Flow (Plus):

Trigger: AfterShip tracking event received
Condition: Status is "Exception" or "Failed Attempt"
Action: Create customer service task in Gorgias or Zendesk
Action: Send internal Slack notification to #shipping-exceptions
Responding to exceptions

When AfterShip or your tracking tool flags an exception:

  1. Check the carrier's native tracking portal for the most current status
  2. For lost packages: file a claim with the carrier (UPS, FedEx, USPS all have online claims portals)
  3. For failed delivery: contact the customer to update their delivery address or arrange pickup
  4. For returned packages: coordinate with the customer on re-shipping vs. refund

Step 4: Add a branded tracking page to your store

A branded tracking page keeps customers on your site (vs. carrier sites), allows product recommendations, and reduces "where is my order" contacts.

AfterShip generates this automatically at yourstore.aftership.com. To put it on your own domain:

  1. In AfterShip → Tracking Page → Custom Domain, enter your subdomain (e.g., tracking.yourstore.com)
  2. Add a CNAME DNS record pointing tracking.yourstore.com to AfterShip's servers
  3. Update your shipping confirmation email to link to tracking.yourstore.com/[tracking-number] instead of the carrier URL

Embed tracking in your existing order status page:

  • For Shopify: AfterShip has a theme app extension that embeds the tracking widget directly in the Shopify order status page
  • For WooCommerce: the AfterShip plugin adds a tracking section to the WooCommerce "My Account → Orders" page automatically

Step 5: Custom / Headless — webhook-based tracking

For headless implementations, use EasyPost or Shippo to receive carrier webhooks and normalize tracking events:

// Register a tracking number with EasyPost to receive webhook updates
async function registerEasyPostTracker(params: {
  trackingNumber: string;
  carrier: string; // 'UPS', 'FedEx', 'USPS', 'DHL'
  orderId: string;
}): Promise<void> {
  const response = await fetch('https://api.easypost.com/v2/trackers', {
    method: 'POST',
    headers: {
      'Authorization': `Bearer ${process.env.EASYPOST_API_KEY}`,
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({
      tracker: {
        tracking_code: params.trackingNumber,
        carrier: params.carrier,
      },
    }),
  });
  const tracker = await response.json();
  // Store tracker.id to correlate future webhook events with this order
  await db.shipments.update({ tracking_number: params.trackingNumber }, {
    easypost_tracker_id: tracker.id,
  });
}

// Receive EasyPost webhook and update order status
// POST /webhooks/easypost
async function handleEasyPostWebhook(rawBody: Buffer, signature: string): Promise<void> {
  // Verify webhook signature
  const expectedSig = crypto
    .createHmac('sha256', process.env.EASYPOST_WEBHOOK_SECRET!)
    .update(rawBody)
    .digest('hex');
  if (expectedSig !== signature) throw new Error('Invalid webhook signature');

  const event = JSON.parse(rawBody.toString());
  if (event.description !== 'tracker.updated') return;

  const tracker = event.result;
  const shipment = await db.shipments.findByEasyPostTrackerId(tracker.id);
  if (!shipment) return;

  // Normalize EasyPost status to your internal status
  const statusMap: Record<string, string> = {
    pre_transit: 'label_created',
    in_transit: 'in_transit',
    out_for_delivery: 'out_for_delivery',
    delivered: 'delivered',
    failure: 'exception',
    return_to_sender: 'returned',
  };
  const normalizedStatus = statusMap[tracker.status] ?? 'in_transit';

  await db.shipments.update(shipment.id, { status: normalizedStatus });

  // Update order to delivered when package arrives
  if (normalizedStatus === 'delivered') {
    await db.orders.update(shipment.order_id, { status: 'delivered', delivered_at: new Date() });
  }

  // Send notification email at key milestones
  if (['in_transit', 'out_for_delivery', 'delivered', 'exception'].includes(normalizedStatus)) {
    await sendTrackingNotificationEmail(shipment.order_id, normalizedStatus, tracker.tracking_code);
  }
}

Best Practices

  • Use webhooks over polling — carrier webhooks deliver updates in near-real-time; polling every few hours misses same-day events like "out for delivery" and "delivered"
  • Send proactive notifications for exceptions — a delay or failed delivery email from you, before the customer notices, transforms a bad situation into a positive brand moment
  • Show estimated delivery date from day one — AfterShip and most carriers provide an EDD when the label is first scanned; display it on the tracking page and order confirmation email immediately
  • Alert your ops team on exceptions, not just customers — create an internal Slack/email alert for every exception event so your team can proactively resolve issues
  • Deduplicate notification emails — carriers sometimes send duplicate events; ensure your tracking app or custom webhook handler deduplicates based on event type per shipment

Common Pitfalls

ProblemSolution
Customer doesn't receive shipping confirmationCheck that Shopify/WooCommerce shipping notification emails are enabled and that the customer's email address was captured at checkout
Tracking page shows "no information available" for daysThis is normal for USPS for 24–48 hours after label creation; set customer expectations in the shipping confirmation email
Exception events not triggering alertsVerify your AfterShip notification settings include exception types; test by using a test tracking number that simulates an exception event
International tracking stops updating mid-journeyInternational handoffs between carriers often cause gaps; log the carrier's native tracking URL and fall back to it when events stop for 48+ hours

Related Skills

  • @order-fulfillment-workflow
  • @returns-management
  • @international-shipping
  • @order-management-system
  • @same-day-delivery

平台分布

Codex

36.11%
按下载量换算69

Claude

30.65%
按下载量换算59

Cursor

18.91%
按下载量换算36

Gemini CLI

8.82%
按下载量换算17

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills