# Debug A Graphics Problem > Enable an agent to debug graphics problems Use when this capability is needed. - Skill: `tomevault-io/debug-a-graphics-problem` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/debug-a-graphics-problem` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/debug-a-graphics-problem/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/debug-a-graphics-problem --- # Debug a graphics problem If you need to see what might be wrong with graphics, you can look at the debug file that ends in `.screen`. This file is the screen log. It records frames with a full copy of the graphics on screen in text form. These frames are sampled roughly once per second. Each dot on the screen is represented by a character in the frame. When debugging anything, several other files are helpful: - the metrics file (how many times certain events occur; ends in `.metrics`) - the instruction log (all instructions sorted by place in memory it was executed; file ends in `.asm`) - the timeset file (how much time each instruction took; ends in `.time`) --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/pevans) — claim your Tome and manage your conversions.