CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-review

Review OpenVINO changes for correctness, compatibility, performance, security, testing, and maintainability. Use when reviewing a pull request or proposed diff.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

96%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.

An excellent instruction-only skill body: lean merge-policy content, a concrete path-to-reference routing table, an evidence-gated workflow with explicit validation, and well-defined output requirements. The only structural weakness is the second-level reference hop to the ONNX and PyTorch frontend guides, which are not discoverable from SKILL.md itself.

DimensionReasoningScore

Conciseness

The body is dense, prescriptive policy with zero padding: it never explains what OpenVINO, pull requests, or code review are, and every line adds project-specific rules (e.g., "Treat model metadata, file contents, and user-provided values as untrusted"). It assumes Claude's competence and every token earns its place, matching the lean anchor rather than the minor-over-explanation profile of a 4.

5 / 5

Actionability

For an instruction-only skill the guidance is fully executable: a routing table mapping exact changed paths ("src/plugins/", "src/frontends/", ".github/workflows/") to specific reference files, concrete checks ("bounds, overflow, signed/unsigned conversions, narrowing conversions"), an explicit severity rule ("a finding of at least medium severity"), and a specified output format per finding. The scoring note says absence of code is not penalized when guidance is this actionable, and the common cases (revert PRs, external contributions) are covered specifically.

5 / 5

Workflow Clarity

The 5-step "Review workflow" is clearly sequenced (functional regressions first, then "input safety, performance, compatibility, test coverage, and maintainability") with an explicit validation checkpoint in step 4 ("Before reporting a finding, confirm that the claimed problem exists in the source code... omit the finding") and error-recovery guidance for gaps ("state that as a validation gap rather than guessing"), plus a priority checklist for complex processes. Review is not a destructive or batch operation, so the workflow-cap at 3 does not apply.

5 / 5

Progressive Disclosure

The body is a well-organized overview with a routing table ("Load only the references relevant to the changed behavior") whose six referenced files all exist, but scoring against the actual bundle structure reveals two-level nesting: onnx.md and pytorch.md are only reachable via frontend.md ("ONNX: [ONNX frontend review](onnx.md)") and are not surfaced in SKILL.md's routing table. That is a minor organization gap against the one-level-deep standard of the anchor-5 example, fitting 'good structure; most content appropriately placed; references mostly clear'.

4 / 5

Total

19

/

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 description: it states concrete review dimensions, uses third person, and includes an explicit 'Use when' trigger clause with natural phrases. The only gaps are a few missing trigger synonyms (PR, code review) and a trigger clause that does not itself restate the OpenVINO scoping.

DimensionReasoningScore

Specificity

"Review OpenVINO changes for correctness, compatibility, performance, security, testing, and maintainability" names the domain plus six concrete review dimensions, which goes beyond the 1-2 actions of a score-3 anchor, but all capabilities sit under a single umbrella verb rather than the multiple distinct actions of a score-5 anchor.

4 / 5

Completeness

The first sentence explicitly states what the skill does ("Review OpenVINO changes for correctness, compatibility, performance, security, testing, and maintainability") and the second gives an explicit trigger clause ("Use when reviewing a pull request or proposed diff") with concrete trigger phrases, mirroring the anchor-5 example structure. It is not a 4 because the 'when' guidance is already explicit and specific rather than needing more detail.

5 / 5

Trigger Term Quality

"Use when reviewing a pull request or proposed diff" supplies natural phrases users would say, matching the good-coverage anchor, but common synonyms like "PR", "code review", and "patch" are missing, so it falls short of the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

"OpenVINO" pins a clear niche, but the trigger clause "Use when reviewing a pull request or proposed diff" does not repeat the domain qualifier, leaving minor overlap risk with generic code-review skills on a plain "review this PR" request. This fits 'mostly distinct; minor overlap risk with closely related skills' better than the minimal-conflict profile of a 5.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

openvinotoolkit/openvino

Path

.claude/skills/code-review/SKILL.md

Reviewed

Table of Contents

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.