cli-anything-renderdoc

Analyze RenderDoc .rdc captures and export pipeline state, shaders, and resources.

Updated May 7, 2026
One-click install
npx skills add https://github.com/dawsonblock/JUDGE_ATLAS --skill cli-anything-renderdoc-dawsonblock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-anything-renderdoc
Source: https://github.com/dawsonblock/JUDGE_ATLAS/tree/main/external/CLI-Anything-main/skills/cli-anything-renderdoc
Command: npx skills add https://github.com/dawsonblock/JUDGE_ATLAS --skill cli-anything-renderdoc-dawsonblock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

RenderDoc .rdc captures are hard to inspect manually, so this Skill automates headless analysis and export of GPU frame capture details into usable artifacts and machine-readable outputs.

Core Features & Use Cases

  • Capture inspection: Read capture metadata and enumerate sections for quick triage of what was captured.
  • Action tree exploration: List, filter/search, and summarize actions such as draw calls, dispatches, and clears to understand rendering flow.
  • Texture and resource export: Inspect textures/resources and export images (e.g., PNG/JPG/DDS/HDR/EXR) or read buffer contents for debugging and reporting.
  • Pipeline and shader analysis: Extract pipeline state at a given event and export shader code (or disassembly) plus constant buffer data for diagnosis.
  • Action-to-state comparisons: Diff pipeline state between two events or captures and generate JSON outputs for regression investigations.
  • Use Case: When a visual regression happens, you can compare pipeline state between the failing and expected events and export the exact shader and texture outputs that changed to pinpoint the cause.

Quick Start

Run cli-anything-renderdoc to analyze a capture and export a thumbnail: cli-anything-renderdoc -c frame.rdc capture thumb -o thumb.png.

Frequently Asked Questions about cli-anything-renderdoc

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

FAQPage Schema
How do I inspect a RenderDoc capture file and export GPU pipeline state to JSON?

To inspect a RenderDoc capture, you can parse the `.rdc` file headlessly to extract metadata, enumerate sections, and export pipeline state, shaders, and resources into machine-readable JSON outputs for offline debugging.

Can I export textures and shaders from an .rdc capture for a specific event ID?

Yes, you can target specific event IDs within an `.rdc` capture to export textures as PNG, JPG, DDS, or EXR images, and extract shader code or disassembly alongside constant buffer data for detailed diagnosis.

What's the best way to diff pipeline state between two RenderDoc events for visual regression debugging?

Diffing pipeline state between two events involves comparing the failing and expected draw calls within the `.rdc` capture, generating a JSON output that highlights state changes to pinpoint visual regression causes.

Does headless RenderDoc analysis require a Python CLI with specific bindings?

Headless RenderDoc analysis requires a Python CLI environment utilizing RenderDoc bindings, along with Click and prompt-toolkit dependencies, to execute capture, action, pipeline, and resource subcommands without a GUI.

How do I list and filter draw calls in an .rdc file for offline rendering flow analysis?

You can explore the action tree of an `.rdc` capture to list, filter, and summarize actions such as draw calls, dispatches, and clears, allowing you to understand the rendering flow completely offline.