CtrlK
BlogDocsLog inGet started
Tessl Logo

code-review

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

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 well-engineered review skill body: lean, project-specific, with a validated workflow, checklists, conditional review modes, and exemplary progressive disclosure through a changed-path-to-reference routing table. The only improvement space is adding a short example of a well-formed finding.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it contains no generic explanations of code review or OpenVINO basics, and every section adds project-specific policy (e.g., "Treat model metadata, file contents, and user-provided values as untrusted", revert-PR and external-contributor handling). It does not fit the 'minor instances of over-explanation' anchor below.

5 / 5

Actionability

Guidance is mostly executable and concrete — a numbered workflow, specific check items ("bounds, overflow, signed/unsigned conversions"), and an exact changed-path-to-reference table — but it provides no commands and no worked example of a formatted finding, so it falls between 'mostly executable with minor gaps' and fully copy-paste-ready guidance.

4 / 5

Workflow Clarity

The four-step review workflow is clearly sequenced with an explicit validation gate ("Before reporting a finding, confirm that the claimed problem exists in the source code... If the available evidence does not establish a defect, omit the finding"), plus a priority checklist, conditional modes, and an explicit no-findings output requirement. The skill is read-only, so the destructive/batch validation cap does not apply.

5 / 5

Progressive Disclosure

The body is a clean overview that routes detail to six one-level-deep, clearly linked reference files (all present in references/), with explicit instructions to "Load only the references relevant to the changed behavior" and to combine references for cross-boundary changes. All links resolve and none nest beyond one level.

5 / 5

Total

19

/

20

Passed

Description

92%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: concrete, domain-anchored, third-person, with an explicit 'Use when' clause covering pull requests and proposed diffs. The only gap is modest synonym coverage for common user phrasings.

DimensionReasoningScore

Specificity

"Review OpenVINO changes for correctness, compatibility, performance, security, testing, and maintainability" names the domain and comprehensively enumerates six concrete review dimensions, matching the comprehensive-coverage anchor rather than the 'minor gaps' anchor below it.

5 / 5

Completeness

The description explicitly answers both what ("Review OpenVINO changes for correctness, compatibility, performance, security, testing, and maintainability") and when ("Use when reviewing a pull request or proposed diff") with concrete trigger phrases, in third-person voice.

5 / 5

Trigger Term Quality

"pull request", "diff", "review", "security", and "performance" are natural user terms, but common synonyms such as "PR", "patch", "commit", or "code review" are missing, which fits the 'good keyword coverage; a few natural terms missing' anchor rather than comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"OpenVINO changes" pins a clear niche with distinct triggers; only minimal overlap risk exists with a generic code-review skill, matching the clear-niche anchor.

5 / 5

Total

19

/

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