Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Plan and manage parcel shipping decisions with carrier selection, landed-cost math, customs checks, and delivery exception playbooks.
Plan and manage parcel shipping decisions with carrier selection, landed-cost math, customs checks, and delivery exception playbooks.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
On first use, read setup.md for integration guidelines.
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.
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
Use the smallest relevant file for the current task. TopicFileSetup flowsetup.mdMemory templatememory-template.mdCarrier selectioncarrier-selection.mdInternational customsinternational-customs.mdDelivery exception handlingexception-playbook.md
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.
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.
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.
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.
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.
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
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.
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.
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.
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.
If useful: clawhub star shipping Stay updated: clawhub sync
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.