cli-anything-renderdoc

Analyze RenderDoc .rdc captures headlessly to inspect frames, shaders, and resources.

1|Updated Jun 13, 2025
One-click install
npx skills add https://github.com/quazfenton/binG --skill cli-anything-renderdoc-quazfenton
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cli-anything-renderdoc
Source: https://github.com/quazfenton/binG/tree/main/.agents/skills/CLI-Anything-main/CLI-Anything-main/skills/cli-anything-renderdoc
Command: npx skills add https://github.com/quazfenton/binG --skill cli-anything-renderdoc-quazfenton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This CLI harness provides headless RenderDoc capture analysis to quickly inspect GPU frame data without a GUI, enabling fast debugging and verification.

Core Features & Use Cases

  • Metadata extraction: retrieve capture metadata, sections, and thumbnails.
  • Action inspection: enumerate and filter draw calls, clears, and markers.
  • Texture and shader analysis: export textures and view shader state for debugging and optimization.
  • Use Case: in a CI pipeline, automatically verify frame integrity and capture completeness across builds.

Quick Start

Run cli-anything-renderdoc -c frame.rdc capture info to inspect a capture's metadata and sections.

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 captures from the command line?▼

You can analyze RenderDoc captures from the command line by running a headless CLI harness to inspect frames, shaders, and resources in .rdc files without needing a GUI.

Can I inspect GPU shaders and textures in a CI pipeline?▼

Yes, you can inspect GPU shaders and textures in a CI pipeline by automating headless capture analysis to verify frame integrity and capture completeness across builds.

What is headless GPU frame analysis used for?▼

Headless GPU frame analysis is used to extract capture metadata, enumerate draw calls, and export textures for fast debugging and optimization without launching a graphical interface.

How do I enumerate draw calls and clear markers in a .rdc file?▼

To enumerate draw calls and clear markers in a .rdc file, use the action inspection command group to filter and list frame actions within your capture.

Do I need RenderDoc Python bindings to extract capture metadata?▼

Yes, RenderDoc Python bindings are required as the underlying dependency to parse .rdc files and extract capture metadata, sections, and thumbnails programmatically.

Can I view shader state and pipeline resources without opening the RenderDoc GUI?▼

You can view shader state and pipeline resources without the GUI by executing CLI commands for pipeline and resource inspection to debug headless environments.