Agent skill · software engineering · jeremylongshore
flexport-rate-limits
Analyze and control Flexport request volume without inventing undocumented global limits or headers. Use when handling throttling, OAuth token budgets, endpoint-specific quotas, pagination pressure, or retry policy. Trigger with: "Flexport rate limit", "throttle Flexport calls", "budget Flexport tokens".
Why this skill is useful
Adds executable scripts for handling Flexport API rate limits with exponential backoff and queue-based throttling that aren't in public docs.
What it needs
Requires p-queue 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
Evidence-Driven Flexport Quota Control Overview Build controls from documented endpoint constraints and observed responses, not a fictional universal requests-per-minute number. The clearest fixed budget is OAuth token issuance: at most 10 token requests per day per documented credential flow. Prerequisites Inventory by OAuth, REST endpoint, and MCP tool Shared token cache and per-workload queues Observed statuses, provider messages, and latency without sensitive payloads Instructions Step 1: Separate budgets Track token acquisition, read traffic, mutations, webhook processing, and MCP tool calls independently. Step 2: Eliminate token churn Reuse each 24-hour OAuth JWT through a shared cache and single-flight refresh so business concurrency does not consume the 10/day token-request budget. Step 3: Honor explicit evidence Apply endpoint-specific documented limits and provider retry signals when present. Do not assume rate-limit headers or Retry-After exist universally. Step 4: Shape reads Use documented page sizes/cursors or links, avoid expensive expansions on index calls, and stop pagination when the business window is satisfied. Step 5: Serialize mutations Queue bookings and record creation by business key, cap attempts, and reconcile ambiguous outcomes before retry. Step 6: Tune from receipts Change concurrency only from measured latency/error evidence and preserve the before/after decision. 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-rate-limits