Agent skill · software engineering · jeremylongshore
flexport-debug-bundle
Assemble a metadata-only Flexport diagnostic package without sweeping environment files, logs, or payloads. Use when escalating an API, MCP, OAuth, or webhook defect. Trigger with: "create Flexport debug bundle", "escalate Flexport issue", "collect Flexport diagnostics".
Why this skill is useful
Adds an executable script for collecting diagnostic information from the Flexport API that automates troubleshooting and support ticket preparation.
What it needs
Requires curl, jq, tar 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
Redacted Flexport Diagnostic Manifest Overview Collect the smallest evidence that can distinguish contract, permission, version, transport, and provider failures. Never archive an entire environment, log directory, request body, webhook payload, or credential file. Prerequisites Incident ID, time window, surface, and failing operation Approved redaction rules and evidence recipient Known credential alias, application release, and expected Flexport version Instructions Step 1: Set an allowlist Declare exact metadata fields before collection: timestamps, release SHA, surface, operation, version header, status/code/message, correlation ID, and payload digest. Step 2: Collect configuration shape Record variable names, endpoint hosts, feature flags, and credential aliases—not values, tokens, secret suffixes, or .env content. Step 3: Summarize attempts List bounded attempt timestamps and outcomes. Exclude raw request/response bodies, document data, route details, names, emails, and addresses. Step 4: Add contract evidence Include a minimal sanitized fixture or field-name diff only when necessary to reproduce the failure. Step 5: Review twice Run automated secret/sensitive-data scanning, then require a human owner to approve the exact manifest and recipient. Step 6: Transfer and expire Use the approved support channel, record a checksum and expiry, then delete according to incident evidence policy. 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-debug-bundle--509f2f