Agent skill · data analytics · jeremylongshore
flexport-observability
Instrument Flexport REST, MCP, OAuth, and webhook outcomes without logging logistics payloads or credentials. Use when defining metrics, traces, dashboards, or alerts. Trigger with: "monitor Flexport integration", "Flexport metrics", "trace Flexport webhooks".
Why this skill is useful
Adds executable scripts for Prometheus metrics, structured logging, and alerting specific to Flexport integrations that aren't in public docs.
What it needs
Requires pino, prom-client 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
Identifier-Safe Flexport Observability Overview Observe operations and reconciliation, not shipment contents. Build low-cardinality telemetry around surface, operation class, outcome, version, and queue health while keeping identifiers and payloads out. Prerequisites Approved metric labels and redaction rules Operation taxonomy across OAuth, REST, MCP, webhook, and local processing Business-defined service objectives and incident ownership Instructions Step 1: Define safe dimensions Use environment, surface, operation class, status family, error class, version selection, and release. Exclude URLs with IDs, names, emails, routes, tags, documents, tokens, and raw messages. Step 2: Measure auth health Track cache hit, refresh success, token-request count, and credential alias as a controlled internal dimension; never log tokens or secret fragments. Step 3: Measure reads and mutations separately Record latency, attempts, pages, queue age, reconciliation lag, and ambiguous outcomes by operation class. Step 4: Measure webhooks in stages Distinguish received, signature-valid, durably queued, deduplicated, processed, and reconciled counts. Step 5: Alert on objectives Derive thresholds from approved freshness, queue, and error objectives—not arbitrary fixed seconds or undocumented rate headers. Step 6: Audit telemetry Sample schemas and label cardinality for sensitive leakage and regressions before expanding collection. 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-observability