Agent skill · software engineering · jeremylongshore
flexport-local-dev-loop
Develop Flexport integrations locally with sanitized contract fixtures and explicit live-test boundaries. Use when implementing REST v3 parsers, MCP tool adapters, webhook verification, or failure handling. Trigger with: "develop Flexport locally", "mock Flexport API", "test Flexport webhook".
Why this skill is useful
Provides a typed HTTP client wrapper and mock data setup specifically for Flexport's logistics API, which the AI wouldn't reliably generate on its own.
What it needs
Requires npm 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
Flexport Contract-Fixture Development Loop Overview Most development should run without credentials. Model official v3, MCP, and webhook shapes as fixtures, then use a separately approved read-only live smoke test only for gaps fixtures cannot prove. Prerequisites Current first-party schema pages and snapshot date Sanitized success, pagination, additive-field, and error fixtures Separate local secret injection and no-production-data rule Instructions Step 1: Choose one contract Name the exact REST endpoint, MCP tool, or webhook event and expected business outcome. Step 2: Capture shape, not data Build synthetic fixtures from documented field names/types. Replace all identifiers, routes, parties, financials, and document content. Step 3: Test invariants Cover required fields, unknown additive fields, opaque cursors/links, status/code/message errors, and missing authorization. Step 4: Exercise raw webhooks Sign exact synthetic bytes with a test secret and test malformed, wrong-length, duplicate, and valid SHA-256 signatures before parsing. Step 5: Gate live checks If needed, use an approved credential for one read-only operation. Never create bookings, documents, purchase orders, or invoices from the local loop. Step 6: Promote the receipt Commit fixtures and assertions, not tokens or live payloads; record schema source and review date. 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. Use Write or Edit only for the approved artifact, code, configuration, test, or receipt described by this workflow; do not make an unapproved Flexport-side change. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/flexport-local-dev-loop