tw-ecom-logistics-cross-border
Select carriers and manage cross-border shipping operations for Taiwan — carrier choices (DHL / FedEx / UPS / 郵局 國際), customs clearance operations (報關), DDP vs DDU trade-offs, label generation, and returns handling. Use when choosing a carrier, estimating shipping cost or transit time, or managing the physical movement of cross-border goods. Do NOT use for duty/tax calculation, HS-code classification, or 境外電商 tax registration (see tw-ecom-compliance-cross-border). Do NOT use for domestic TW shipping. STATUS: SKELETON — body pending.
pinned to #4e7f4f8updated last month
Ask your AI client: “install skills/tw-ecom-logistics-cross-border”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/tw-ecom-logistics-cross-bordermetahub onboarded this repo on the author's behalf.
If you own github.com/asgard-ai-platform/skills on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
225
Last commit
last month
Latest release
published
- #ai-agent
- #anthropic
- #claude
- #claude-agent-skills
- #claude-code
- #coding-agent
- #knowledge-base
- #mcp
- #methodology
- #open-source
- #prompt-engineering
- #skills
- #taiwan
About this skill
Pulled from SKILL.md at publish time.
STATUS: SKELETON — body pending.
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.4e7f4f8· last month
Behavioral checks ran but aren't published for this artifact; the static checks above ran at publish time.
Documentation
7 passed2 warningsHomepage or repository declaredwarn
No homepage or repository declared.
Add a "homepage" or "repository" field to SKILL.md.
Documentation shows usagewarn
Documentation has no code examples.
Add at least one fenced example showing a real invocation.
Description quality
88 words · 538 chars — "Select carriers and manage cross-border shipping operations for Taiwan — carrier…"
README is present and substantial
33,936 chars · 20 sections · 3 code blocks
Tags / topics declared
13 total — ai-agent, anthropic, claude, claude-agent-skills, claude-code, coding-agent (+7)
README has usage / example sections
no labeled section but 3 code blocks document usage
Homepage / docs URL declared
https://vault.asgard-ai.com/skills/
Description is substantive
Description is 87 words.
Documentation present and substantive
Documentation present (SKILL.md, 354 words).
Release history
1- releasecurrent4e7f4f8warnlast month
Contents
Cross-Border Logistics
STATUS: SKELETON — body pending.
When to use this skill
- Choosing a carrier for TW → overseas or overseas → TW shipments
- Estimating shipping cost, transit time, or DDP total landed cost
- Managing customs clearance operations (報關) and document prep
- Handling returns from overseas buyers
- Comparing DHL / FedEx / UPS / 郵局 國際 for a given route
Do NOT use when
- Duty/tax calculation, HS-code classification, or 報單 filing →
tw-ecom-compliance-cross-border - 境外電商 sales-tax registration →
tw-ecom-compliance-cross-border - Domestic TW logistics →
tw-ecom-logistics-home/tw-ecom-logistics-cvs
Core concepts
TODO: DDP vs DDU trade-offs (landed cost transparency, liability shift), carrier-choice framework (weight / speed / destination / DDP capability), customs document prep (商業發票、包裝明細、原產地證明), label standards per carrier, returns friction and cost structure. NOTE: HS-code classification, de minimis thresholds, and duty/VAT rates belong in tw-ecom-compliance-cross-border — do not duplicate here.
Decision tree
TODO: carrier by destination / weight / speed / DDP preference.
Implementation guidance
TODO: customs doc prep, label generation, tracking reconciliation.
Gotchas
TODO: 5-6 pitfalls (HS misclassification, DDP total cost shock, returns black hole, restricted-items list, FTZ vs general customs).
IRON LAW
TODO.
Output Format
TODO.
Related
tw-ecom-compliance-cross-borderxborder-logistics,xborder-sea-entry
Last verified: 2026-04
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/tw-ecom-logistics-cross-border