debug-get-voxel-grid skill

Overview

This skill is a debug tool that returns the observed voxel grid using agent-relative coordinates. It helps inspect the local environment around an agent and verify coordinate and occupancy conventions. Use it during development and testing to visualize what the agent perceives and how grid cells are reported.

How this skill works

The skill samples a cubic voxel region around the agent and returns both a human-readable text grid and a structured data object. Output includes the absolute center pose (x, y, z, yaw), the requested radius, and a list of cells with agent-relative coordinates (dx, dy, dz) plus occupancy fields: solid, block_id, and support. Invoke the skill directly with an optional radius parameter (default 2).

When to use it

• Verify agent-relative coordinate mapping (dx = right/left, dz = forward/back).
• Inspect local occupancy to debug pathfinding or collision logic.
• Validate perception or voxelization outputs during environment changes.
• Confirm block IDs and support flags for physics/placement rules.
• Quickly visualize the immediate surroundings while developing agents.

Best practices

• Start with a small radius (2–4) to keep output readable during iteration.
• Compare the formatted text grid with the structured cells list to detect mapping errors.
• Use consistent agent poses when reproducing bugs so center and yaw remain stable.
• Log outputs alongside timestamps and agent state for traceability.
• Avoid relying on this tool in production planners; use it for debugging only.

Example use cases

• Run before and after a perception change to confirm voxelization updates correctly.
• Check that forward/back and right/left axes match simulation conventions when integrating new sensors.
• Diagnose unexpected collisions by examining which cells report solid=true nearby.
• Confirm support flags under blocks before attempting placement or removal actions.

FAQ