Agent skill · software engineering · jeremylongshore
flexport-deploy-integration
Deploy a Flexport REST, MCP, or webhook integration through provider-neutral canaries and rollback gates. Use when releasing credential, receiver, schema, or workflow changes. Trigger with: "deploy Flexport integration", "canary Flexport webhook", "roll back Flexport release".
Why this skill is useful
Adds deployment scripts and configurations for Flexport integrations on multiple platforms, which are not commonly found in public documentation.
What it needs
Requires fly, gcloud 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 Integration Deployment Canary Overview Keep deployment mechanics provider-neutral and Flexport validation surface-specific. A safe release proves secret injection, read-only access, version handling, webhook raw-body verification, and mutation gates before traffic expands. Prerequisites Immutable release artifact and reviewed configuration diff Secret references supplied by the deployment platform, not command-line values Read-only canary and tested rollback procedure Instructions Step 1: Classify the change Label REST schema/version, OAuth credential, MCP tool/session, webhook receiver, or business-policy change and name its rollback unit. Step 2: Validate offline Run contract fixtures for documented success, additive fields, auth errors, webhook signatures, and ambiguous mutations. Step 3: Deploy dark Start the release with mutations disabled and no automatic booking, document creation, or record update. Step 4: Run a read-only canary Reuse a cached token and perform one approved shipment read or MCP tracking call. For receivers, send a signed synthetic fixture through the exact raw-body path. Step 5: Expand gradually Increase traffic by a reversible cohort while monitoring auth, permission, parsing, queue, duplicate, and reconciliation outcomes. Step 6: Rollback on invariant breach Restore the prior artifact/configuration together, preserve redacted evidence, and reconcile any ambiguous in-flight mutation. 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-deploy-integration