# Renderdoc Analysis

> Domain skill — Inspect an existing RenderDoc capture and export its embedded thumbnail, Chrome trace, or drawcall texture resources. Use for offline graphics triage and automation artifacts. Not for launching a capture — use renderdoc-capture.

- Skill: `dcc-mcp/renderdoc-analysis` (Agent Skill, multi-file: 7 files)
- Install (CLI): `npx skillmds@latest add dcc-mcp/renderdoc-analysis`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dcc-mcp/renderdoc-analysis/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: dcc-mcp (https://skillmd.com/u/dcc-mcp)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/dcc-mcp/renderdoc-analysis

---


# RenderDoc Analysis

Inspect before exporting. These tools never modify the input `.rdc`; exports require an explicit
destination path and create its parent directory when needed.

Use `export_drawcall_resources` with an exact event ID to export only texture resources that the
pixel shader reports as used at that event. The result records binding, resource name, dimensions,
format, and output file for each PNG.

Inspection reports `draw_dispatch_count`, `frame_work_count`, `present_count`, and
`frame_content_status` so a structurally readable capture with no rendering work is not mistaken
for a usable frame.