Agent skill · software engineering · jeremylongshore
flexport-multi-env-setup
Separate Flexport development, test, staging, and production configuration without inventing provider hostnames or key prefixes. Use when creating environments, test credentials, receivers, or promotion rules. Trigger with: "Flexport environments", "Flexport staging setup", "separate Flexport credentials".
Why this skill is useful
Provides specific configuration patterns and safety guards for managing Flexport API across multiple environments 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 Environment and Credential Isolation Overview Flexport documents the same API base rather than arbitrary environment URLs. Isolation comes from accounts/credentials, receiver URLs, data policy, and mutation gates; a test credential may require coordination with the account executive. Prerequisites Environment/account matrix and data classification Distinct credential aliases and secret-store namespaces Separate webhook URLs, queues, databases, and mutation policy Instructions Step 1: Define each boundary For every environment record account identity, credential type, endpoint resources, version behavior, receiver, data class, and permitted operations. Step 2: Issue distinct credentials Never share client IDs, client secrets, API keys, cached tokens, or MCP sessions across environments. Step 3: Keep canonical hosts Use documented Flexport API/MCP hosts. Do not invent staging subdomains or infer an environment from a credential prefix. Step 4: Control test access Request any Flexport test credential through the documented account-executive route and keep local/default tests fixture-only. Step 5: Gate promotion Promote immutable artifacts while supplying environment-specific secret references and config. Production mutations remain disabled until canary approval. Step 6: Prove non-crossing Test that each environment rejects another's credential alias, callback destination, queue, and data-store identity. 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-multi-env-setup