Agent skill · data analytics · jeremylongshore
flexport-data-handling
Analyze, minimize, and govern Flexport shipment, customs, invoice, purchase-order, and document data. Use when mapping fields, designing storage, exporting records, or setting retention with the real data owner. Trigger with: "handle Flexport data", "minimize shipment fields", "govern Flexport documents".
Why this skill is useful
Provides specific data handling procedures and compliance patterns for Flexport logistics 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 Logistics Data Minimization Overview Flexport payloads can contain commercial, personal, customs, financial, and document content. This skill does not invent universal GDPR, CCPA, ITAR, or retention rules; it makes the accountable owner and policy explicit. Prerequisites Documented purpose and accountable data owner Field-level source-to-destination map Approved classification, residency, access, retention, and deletion policy Instructions Step 1: Inventory exact fields Map only fields needed for the approved outcome, including identifiers embedded in routes, parties, documents, invoices, customs, tags, or MCP tracking output. Step 2: Classify with policy Apply the organization's authoritative classification and legal guidance. Do not infer a regime from an HS code, endpoint, country, or shipment mode. Step 3: Minimize collection Prefer opaque resource IDs and derived operational state over raw documents, addresses, names, emails, entry numbers, or charge details. Step 4: Protect transport and storage Use approved encrypted channels and stores, workload-scoped credentials, tenant boundaries, and access logging. Step 5: Control outputs Redact logs, metrics, prompts, tickets, debug bundles, and analytics. Never include document bodies, tokens, or full route/party payloads by default. Step 6: Enforce lifecycle Attach retention/deletion rules to the approved data class, test deletion and backup behavior, and record exceptions with owner and expiry. 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-data-handling--9debc5