{"id":18137,"plugin_id":"plugins_6a8623a0fe288191833ee0ca3fa883e7","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:14:39.274Z","digest":"f4dcfde9faf837e5c5a3a4e1f3c9c6c80a88db96b3d05c1aae55142a2b697d00","against":null,"payload":{"description":"Use when investigating a robot log or flight log with bagel — finding events, anomalies, or \"what happened around X\" in rosbags, MCAP, CAN, MDF4, ULog, or Betaflight files. Routes to the server's triage capability.","included_files":[],"name":"triaging-robot-logs","skill_md_contents":"---\nname: triaging-robot-logs\ndescription: Use when investigating a robot log or flight log with bagel — finding events, anomalies, or \"what happened around X\" in rosbags, MCAP, CAN, MDF4, ULog, or Betaflight files. Routes to the server's triage capability.\n---\n\n# Triaging robot logs\n\nThe bagel MCP server ships its own step-by-step triage workflow. Do not\nimprovise one: fetch and follow it.\n\n1. Call `run_poml_capability` with `poml_path=\"./src/agent/triage/investigate.poml\"`.\n2. Follow the returned instructions exactly (describe-first, windowed queries,\n   snippet/GIF evidence).\n\nIf the bagel tools are missing or the connection fails, the server is probably\nnot running — the user must start the Docker container for their data format\nfirst (see references/formats.md for the format → image → extra-args table,\nincluding the CAN `dbc` requirement).\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}