flight-recorder
Analyze flight recorder dumps to diagnose bugs from event traces
npx skills add majiayu000/claude-skill-registry --skill flight-recorder --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
Analyze flight recorder dump(s) to diagnose a bug or anomaly. The user may describe the bug, specify files, or both. If invoked with no arguments, load the newest dump and use the USER NOTE in the dump as the bug description. ## File Resolution 1. **No argument**: Use `release/recorder/`, pick the newest `fr_*.txt` by modification time. The USER NOTE inside the dump describes what happened. 2. **Count** (e.g., "last 3", "3 newest"): Load that many newest dumps from `release/recorder/` 3. **"today"** or **"all from today"**: All `fr_*.txt` files from today in `release/recorder/` 4. **Exact filename**: Search `release/recorder/` for a matching file 5. **Full path**: Use as-is Use `ls -t release/recorder/fr_*.txt` to find files. Confirm resolved file(s) to the user before analyzing. ## Dump Structure Each dump has four sections: 1. **USER NOTE** — The user's description of what they observed (entered at dump time via InputBox). This is your primary bug description when no argument is provided. 2. **GLOBAL STATE** — Snapshot of GUI state, interceptor flags, overlay visibility, workspace, foreground window at dump time. 3. **WINDOW LIST STATE** — Store revision, dirty flags, queue lengt
- File Resolution
- Dump Structure
- Analysis Method
- Step 1 — Understand the bug
- Step 2 — Check global state for immediate red flags
- Step 3 — Trace the event chain
- Step 4 — Multi-dump correlation (when multiple files)
- Event Reference
- Reporting
What does the flight-recorder skill do?
Analyze flight recorder dumps to diagnose bugs from event traces
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill flight-recorder --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.