Agent skill · marketing growth · jeremylongshore
flexport-cost-tuning
Reduce unnecessary Flexport traffic and processing without making unsupported API pricing claims. Use when tuning polling, pagination, payload expansion, cache freshness, or reconciliation volume. Trigger with: "optimize Flexport requests", "reduce Flexport polling", "tune shipment freshness".
Why this skill is useful
Provides specific strategies and code examples for optimizing Flexport API usage that the AI wouldn't reliably generate on its own.
What it needs
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 Request-Volume and Freshness Tuning Overview Optimize volume and latency against business freshness, not a fabricated per-request bill. Prefer event-driven invalidation plus bounded reconciliation and measured page/expansion choices. Prerequisites Baseline request counts by operation and outcome Business-approved freshness and recovery windows Metrics for pages read, expansions, cache hits, and reconciliation lag Instructions Step 1: Name the outcome Tie each request to shipment tracking, trade document ingestion, invoice reconciliation, or booking—not generic synchronization. Step 2: Set freshness classes Define active-shipment, completed-shipment, invoice, and reference-data windows from operational need; do not hard-code invented provider change rates. Step 3: Use events as hints Let authenticated webhooks trigger targeted reads, then run bounded periodic reconciliation for missed deliveries. Step 4: Trim reads Stop pagination at the required window, request only supported expansions, and avoid expansion on invoice index calls where Flexport recommends against it. Step 5: Cache safely Cache read-only reference results under an explicit TTL and invalidate on evidence; never cache credentials, authorization decisions, or mutable booking approval. Step 6: Prove the change Compare request count, stale-result rate, reconciliation time, and provider errors before and after; roll back if correctness worsens. 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-cost-tuning