Agent skill · software engineering · jeremylongshore
flexport-hello-world
Prove a Flexport integration with one read-only shipment request and a defensively parsed receipt. Use when validating new credentials, network access, version selection, or response handling. Trigger with: "test Flexport API", "Flexport hello world", "verify shipment access".
Why this skill is useful
Provides specific commands and patterns for interacting with the Flexport REST API v2, which are not widely known or documented.
What it needs
Requires node 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
Read-Only Flexport v3 Proof Overview Establish connectivity without creating freight, documents, or bookings. Pin the intended API version, accept documented response wrappers, and preserve only a redacted proof. Prerequisites Approved read-only credential and credential alias Known account API version or explicit Flexport-Version choice A test policy that permits either one shipment reference or an empty list Instructions Step 1: Define the proof Set the expected account, endpoint, version, and allowed evidence before making a call. Step 2: Acquire authentication Reuse a cached OAuth client-credentials token, or use an explicitly approved API key. Keep the credential out of command text and logs. Step 3: Request shipments Send GET https://api.flexport.com/shipments with Bearer authorization, JSON acceptance, and Flexport-Version: 3 when an explicit v3 override is intended. Step 4: Parse defensively Read the documented response envelope and pagination links without assuming invented ID prefixes, undocumented nested records, or a fixed set of additive fields. Step 5: Validate tenant safety Confirm the response belongs to the intended account and emit only count, HTTP status, selected version, and a hashed operation identifier. Step 6: Fail closed Do not progress from a successful read to document creation, booking, or mutation. Make the next action a separate approved workflow. 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-hello-world