world-data

Queries the live CARLA world to resolve actor descriptions into concrete actor ids.

3|Updated Jul 20, 2026
One-click install
npx skills add https://github.com/carla-simulator/carla-agentic-tools --skill world-data-carla-simulator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: world-data
Source: https://github.com/carla-simulator/carla-agentic-tools/tree/main/skills/python-api/world-data
Command: npx skills add https://github.com/carla-simulator/carla-agentic-tools --skill world-data-carla-simulator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires carla, and includes scripts (resource) and references (resource) components.

What problem does it solve? When working with a running CARLA simulation, requests like "the red prius" or "the nearest walker" are ambiguous — this Skill turns such descriptions into a concrete, stable actor id that other action skills (telemetry, control-vehicle, bounding-boxes) can act on, and also reads world-level data like snapshots, level bounding boxes, raycasts, and ROS 2 topic mappings. ## Core Features & Use Cases - Actor resolution: Find actors by type/blueprint filter, role, or color, or pick the single closest actor to a point or another actor with --nearest, yielding one stable id. - World queries: Read the world snapshot (frame/time/actor count), static level bounding boxes by CityObjectLabel, semantic raycast hits, and ground projection of a point. - ROS 2 topic diagnosis: List the native ROS 2 topics each actor should publish and explain why any expected topic is silent, without needing ROS 2 installed. - Use Case: A user asks "get the prius closest to my ego vehicle" — run actors --filter '*prius*' --near-id <ego> --nearest to get one id, then hand it to the telemetry skill. ## Quick Start Ask the agent to find the red prius in the running CARLA simulation and report its actor id.

Frequently Asked Questions about world-data

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

FAQPage Schema
How do I find a specific actor in a running CARLA simulation?▼

Use the actors command with stable attributes: filter by type pattern like --filter '*prius*', narrow by --role or --color, or take the single closest with --nearest plus --near or --near-id. The result is a stable actor id for other skills.

How to get the vehicle nearest to the ego in CARLA?▼

Run actors with --filter for the vehicle type, --near-id set to the ego actor id, and --nearest to return only the single closest match. Note the distance is a single-frame snapshot, so re-query for a fresh value as actors move.

Why is my CARLA ROS 2 topic missing or silent?▼

The ros-topics mode names three causes: the sensor was not enabled with enable_for_ros(), the sensor type has no native publisher, or the vehicle is not role_name hero. If even rt/clock is missing, the server was not built or started with ROS 2.

Does this work with CARLA 0.10.0 and the UE5 line?▼

Yes, actor queries are unchanged on the UE5 line, but rt/carla/map is not published there because CarlaMapPublisher was removed. The ros-topics mode detects the server version and tells you to read the map via map.to_opendrive() instead.

Why does the actor query return no matching actors?▼

The actor may be a traffic light, sign, or spectator, which are hidden by default — add --all to include them. Also verify the carla module imports and the server is reachable by running the check_env.sh prerequisite script.

Can I select the third vehicle in a CARLA actor list?▼

No, there is no rank or ordering among peer actors, so positional selection is not supported. Identify actors by stable attributes like id, type, role, or color, or use the --nearest spatial predicate instead.