Agent skill · software engineering · jeremylongshore
flyio-debug-bundle
Collect a bounded, redacted Fly.io support bundle for release, Machine, health, volume, network, and platform incidents. Use when escalating a reproducible problem. Trigger with: "build Fly debug bundle", "collect Fly support evidence", "sanitize Fly incident data".
Why this skill is useful
Adds an executable script for collecting comprehensive Fly.io diagnostics that aren't available in public documentation.
What it needs
Requires curl, jq, tar installed locally. Requires flyio account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Fly.io Redacted Support Evidence Overview Create a minimal evidence package that preserves diagnostic value without copying tokens, secret values, connection strings, full customer payloads, or unbounded logs. Every artifact needs source, timestamp, scope, redaction rule, and collection status. Prerequisites Incident ID, owner, app, environment, regions, and time window Approved secure destination with retention and access controls Redaction rules for identifiers, logs, environment, network, and customer content Instructions Step 1: Define the evidence manifest List requested artifacts, collection commands or APIs, owners, time bounds, redaction transformations, and expected hashes before gathering data. Step 2: Capture release and configuration state Record flyctl version, release or image identity, configuration hash, process groups, services, health definitions, and recent change references without including secrets. Step 3: Capture Machine and health state Collect aggregate status, Machine IDs or approved pseudonyms, regions, lifecycle and instance-version state, checks, restarts, and relevant exit metadata. Step 4: Capture bounded logs and platform context Use the smallest incident window, remove sensitive fields, note truncation, and record provider status separately from application evidence. Step 5: Capture storage and network topology Record volume IDs or pseudonyms, regions, attachments, snapshot state, public allocations, and private DNS expectations; exclude credentials and packet contents. Step 6: Seal and review Hash the sanitized artifacts, have the incident owner review the manifest, and publish only to the approved destination with expiry metadata. Authentication Collect with a read-only token where possible. Never place FLYAPITOKEN, app secret values, database URLs, WireGuard private keys, registry credentials, or raw environment dumps in the bundle. Treat deploy access as sensitive because deployed code can read runtime secrets. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/flyio-debug-bundle