ov-debug
Troubleshooting all sorts of failures, crashes, exceptions and errors using debug capabilities. Analyze accuracy, performance, model compilation, or memory issues. Dump tensors and intermediate blobs. Serialize and visualize IRs, execution graphs. Enable verbose, logging. Profile execution. Compare layer outputs. Inspect, trace or dump transformations. Identify executed operations, nodes, primitives, kernels.
55
62%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/ov-debug/SKILL.mdDebug Skill
Prerequisites
Build flags that enable debug capabilities (check CMakeCache.txt in the build dir):
-DENABLE_DEBUG_CAPS=ON— CPU/GPU plugin debug env vars, transformation matcher logging
Components
| Component | Reference file to read | Routing hints |
|---|---|---|
| openvino_intel_cpu_plugin | @components/debug-intel-cpu-plugin.md | CPU: inference issues, wrong results, slow inference, tensor dumps, execution graphs |
| openvino_intel_gpu_plugin | @components/debug-intel-gpu-plugin.md | GPU: inference issues, wrong results, slow inference, tensor dumps, execution graphs |
| transformations | @components/debug-transformations.md | transformation not applied, pass not firing, slow compilation, graph inspection |
Steps
- Match the user's symptom to the routing hints above to identify the component(s)
- Load the component's reference file
- Follow the instructions and recommendations for debugging
- Repository
- openvinotoolkit/openvino
- Commit
4c20980
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.