Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Bounding Boxes

ASecurity

Gets actor and level 3D bounding boxes and projects them into a camera image as 2D boxes — the dataset-annotation workflow. Lists box geometry, draws 3D boxes in the world via debug, or captures one camera frame and writes an annotated PNG plus a JSON of 2D boxes for matching actors. Use when the user asks to "get bounding boxes", "draw boxes around the cars", "project boxes onto the camera", or "generate a detection dataset / annotations".

14,461 stars
0 votes
0 copies
0 views
Added 10/6/2026
ai-agentspythongobashawsapi

Works with

cliapi

Security Analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned 10/6/2026

$npx -y skills add carla-simulator/carla --skill bounding-boxes --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Bounding Boxes?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Bounding Boxes
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/carla-simulator-bounding-boxes-carla/badge)](https://www.skillsdirectory.com/skills/carla-simulator-bounding-boxes-carla)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: bounding-boxes
description: Gets actor and level 3D bounding boxes and projects them into a camera image as 2D boxes — the dataset-annotation workflow. Lists box geometry, draws 3D boxes in the world via debug, or captures one camera frame and writes an annotated PNG plus a JSON of 2D boxes for matching actors. Use when the user asks to "get bounding boxes", "draw boxes around the cars", "project boxes onto the camera", or "generate a detection dataset / annotations".
license: MIT
compatibility: Any OS with the CARLA PythonAPI + numpy (cv2 for drawing) installed for the active interpreter and a reachable, already-running CARLA server. `project` needs an RGB camera (create-sensor). Does NOT need UE4_ROOT. Tested against CARLA 0.9.16.
metadata:
  group: python-api
  requires: create-sensor
  prerequisites: scripts/check_env.sh
  reference: references/bounding-boxes.md
---

# Bounding boxes

> **Paths.** `scripts/…` and `references/…` below are relative to the
> directory holding this SKILL.md. Your working directory is the user's
> project, not that directory, so prefix them with its absolute path or the
> command is not found.

Three things: read actors' 3D boxes, draw them in the world, or **project** them
into a camera image as 2D boxes with a JSON sidecar — the standard CARLA
dataset-annotation pipeline (`client_bounding_boxes.py`).

## Instructions

```
Progress:
- [ ] Step 1: Check prerequisites (bash scripts/check_env.sh), clear FAILs
- [ ] Step 2: For `project`, have a camera on the ego (create-sensor) + actors around
- [ ] Step 3: list / draw / project
```

Commands need `CARLA_HOST`/`CARLA_PORT` from `scripts/env.sh`.

### Step 1: Check prerequisites

```bash
bash scripts/check_env.sh
```

### Step 3: Boxes

```bash
source scripts/env.sh

# 3D box geometry of every vehicle
python3 scripts/bounding_boxes.py list --filter vehicle.*

# draw 3D boxes around vehicles — they track moving cars, stay 30 s (default)
python3 scripts/bounding_boxes.py draw --filter vehicle.*
python3 scripts/bounding_boxes.py draw --filter vehicle.* --seconds 60

# project vehicle boxes into a camera frame -> annotated PNG + JSON
python3 scripts/bounding_boxes.py project --camera <camera_id> --filter vehicle.* --out boxes.png
```

## How the projection works (brief)

Capture one frame → build the camera intrinsics `K` from its `fov` + resolution →
for each actor, take its 3D box's 8 world vertices (`get_world_vertices`),
transform to camera space with the camera's inverse matrix, keep those in front,
apply `K` → 2D points → the min/max is the 2D box. Off-frame and too-far
(`--max-dist`) actors are skipped. Full math in the reference.

## Examples

**Example 1: annotate the ego camera**

User says: "put boxes on the cars in the camera view"

Spawn a camera on the ego (create-sensor), then `project --camera <id>
--filter vehicle.*` → `boxes.png` with green 2D boxes + `boxes.json`.

**Example 2: how big is that actor**

User says: "what are the dimensions of vehicle 137?"

`list --filter vehicle.*` (find 137) → its LxWxH from the extent.

**Example 3: visualise in 3D**

User says: "outline all the vehicles in the world"

`draw --filter vehicle.*` — green 3D boxes on a rendered server.

## Troubleshooting

**Problem: `project` finds no boxes**
Cause: no actors in front of / within `--max-dist` of the camera, or wrong filter.
Solution: raise `--max-dist`, widen `--filter`, ensure vehicles are in view.

**Problem: boxes misaligned**
Cause: the frame and the actor poses drifted (fast motion, async).
Solution: capture in synchronous mode (set-world-settings) so the frame and poses
are from the same tick.

**Problem: `draw` shows nothing**
Cause: headless `-nullrhi` server.
Solution: use a rendered server (see debug-draw).

**Note: boxes always track moving actors**
`draw` re-stamps each frame for `--seconds` (default 30), so boxes ride moving
cars automatically — the command blocks for that duration.

## Outputs

- `list`: box dimensions per actor.
- `draw`: 3D box overlay (rendered view).
- `project`: `<out>.png` (annotated) + `<out>.json` (2D boxes: id, type, xyxy).

Detail (intrinsics, world→camera transform, level boxes, lidar-to-camera) in
[references/bounding-boxes.md](references/bounding-boxes.md).

Attribution

carla-simulatorcarla-simulator
View sourceSee grades on GitHubMore from carla-simulator →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →