Agent skill · software engineering · jeremylongshore
flexport-migration-deep-dive
Migrate a legacy or v2-era Flexport integration to current v3 and MCP-aware contracts without unsafe concurrent production writers. Use when inventorying old endpoints, changing versions, or replacing custom workflows. Trigger with: "migrate Flexport integration", "upgrade Flexport v2", "adopt Flexport MCP".
Why this skill is useful
Adds executable scripts for migrating to Flexport, including dual-write patterns and validation processes that aren't in public docs.
What it needs
Requires bash 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
Controlled Flexport Integration Migration Overview Migration is a sequence of read-only comparison, explicit field mapping, shadow evaluation, and one controlled write owner. Never dual-book freight or dual-create trade records merely to compare systems. Prerequisites Endpoint/tool inventory with read/write classification Captured account default version and any Flexport-Version overrides Business-key mapping, rollback plan, and reconciliation owner Instructions Step 1: Inventory reality Trace every legacy path, version header, response assumption, event name, expansion, credential, and mutation. Step 2: Map to documented targets Choose current v3 REST endpoints or MCP tools by outcome. Record unsupported fields/operations rather than guessing equivalents. Step 3: Build tolerant readers Accept documented envelopes and additive fields, preserve opaque identifiers, and add sanitized fixtures for old/new differences. Step 4: Shadow reads only Compare current and target read paths over an approved sample. Normalize only business facts and investigate discrepancies. Step 5: Cut over one writer Freeze the legacy mutation queue, reconcile in-flight operations, switch one authoritative writer, and retain a rapid rollback that cannot produce concurrent writes. Step 6: Verify and retire Reconcile provider resources, events, and local operation keys across the cutover window before removing old credentials/code. 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-migration-deep-dive