Agent skill · software engineering · jeremylongshore
flexport-core-workflow-b
Create and reconcile Flexport purchase orders, commercial invoices, and shipment documents without inventing update semantics. Use when moving approved trade data into Flexport or attaching documents. Trigger with: "create Flexport purchase order", "upload Flexport document", "submit commercial invoice".
Why this skill is useful
Adds executable scripts for managing commercial invoices and product catalogs through the Flexport API that are not widely documented.
What it needs
Requires npm installed locally. Requires flexport account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Flexport Trade Document Workflow Overview Treat structured trade records and uploaded files as separate governed operations. Validate referenced network entities first, apply only documented create/update behavior, and never assume an uploaded document can be updated in place. Prerequisites Approved source record and data owner Resolved Flexport entity, location, shipment, and product references Document malware scan, MIME policy, and retention decision Instructions Step 1: Select the resource Choose purchase order, commercial invoice, or document from the business outcome; do not overload one endpoint with another resource's fields. Step 2: Resolve references Verify network entity, location, shipment, and product identifiers with read-only lookups before mutation. Step 3: Validate permissions Confirm the OAuth credential includes the required endpoint resource. Commercial invoice create/update also requires Flexport-side enablement and permission. Step 4: Submit once Persist an operation digest, then use the documented endpoint: /purchaseorders, /commercialinvoices, or /documents. Base64 document content must remain within the documented 10 MB pre-encoding limit. Step 5: Reconcile the result Store opaque returned IDs and retrieve the resource. For documents, replace through an approved new upload rather than inventing an update call. Step 6: Record lineage Link the Flexport resource to the approved source revision, actor, version header, and redacted outcome. Authentication REST calls authenticate with a cached OAuth 2.0 client-credentials Bearer token using audience https://api.flexport.com, or an explicitly accepted broad API key. Use distinct credentials per workload and never log credentials or tokens. MCP calls use the authenticated connection to https://mcp.flexport.com/mcp and remain subject to each tool's documented account permissions. Tool Discipline Use Read and Grep for discovery and evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/flexport-core-workflow-b--20d9a9