slam-log-triager

Diagnose SLAM and localization failures from logs, sensor feeds, and TF frames.

1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/00PrabalK00/claude-skills --skill slam-log-triager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slam-log-triager
Source: https://github.com/00PrabalK00/claude-skills/tree/main/skills/slam-log-triager
Command: npx skills add https://github.com/00PrabalK00/claude-skills --skill slam-log-triager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze SLAM and localization logs to identify mapping drift, sensor mismatches, TF frame issues, and timing or parameter failures that destabilize mapping or localization.

Core Features & Use Cases

  • Inspect logs, configurations, and recent changes to diagnose drift and misalignment between odometry and the map.
  • Correlate sensor data and TF frames to locate root causes and inform targeted fixes.
  • Provide a concise action plan with minimal, testable changes to stabilize SLAM and localization in robotics projects.

Quick Start

Run the triage on the latest slam log to identify the most likely cause of drift and outline the next steps.

Frequently Asked Questions about slam-log-triager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose SLAM drift from robot logs and TF frames?

Diagnose SLAM drift by analyzing logs, sensor feeds, and TF frames to identify misalignment or timing issues. The triage workflow maps these symptoms to root causes and proposes minimal, testable fixes for your robotics project.

What causes localization drift and misalignment between odometry and the map?

Localization drift and misalignment are caused by sensor mismatches, TF frame issues, or timing and parameter failures. Inspecting logs and configurations helps identify these specific destabilizing factors in SLAM systems.

How do I troubleshoot SLAM timing issues and sensor mismatches?

Troubleshoot SLAM timing issues and sensor mismatches by correlating sensor data and TF frames. This triage process locates root causes and informs targeted fixes to stabilize mapping and localization.

Can I use log analysis to find root causes of mapping failures without external dependencies?

Yes, you can use log analysis to find root causes of mapping failures without external dependencies. The triage process inspects recent changes and configurations to output an evidence-based diagnosis with concrete next steps.

What is the best way to fix SLAM localization drift with minimal changes?

The best way to fix SLAM localization drift with minimal changes is applying a triage workflow that maps symptoms to root causes. It provides an action plan with minimal, testable modifications to stabilize the system.