cli-anything-renderdoc

Analyze RenderDoc GPU frame captures via command-line inspection, export, and comparison.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/xxxxkkkqq/CineWeave --skill cli-anything-renderdoc-xxxxkkkqq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-anything-renderdoc
Source: https://github.com/xxxxkkkqq/CineWeave/tree/main/research/upstreams/CLI-Anything/renderdoc/agent-harness/cli_anything/renderdoc/skills
Command: npx skills add https://github.com/xxxxkkkqq/CineWeave --skill cli-anything-renderdoc-xxxxkkkqq

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies the process of analyzing RenderDoc GPU frame captures by providing a headless, command-line interface for inspecting, exporting, and comparing GPU rendering data.

Core Features & Use Cases

  • Capture Inspection: View metadata, sections, and thumbnails of GPU captures.
  • Action Tree Analysis: List, search, and filter draw calls and GPU actions.
  • Texture Operations: Inspect, export, and pick pixels from GPU textures.
  • Pipeline State Examination: Export and compare shader, viewport, and resource states.
  • Shader Analysis: Export shaders in human-readable or disassembled formats.
  • Resource and Mesh Inspection: Read buffer data and decode mesh inputs/outputs.
  • Counter Monitoring: Enumerate and fetch hardware performance counters.

Quick Start

To analyze a GPU capture, run the command with your capture file and specify the desired action, such as listing actions or exporting shaders.

Frequently Asked Questions about cli-anything-renderdoc

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

FAQPage Schema
How do I analyze RenderDoc GPU captures from the command line?

You can analyze RenderDoc GPU captures from the command line by using this skill to inspect metadata, list draw calls, export shaders, and compare pipeline states headlessly without launching the GUI.

Can I export GPU textures and shaders without opening the RenderDoc interface?

Yes, you can export GPU textures and shaders without the RenderDoc interface by running command-line commands to extract textures, pick pixels, and output shaders in human-readable or disassembled formats.

How do I search and filter specific draw calls in a GPU frame capture?

To search and filter draw calls in a GPU frame capture, use this skill's command-line action tree analysis features to list, search, and narrow down specific GPU actions for rendering diagnostics.

Do I need RenderDoc Python bindings to inspect pipeline state and mesh data?

Yes, you need RenderDoc Python bindings to inspect pipeline state and mesh data, as this skill relies on these bindings to read buffer data, decode mesh inputs, and examine viewport states.

What is the best way to compare GPU rendering states for optimization?

The best way to compare GPU rendering states for optimization is by using command-line tools to export and compare shader, viewport, and resource states across different frame captures.

How do I fetch hardware performance counters during GPU debugging?

You can fetch hardware performance counters during GPU debugging by running command-line commands that enumerate and retrieve counter data directly from your captured GPU frames.