Openclaw Skills for vessel cargo matching finds domestic or international cargo boards by current port, destination port, and ship capacity.
Install & Download
1. ClawHub CLI
The fastest way to install a skill directly from the registry.
npx clawhub@latest install find-cargo-for-vessel
2. Manual Installation
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
3. Prompt Installation
Copy this prompt to OpenClaw to install it automatically.
Help me install find-cargo-for-vessel using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Prefer to download?
Get the raw skill files in a ZIP archive.
What is find-cargo-for-vessel?
Openclaw Skills for vessel cargo matching
This skill provides a structured workflow for ShippingClaw/OpenClaw agents to search for cargo opportunities that fit a vessel’s available tonnage. It uses current port, destination port, and ship capacity as the only required inputs, then filters live freight listings by route distance and capacity compatibility.
Openclaw Skills makes cargo discovery more reliable by avoiding guesswork around cargo board selection, port coordinates, vessel type, cargo type, and other unavailable factors. It supports both inland/domestic and international trade classification, and returns searchable results plus detail views for one complete booking or inquiry pass.
find-cargo-for-vessel Use Cases
- Shipowners or operators need to find cargo boards for a vessel based on current port and destination port.
- A user wants to know whether a vessel can carry a given tonnage on a specific route.
- An agent must search "ship finding cargo" or "cargo board matching" without manually estimating distance or cargo fit.
- A workflow needs to distinguish domestic trade from international trade using port pair logic.
- A front end needs clickable cargo board results and in-app detail actions for deeper inspection.
- A service must record and return cargo opportunities after a single complete query.
- A system needs a local queue fallback when the backend API is not configured.
How find-cargo-for-vessel Works
- Collect the three required inputs: current port, destination port, and vessel capacity in tons.
- Call the search script with those parameters and a user ID.
- The script queries the online cargo-board source and applies route and tonnage filtering rules.
- The system classifies the result as
domesticorinternationalbased on whether either end is outside mainland China. - Results are returned in a ranked list, defaulting to the top 10 items.
- Each result includes cargo board number, company, cargo name, quantity, loading/unloading ports, loading time, update date, and distance fields.
- The cargo board number is rendered as a clickable Markdown link, and structured
detail_actiondata is provided when supported. - If the quantity cannot be converted reliably to tons, the item is retained and flagged as manual confirmation required.
- On successful completion, the request is treated as one full inquiry and the system records the requirement automatically.
- If the backend is not configured, the request is safely written to a local pending-sync queue instead of failing.
find-cargo-for-vessel Setup
- Ensure Python 3 is available, since the skill metadata requires
python3. - Install dependencies from the project requirements.
pip install -r requirements.txt
- Run the cargo-matching service locally for development.
uvicorn scripts.service:app --host 0.0.0.0 --port 8765
- Set the public base URL in deployment so the browser can reach the service endpoint.
export CARGO_MATCHER_PUBLIC_URL="https://shipping.example.com/cargo-service"
- Use the local default during development if no public endpoint is available.
export CARGO_MATCHER_PUBLIC_URL="http://127.0.0.1:8765"
- Invoke the search command with the required inputs.
python scripts/find_cargo.py search \
--current-port "<current port>" \
--destination-port "<destination port>" \
--capacity-tons <capacity> \
--user-id "<logged-in shipowner user ID>"
- For a selected result, call the detail command using the returned
solididentifier.
python scripts/find_cargo.py detail --solid "<solid>"
find-cargo-for-vessel Data Schema & Taxonomy
Openclaw Skills organizes cargo matching output around a small, route-centric data model.
Core input fields
| Field | Type | Required | Notes |
|---|---|---|---|
| current_port | string | Yes | Port name or UN/LOCODE |
| destination_port | string | Yes | Port name or UN/LOCODE |
| capacity_tons | number | Yes | Positive vessel capacity in tons |
| user_id | string | Yes | Logged-in shipowner user identifier |
Search result fields
| Field | Type | Notes |
|---|---|---|
| solid | string | Unique cargo board identifier used for detail lookup |
| company | string | Cargo source company |
| cargo_name | string | Cargo description |
| quantity | string/number | Cargo volume or weight display value |
| loading_port | string | Port where cargo is loaded |
| unloading_port | string | Port where cargo is discharged |
| loading_time | string | Scheduled loading time |
| update_date | string | Latest listing update |
| current_to_loading_distance | number | Great-circle port distance used for ranking |
| unloading_to_destination_distance | number | Great-circle port distance used for ranking |
| trade_type | enum | domestic or international |
| quantity_status | enum | May be manual_confirmation when conversion to tons is uncertain |
Detail payloads
| Field | Type | Notes |
|---|---|---|
| detail_url | string | Clickable in-site HTML detail page |
| detail_action | object | Structured action for UI binding |
| detail_action.api_path | string | In-site API path for JSON access |
Operational taxonomy
- Result ranking: quantity-confirmable first, then ascending combined distance.
- Filtering: capacity-fit and route-distance rules only; no vessel type, cargo type, draft, or minimum load-rate assumptions.
- Persistence: successful inquiries are recorded automatically; unconfigured backend requests may be queued locally for later sync.
- Presentation: cargo board numbers are exposed as Markdown links, with detail actions preferred when supported.
find-cargo-for-vessel Advanced Features
- Supports both search and detail workflows in one Openclaw Skills package.
- Returns clickable cargo board identifiers for richer agent or UI interactions.
- Provides structured
detail_actionbindings for in-app detail opening instead of raw page scraping. - Distinguishes domestic and international trade automatically from port pair context.
- Preserves uncertain quantity records with
manual_confirmationinstead of discarding them. - Uses route-distance and capacity-fit ranking to surface the most relevant cargo opportunities first.
- Safely falls back to a local pending-sync queue when the backend API is unavailable.
- Exposes service endpoints for health checks, search, JSON detail retrieval, and view rendering.
SKILL.md
Loading
Related Openclaw Skills
招采萝卜坑识别专家 · 招标文件量身定制扫描
Openclaw Skills for scanning full tender documents to identify hidden "carrot pit" clauses, exclusion signals, and compliance risks.
Bid Carrot Pit Tenderer
Openclaw Skills helps procurement teams self-audit tender documents, detect objection-prone clauses, and generate compliant redraft and rebuttal plans before publication.
Connect to Skilder
Openclaw Skills for instantly connecting an AI agent to Skilder via a fixed remote MCP endpoint with OAuth or key-based fallback.
Requirement Processor
Requirement Processor standardizes how Openclaw Skills turns unclear feature requests into validated, phased implementation plans and reusable project documentation.
Zhiyanzhai Research Article Generator
Openclaw Skills for generating a long-form, citation-backed Simplified Chinese research article on the identity of Zhiyanzhai in Dream of the Red Chamber.
Luoshenfu Literary Research
Openclaw Skills for researching and writing a scholarly Simplified Chinese analysis of Ode to the Goddess of Luo River, with citations and annotations.
Featured*
