Token导航 LogoToken导航TokenDH.com
开发需要联网clawhub未标认证来源可访问clear审计通过

shippingshipping 开发

Agent Skill

shipping 用于补充开发相关能力,适合在 OpenClaw 中需要让 Agent 承接开发相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

25,884

周安装

1,037

GitHub Stars

公开资料未说明

下载量

8,379
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:shipping(shipping 开发)
来源仓库:https://github.com/ivangdavila/shipping
安装命令:
openclaw skills install shipping
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install shipping

简介

shipping 协助规划包裹运输决策,涵盖承运商选择、关税计算与交付异常处理。

  • 适用于 OpenClaw 中跨境电商或物流优化类项目开发。
  • 使用 openclaw skills install shipping 命令安装,需配置目的地与货物参数。
  • 费率与政策随地区变化,建议定期更新数据库以保证准确性。
  • 涉及跨境清关信息,须遵守当地法律法规与数据隐私要求。

SKILL.md

name
Shipping Operations
slug
shipping
version
1.0.0
homepage
https://clawic.com/skills/shipping
description
Plan and manage parcel shipping decisions with carrier selection, landed-cost math, customs checks, and delivery exception playbooks.
changelog
Initial release with carrier selection, customs checks, and exception handling workflows.
metadata
{"clawdbot":{"emoji":"BOX","requires":{"bins":[],"config":["~/shipping/"]},"os":["linux","darwin","win32"],"configPaths":["~/shipping/"]}}

Setup

On first use, read setup.md for integration guidelines.

When to Use

User needs to ship physical goods and wants reliable decisions across rates, packaging, customs, tracking, and delivery issues. Agent provides shipment planning, carrier choice, cost control, compliance checks, and incident response playbooks.

This skill is advisory and workflow-focused. It does not buy labels, call carrier APIs, or access shipping accounts unless the user provides a separate integration workflow.

Architecture

Memory lives in ~/shipping/. See memory-template.md for structure and status fields.

~/shipping/
|- memory.md             # Durable shipping context and preferences
|- carrier-rules.md      # Preferred carriers and service constraints
|- international.md      # Country and customs notes
`- incidents.md          # Repeated failure patterns and resolutions

Quick Reference

Use the smallest relevant file for the current task.

TopicFile
Setup flowsetup.md
Memory templatememory-template.md
Carrier selectioncarrier-selection.md
International customsinternational-customs.md
Delivery exception handlingexception-playbook.md

Core Rules

1. Confirm Shipment Profile First

Before recommending any option, confirm:

  • Origin and destination
  • Package count, dimensions, and weight
  • Delivery deadline and budget ceiling
  • Value, fragility, and regulatory constraints

Never optimize blind.

2. Price for Total Landed Cost

Always show total cost, not just carrier label price:

  • Transport fee
  • Packaging and handling
  • Fuel, remote, residential, signature, and insurance surcharges
  • Duties, taxes, and brokerage where applicable

If any component is unknown, mark it as estimate and show risk.

3. Select Carrier by SLA Risk, Not Sticker Price

Pick service based on the real failure cost:

  • Time-critical shipment: prioritize reliability and claims process
  • Low-value shipment: prioritize cost efficiency
  • International shipment: prioritize customs support and tracking depth

State tradeoffs explicitly before final recommendation.

4. Validate Compliance Before Label Purchase

For cross-border shipments, verify:

  • Commodity description and HS code quality
  • Declared value consistency with invoice
  • Prohibited or restricted item checks
  • Incoterm and importer responsibilities

Do not proceed when documentation is incomplete.

5. Run Tracking Checkpoints Proactively

Set checkpoints at minimum for:

  • Label created but not scanned within 24h
  • Customs hold or pending documents
  • Out for delivery delays beyond promised window

For each checkpoint, provide next action and owner.

6. Treat Exceptions as Playbooks, Not Improvisation

Use a defined response path for lost, damaged, delayed, returned, or refused shipments:

  • Capture facts and evidence first
  • Notify customer with realistic timeline
  • Open claim/escalation within carrier deadline
  • Decide reshipment vs refund based on cost and SLA

7. Save Reusable Shipping Intelligence

After each meaningful case, update memory with:

  • Carrier performance by route
  • Recurring surcharge patterns
  • Packaging failures and fixes
  • Country-specific documentation pitfalls

This turns shipping from reactive to compounding.

Common Traps

  • Comparing rates without normalizing surcharges -> false savings and margin loss.
  • Guessing box size from product photos -> dimensional weight surprises.
  • Declaring vague item descriptions -> customs holds and rejections.
  • Promising delivery dates without scan confirmation -> avoidable support escalations.
  • Filing claims without evidence package -> denied reimbursement.
  • Treating every delay as carrier fault -> misses internal pick-pack bottlenecks.

Security & Privacy

Data that leaves your machine:

  • None by default from this skill itself.

Data that stays local:

  • Shipping context and learned patterns under ~/shipping/.

This skill does NOT:

  • Access undeclared external services automatically.
  • Buy labels or place shipping orders automatically.
  • Retrieve tracking events from carrier APIs automatically.
  • Store payment credentials or full card data.
  • Modify files outside ~/shipping/ for memory.

Related Skills

Install with clawhub install <slug> if user confirms:

  • ecommerce - Store operations and conversion workflows.
  • marketplace - Multi-platform selling and fulfillment strategy.
  • inventory - Stock planning and replenishment control.
  • sell - Listing, pricing, and sales execution.
  • buy - Purchasing decisions and supplier-side evaluation.

Feedback

  • If useful: clawhub star shipping
  • Stay updated: clawhub sync

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

92.31%
按下载量换算7,735

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

需要联网

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

安装前确认

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

来源信息

继续浏览同类 Skills