bag replay debugger

Data Community

Skill notes

Core Workflow

Gather the smallest high-signal evidence set: failing outputs, logs, configs, recent changes, and relevant runtime context. Inspect the implementation and surrounding setup to isolate the narrowest plausible failure surface. Rank likely causes, rule out weak explanations, and identify the most actionable next fix or experiment. Validate the explanation with the smallest reliable check the repo or environment supports.

Deliver

A concise diagnosis with the most likely root cause or bounded uncertainty. The highest-signal evidence and suspect files, configs, or systems involved. The smallest safe fix path or next experiment to run.

Guardrails

Do not claim a root cause without evidence that explains the observed behavior. Separate symptoms from likely causes and call out uncertainty explicitly. Prefer the smallest reproducible scope before escalating to broad changes. Avoid commands that actuate hardware, move robots, or change live controller state unless explicitly requested.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Data
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@00PrabalK00 · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# Bag Replay Debugger

## Overview

Check rosbag or recorded data replay issues involving topic names, clocks, remaps, timing, and consumer mismatch.

## Core Workflow

1. Gather the smallest high-signal evidence set: failing outputs, logs, configs, recent changes, and relevant runtime context.
2. Inspect the implementation and surrounding setup to isolate the narrowest plausible failure surface.
3. Rank likely causes, rule out weak explanations, and identify the most actionable next fix or experiment.
4. Validate the explanation with the smallest reliable check the repo or environment supports.

## Deliver

- A concise diagnosis with the most likely root cause or bounded uncertainty.
- The highest-signal evidence and suspect files, configs, or systems involved.
- The smallest safe fix path or next experiment to run.

## Guardrails

- Do not claim a root cause without evidence that explains the observed behavior.
- Separate symptoms from likely causes and call out uncertainty explicitly.
- Prefer the smallest reproducible scope before escalating to broad changes.
- Avoid commands that actuate hardware, move robots, or change live controller state unless explicitly requested.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.