Agent skill · software engineering · jeremylongshore
flexport-performance-tuning
Tune Flexport integration latency and throughput from measured pagination, expansion, and concurrency evidence. Use when reads are slow, backlogs grow, or MCP browsing needs scaling. Trigger with: "speed up Flexport integration", "tune Flexport pagination", "scale shipment reads".
Why this skill is useful
Adds multiple executable scripts for optimizing Flexport API performance, including caching and parallel request handling that aren't in public docs.
What it needs
Requires npm installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Measured Flexport Pagination and Concurrency Overview Performance tuning must preserve correctness, account boundaries, and provider stability. Change one pagination, expansion, cache, or concurrency control at a time and validate full reconciliation. Prerequisites Baseline latency, pages, payload size, errors, and business freshness Documented pagination model for the selected REST endpoint or MCP tool Bounded worker pool and reversible configuration Instructions Step 1: Select one bottleneck Name the operation, surface, dataset window, and business objective. Exclude token acquisition from request concurrency by using a shared cache. Step 2: Use native pagination Follow REST response links where documented; for MCP browseshipments, advance endcursor while hasnextpage is true and keep first within 1–100. Step 3: Control expansions Avoid expansion on freight-invoice index calls as recommended; fetch detail only for records that need it. Step 4: Increase cautiously Raise one page-size or worker limit for read-only work, measure latency/error/backlog effects, and stop on provider or correctness degradation. Step 5: Protect mutations Keep bookings and trade-record writes serialized by business key and outside bulk read tuning. Step 6: Reconcile the result Compare counts and terminal cursors/links over the same bounded window, then document the chosen control and rollback. 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-performance-tuning