Skip to content
Skills Library
DevOps & cloud · Analysis

flyio-debug-bundle

/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".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
7
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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".

Triggers from the description

build Fly debug bundlecollect Fly support evidencesanitize Fly incident data

Arguments

/flyio-debug-bundle [app-environment-and-incident-window]
Original author description

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".

How it works

  1. Overview
  2. Prerequisites
  3. Instructions
  4. Authentication
  5. Tool Discipline
  6. Output
  7. Examples
  8. Error Handling
  9. Resources
Original SKILL.md headings · 78 lines, 550 words
SKILL.md preview
---
name: flyio-debug-bundle
description: >-
  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".
allowed-tools: Read, Grep, Write, Edit
version: 2.0.0
argument-hint: '[app-environment-and-incident-window]'
model: inherit
effort: high
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags:
  - saas
  - flyio
  - diagnostics
  - support
  - redaction
compatibility: 'Requires read access to the affected app, an incident time window, a secure evidence destination, and approval for any log or configuration collection.'
---

# 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 `FLY_API_TOKEN`, 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.

## Tool Discipline

Use Read and Grep to inspect application configuration, deployment evidence, provider documentation, fixtures, logs, schemas, and existing tests before proposing a change. Use Write or Edit only for an approved plan, configuration, implementation, test, or redacted receipt. Do not create, deploy, scale, restart, stop, suspend, destroy, rotate, revoke, expose, or migrate live Fly.io resources without explicit operator approval.

## Output

- Evidence manifest with scope, source, timestamps, hashes, and redaction rules
- Sanitized release, configuration, Machine, health, log, volume, and network artifacts
- Collection failures, gaps, escalation question, retention owner, and deletion date

Return the target organization, app, environment, region set, Machine or database identifiers, source-contract fingerprint, evidence, unresolved risks, rollback state, and final decision without exposing tokens, secrets, connection strings, or customer data.

## Examples

For a Machine restart loop in one region, the bundle includes the release image, redacted config, Machine state history, health transitions, a five-minute sanitized log window, volume attachment metadata, and hashes. It omits environment values and full log history.

## Error Handling

| Failure | Response |
| --- | --- |
| Collection command fails | Record the failure and missing artifact; do not replace it with guessed data. |
| Secret is detected | Quarantine the bundle, rotate if exposure is possible, re-redact from the source, and issue a new hash. |
| Bundle is too large | Narrow the time and resource scope; do not archive an entire production log stream. |

## Resources

- [First-party source notes](references/official-docs.md)
- [Machines API setup](https://fly.io/docs/machines/api/working-with-machines-api/)
- [Automation and tokens](https://fly.io/docs/flyctl/integrating/)
- [App configuration](https://fly.io/docs/reference/configuration/)
- [Machine states](https://fly.io/docs/machines/machine-states/)
- [Monitoring](https://fly.io/docs/monitoring/)
- [Health checks](https://fly.io/docs/reference/health-checks/)
- [Fly Volumes](https://fly.io/docs/volumes/)
Files in this package (2)
  • SKILL.md 5 KB
  • references/official-docs.md 2 KB

Versions

The database has no other skills named flyio-debug-bundle.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 8566f35edbf4 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100flyio-common-errors
    Diagnose Fly.io deployment, routing, health, Machine, volume, and private-network failures with evidence-first triage. Use when an app is unhealthy or a release stalls. Trigger with: "debug Fly deploy", "why is my Fly app down", "triage Fly Machine".
  • 100flyio-webhooks-events
    Detect Fly.io Machine, health, release, and log changes through supported reads, waits, and log export without claiming general app webhooks. Use when building operational event automation. Trigger with: "monitor Fly Machine changes", "replace Fly webhook", "stream Fly health events".
  • 100fly
    Manage Fly.io machines, apps, volumes and app secrets through the Machines API. Use when the user asks what is running on Fly.io, or to start, stop, resize, move, redeploy or destroy a Fly machine.
  • 100customerio-debug-bundle
    Collect Customer.io debug evidence for support. Use when creating support tickets, reporting issues, or documenting integration problems. Trigger with phrases like "customer.io debug", "customer.io support ticket", "collect customer.io logs", "customer.io diagnostics".
  • 100vastai-debug-bundle
    Collect Vast.ai debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Vast.ai problems. Trigger with phrases like "vastai debug", "vastai support bundle", "collect…
  • 100deploy
    Elixir/Phoenix deployment patterns — Dockerfile, fly.toml; Use when configuring Fly.io, Docker, CI/CD, health checks…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.