ov-debug

Debug OpenVINO CPU/GPU plugin inference, accuracy, performance, memory, and device compilation issues, or inspect graph transformations, using debug capabilities such as tensor dumps, execution graphs, profiling, and transformation tracing. Do NOT use for frontend model conversion failures (unsupported operators, translation errors, or source-model loading), build/configuration failures, or generic test/CI failures.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, well-structured router skill with a clear prerequisite, symptom-based routing table, and unambiguous workflow. Its critical weakness is that every referenced component file is absent from the bundle, breaking the progressive-disclosure chain, and the body itself carries no executable debug commands as a fallback.

Suggestions

Ship the three referenced component files in the bundle (components/debug-intel-cpu-plugin.md, debug-intel-gpu-plugin.md, debug-transformations.md), or fix the paths if they live elsewhere — currently all three links are dead.

Include one or two representative debug commands or environment variables inline (e.g., a key OV_* dump or profiling env var) so the skill retains actionable value even before a component file is loaded.

Trim the Scope sentence 'Frontend conversion failures are outside its scope; use an applicable frontend skill or investigate the frontend directly', which restates the exclusions already in the frontmatter description.

Dimension	Reasoning	Score
Conciseness	The ~27-line body is lean with every section earning its place: a short scope clarification, one concrete build prerequisite, a routing table, and three steps. The Scope paragraph is disambiguation ('Device compilation here means compiling an OpenVINO model for CPU/GPU execution, not converting a source model into OpenVINO IR'), not padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Concrete, executable details are present: the exact build flag '-DENABLE_DEBUG_CAPS=ON' with where to verify it ('check CMakeCache.txt in the build dir') and explicit per-component file paths. However, no actual debug command, environment variable, or example appears in the body itself — all executable debugging detail is deferred to the component files, leaving minor gaps.	4 / 5
Workflow Clarity	The three-step routing workflow (match symptom to routing hints → load the component's reference file → follow its instructions) is unambiguous and well sequenced. This is a simple router skill with no destructive or batch operations, so the validation cap does not apply and the simple-skill exception fits.	5 / 5
Progressive Disclosure	The in-body structure is well designed — a clear components table with one-level-deep, clearly signaled references and symptom-based routing hints — but all three referenced files (components/debug-intel-cpu-plugin.md, components/debug-intel-gpu-plugin.md, components/debug-transformations.md) are missing from the bundle (verified by file listing), so navigation fails at the first hop and the disclosure chain is broken.	3 / 5
	Total	17 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with concrete capability enumeration and explicit boundary exclusions that minimize conflict risk. Its main gap is the absence of a positive 'Use when...' trigger clause and a few natural user phrasings, leaving the 'when' guidance implicit on the positive side.

Suggestions

Add an explicit positive trigger clause, e.g., 'Use when debugging OpenVINO CPU/GPU plugin runtime issues (wrong results, slow inference, memory problems, device compilation errors) or investigating graph transformation behavior.'

Include common user phrasings as triggers — 'wrong output/results', 'slow inference', 'model hang or crash on CPU/GPU' — to complement the existing technical terms.

Mention the artifacts users typically reference (OpenVINO IR/.xml files, specific plugin names) to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'Debug OpenVINO CPU/GPU plugin inference, accuracy, performance, memory, and device compilation issues, or inspect graph transformations, using debug capabilities such as tensor dumps, execution graphs, profiling, and transformation tracing' — giving comprehensive, specific coverage of the skill's capabilities rather than vague domain naming.	5 / 5
Completeness	The 'what' is explicit and concrete, and 'when' is addressed through explicit negative trigger guidance ('Do NOT use for frontend model conversion failures..., build/configuration failures, or generic test/CI failures'). However, there is no positive 'Use when...' clause, so the trigger guidance could be more direct.	4 / 5
Trigger Term Quality	Natural trigger terms like 'inference', 'accuracy', 'performance', 'memory', 'tensor dumps', 'execution graphs', and 'profiling' are present, matching what users would say. A few common user phrasings are missing (e.g., 'wrong output', 'slow model', IR/.xml file mentions), so coverage is good but not comprehensive.	4 / 5
Distinctiveness Conflict Risk	The niche is clearly staked out (OpenVINO CPU/GPU plugin runtime debugging and graph transformations) and the explicit exclusions for frontend conversion, build/configuration, and generic CI failures sharply reduce overlap with adjacent skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 3 missing	Warning

	Total	15 / 16 Passed

Repository: openvinotoolkit/openvino
Path: .claude/skills/ov-debug/SKILL.md
Commit: f766feb

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.