How do I install the Vcr Debugger skill?

Run npx skillmds@latest add tomevault-io/vcr-debugger in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Vcr Debugger safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Vcr Debugger?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Vcr Debugger free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Vcr Debugger?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Vcr Debugger by tomevault-io — Agent Skill

Name: Vcr Debugger
Author: tomevault-io

Vcr Debugger

Diagnose and fix VCR manifest/render failures. Use when `vcr check`, `vcr lint`, `vcr preview`, `vcr render-frame`, or `vcr build` fail; when output is blank/incorrect; or when determinism and backend behavior must be investigated. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

VCR Debugger

Debug VCR failures quickly with a deterministic triage sequence.

Triage Sequence

Validate manifest shape and references:
- vcr check <scene>.vcr
- vcr lint <scene>.vcr
Inspect frame-level state:
- vcr dump <scene>.vcr --frame <n>
Reproduce with a single frame:
- vcr render-frame <scene>.vcr --frame <n> -o renders/debug_f<n>.png
Verify runtime/dependency health:
- vcr doctor
If determinism is in question:
- vcr determinism-report <scene>.vcr --frame <n> --json

Debug Heuristics

Start with check before any expensive render.
Prefer minimal frame repro (render-frame) over full build during debugging.
Isolate params and disable optional complexity (post/shaders) when narrowing root cause.
Confirm backend assumptions for GPU-only features.

Common Root Causes

Schema/key typos (deny_unknown_fields).
Missing required environment fields.
Invalid expression functions/variables.
Invalid or out-of-scope asset paths.
GPU-only features executed on software backend.

Success Criteria

Reproducible root cause identified.
Error state removed (check passes).
Target frame or preview matches expected visual behavior.

Failure Handling

If failing command output is unclear, rerun on reduced scene complexity.
If render mismatch persists, compare with a known-good minimal manifest.
If backend-specific behavior diverges, document backend + platform in repro notes.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: vcr-debuggerdescription: Diagnose and fix VCR manifest/render failures. Use when `vcr check`, `vcr lint`, `vcr preview`, `vcr render-frame`, or `vcr build` fail; when output is blank/incorrect; or when determinism and backend behavior must be investigated. Use when this capability is needed.---# VCR DebuggerDebug VCR failures quickly with a deterministic triage sequence.## Triage Sequence1. Validate manifest shape and references: - `vcr check <scene>.vcr` - `vcr lint <scene>.vcr`2. Inspect frame-level state: - `vcr dump <scene>.vcr --frame <n>`3. Reproduce with a single frame: - `vcr render-frame <scene>.vcr --frame <n> -o renders/debug_f<n>.png`4. Verify runtime/dependency health: - `vcr doctor`5. If determinism is in question: - `vcr determinism-report <scene>.vcr --frame <n> --json`## Debug Heuristics- Start with `check` before any expensive render.- Prefer minimal frame repro (`render-frame`) over full build during debugging.- Isolate params and disable optional complexity (post/shaders) when narrowing root cause.- Confirm backend assumptions for GPU-only features.## Common Root Causes- Schema/key typos (`deny_unknown_fields`).- Missing required environment fields.- Invalid expression functions/variables.- Invalid or out-of-scope asset paths.- GPU-only features executed on software backend.## Success Criteria- Reproducible root cause identified.- Error state removed (`check` passes).- Target frame or preview matches expected visual behavior.## Failure Handling- If failing command output is unclear, rerun on reduced scene complexity.- If render mismatch persists, compare with a known-good minimal manifest.- If backend-specific behavior diverges, document backend + platform in repro notes.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/coltonbatts) — claim your Tome and manage your conversions.

Frequently asked questions