debug-operation

What problem does it solve?

This Skill helps you move from a vague “the Scene Optimizer op didn’t work” report to a concrete diagnosis when an operation errors, silently no-ops, or produces unexpected output.

Core Features & Use Cases

• Log-first triage workflow: Reproduce the failure with verbose logging and captured stats to ensure evidence is available for analysis.
• Targeted validation checks: Verify argument key correctness, confirm the operation key, and ensure the input stage actually contains the required prims for the op scope.
• Verbose + analysis-mode execution: Use execution context flags to observe what the operation would do without mutating the stage, when supported.
• Failure-pattern diagnosis: Apply structured tables for common hard-failure patterns (e.g., stage-cache issues, missing operation plugins, libusd mismatch) and silent no-op patterns (e.g., no matching prims, ineffective defaults).
• Operation-family gotchas: Use a cheat sheet for common issues across mesh, deduplication, analysis-only detection, material, and hierarchy operations.

Quick Start

Ask the agent to triage the failing Scene Optimizer operation by capturing a verbose run log first, then validating the argument keys and input stage prim matches before attempting analysis mode.