cli-anything-renderdoc

Inspect RenderDoc GPU captures and export resources via command-line tools.

46.8k|4.4k|Updated Mar 8, 2026

Search Tags:#performance #debugging #gpu #shader #renderdoc #capture analysis

Ready to run

npx skills add https://github.com/HKUDS/CLI-Anything --skill cli-anything-renderdoc-hkuds

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cli-anything-renderdoc
Source: https://github.com/HKUDS/CLI-Anything/tree/main/skills/cli-anything-renderdoc
Command: npx skills add https://github.com/HKUDS/CLI-Anything --skill cli-anything-renderdoc-hkuds

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill enables headless, command-line analysis of RenderDoc GPU frame captures, simplifying graphics debugging and performance inspection.

Core Features & Use Cases

Capture Inspection: Access metadata, sections, and generate thumbnails of capture files.
Action Tree Navigation: List, filter, and search GPU draw calls and actions within captures.
Texture and Resource Analysis: Export textures, inspect buffers, and read resource data.
Pipeline State and Shader Analysis: Examine pipeline configurations, export shaders, and compare states across events.

Quick Start

Use this Skill to analyze a GPU capture file by listing all actions within the capture.

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 GPU capture files from the command line for graphics debugging?▼

GPU capture inspection via the command line allows you to access metadata, sections, and generate thumbnails of capture files. This headless approach simplifies graphics debugging by enabling detailed action tree navigation and texture analysis without a GUI.

Can I automate RenderDoc capture analysis using JSON output?▼

RenderDoc capture analysis supports JSON output to facilitate automation. By providing command-line tools for pipeline state queries and resource export, you can script and automate the inspection of GPU draw calls and shader configurations.

How do I extract textures and examine pipeline states in a RenderDoc capture?▼

To extract textures and examine pipeline states, you can use command-line tools to inspect buffers, read resource data, and compare pipeline configurations across events. This allows detailed analysis of graphics APIs and shader formats.

Do I need RenderDoc installed to perform headless GPU frame analysis?▼

Yes, RenderDoc is a required dependency for performing headless GPU frame analysis. The Skill provides command-line tools that rely on RenderDoc to inspect captures, export shaders, and query resource data across multiple graphics APIs.

What is the best way to filter GPU draw calls and navigate the action tree in a capture?▼

Action tree navigation is best handled by using command-line tools to list, filter, and search GPU draw calls within captures. This approach allows you to pinpoint specific actions and inspect pipeline configurations efficiently.

Are there limitations when using command-line tools for GPU capture inspection compared to the GUI?▼

Command-line GPU capture inspection focuses on headless analysis, texture export, and resource queries with JSON output. While it enables automation, it lacks the interactive visual debugging capabilities inherent to the standard GUI workflow.