Cross Border Logistics Optimizer

Compare cross-border e-commerce shipping options, packaging tactics, customs-risk signals, and speed-versus-cost tradeoffs for sellers, operations teams, and...

Security Scan

The skill's code and instructions are consistent with an advisory logistics helper that uses heuristics only, requests no credentials, and does not appear to call external services — however part of handler.py in the bundle was truncated in the listing, so confidence is reduced until the full file is inspected.

Purpose & Capability

Name/description, SKILL.md workflow, and the visible handler.py logic align: the skill produces heuristic route recommendations, packaging notes, and customs risk flags. It does not request unrelated credentials or binaries.

Instruction Scope

SKILL.md confines the skill to offline heuristics and explicitly disclaims live carrier or customs API use. The visible handler.py implements text parsing and decision logic and does not reference system files, environment variables, or external endpoints in the inspected portion.

Install Mechanism

No install spec is provided (instruction-only plus local code files). No downloads, package installs, or external installers are present in the metadata.

Credentials

The skill declares no required environment variables, no credentials, and the visible code does not access os.environ or require secrets. This is proportional to its advisory purpose.

Persistence & Privilege

always is false and there are no indications the skill attempts to persist or modify other skills or system-wide agent settings. Autonomous invocation remains possible by platform default but is not combined with other high-risk properties here.

Assessment

The skill appears coherent and appropriately scoped for an advisory logistics tool: it uses heuristics, asks for no secrets, and the visible code parses input and builds a markdown brief. Before installing or enabling autonomous use, open and review the full handler.py (the provided listing was truncated near the end) to confirm there are no hidden network calls or file/credential access. Specifically search the file for network or exec calls (requests, urllib, socket, subprocess, os.environ, open, smtplib, paramiko), and run the included tests in a sandbox to verify behavior. If you plan to allow unattended/autonomous invocation, consider restricting that until you confirm the full source contains no telemetry or exfiltration code.

Overview

Use this skill to turn shipment notes into a practical route recommendation brief. It is optimized for parcel-level e-commerce decisions, especially when a seller needs to balance shipping cost, transit speed, customs reliability, and packaging risk.

This MVP is advisory only. It does not fetch live rates, customs rules, or carrier SLAs. It relies on built-in logistics heuristics and common e-commerce exception patterns.

Trigger

Use this skill when the user wants to:

• compare shipping lanes for international e-commerce orders
• choose between cheap, fast, or low-risk logistics modes
• identify customs-delay risks and declaration pitfalls
• reduce dimensional-weight or packaging mistakes
• create a short decision memo for an ops team

Example prompts

• "Compare shipping options from China to Germany for cosmetics"
• "We need the safest route to Brazil for a fragile parcel"
• "How should I package low-value accessories going to Canada?"
• "Help me choose between cheap and fast cross-border shipping"

Workflow

1. Capture the origin, destination, parcel profile, product type, and business priority.
2. Detect likely risk signals such as customs sensitivity, dimensional-weight pressure, or restricted goods handling.
3. Compare three lane patterns with tradeoff notes.
4. Recommend the best-fit route, packaging posture, and documentation focus.
5. Return the result as a markdown decision brief.

Inputs

The user can provide any mix of:

• origin and destination countries
• weight and parcel dimensions
• product category or sensitivity
• declared value
• carrier preferences or service-level goals
• priority, such as cheapest, fastest, or safest
• known issue patterns, such as customs delay or damage

Outputs

Return a markdown report with:

• executive summary
• route comparison table
• recommended shipping plan
• packaging checklist
• customs and exception risks
• assumptions and follow-up actions

Safety

• Do not claim access to live rates or carrier systems.
• Treat all customs and compliance guidance as directional, not legal advice.
• Avoid guaranteed delivery claims.
• Call out when the input lacks dimensions, value, or product sensitivity details.

Examples

Example 1

Input: China to Germany, cosmetics, tracked service preferred.

Output: recommend a duty-aware direct line over the cheapest untracked option, plus declaration and leakage-control notes.

Example 2

Input: US to Canada, small accessories, cost priority.

Output: compare economy tracked, direct line, and express courier options, with dimensional-weight mitigation advice.

Acceptance Criteria

• Return markdown text.
• Include a 3-option lane comparison.
• Explain why the recommended lane fits the stated priority.
• Include at least one packaging note and one customs-risk note.