add-core-op

Adds a core operator to the OpenVINO toolkit. Use when asked to implement a new operation into OpenVINO.

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/agents-prototype/skills/add-core-op/SKILL.md

Quality

Content

80%

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

The content is highly actionable and concise, with concrete OpenVINO-specific code patterns and file locations throughout. Its weaker areas are the absence of explicit validation/feedback checkpoints in the workflow and the lack of any external reference files for the substantial reference-style content.

Suggestions

Add explicit validation checkpoints to the workflow (e.g., after implementation run the type_prop and visitor tests, fix and re-run until they pass, then confirm the opset count before writing the spec).

Move the file-path reference lists and the Core Op Class Pattern into a separate reference file (e.g., references/op-class-pattern.md) and link to it from SKILL.md so the overview stays lean.

Deduplicate the file paths (the "Files to create/update" section repeats paths already given in "Create Header and Source Files") and consolidate the redundant "High-level rules" opset guidance.

Dimension	Reasoning	Score
Conciseness	The body is lean, instructional, and assumes Claude's competence, with concrete paths and code patterns and no padding explaining OpenVINO or basic C++ concepts; the only minor tightening opportunity is a duplicated file-path listing, which is below the verbosity the level-2 anchor targets.	3 / 3
Actionability	It provides exact file paths, copy-paste-ready class and macro snippets (OPENVINO_OP, OV_OP_SCOPE), specific methods to implement, and concrete test directories, matching the fully-executable level-3 anchor.	3 / 3
Workflow Clarity	A 4-step workflow and per-step sections give a clear sequence, but there are no explicit validation checkpoints or feedback loops (e.g., run type_prop tests and confirm pass before writing the spec), leaving checkpoints implicit as the level-2 anchor describes.	2 / 3
Progressive Disclosure	With no bundle files present everything is inline in a ~130-line file; it is well-sectioned but contains reference-style material (file-path lists, the Core Op Class Pattern) that should be split into a separate reference file, matching the level-2 anchor.	2 / 3
	Total	10 / 12 Passed

Description

75%

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

The description is concise, third-person, and cleanly states both what the skill does and when to use it with a distinct OpenVINO-specific trigger. Its main weakness is single-phrasing trigger coverage and naming only one concrete action.

Suggestions

Add common trigger-term variations (e.g., "register a new op", "add an operation", "custom operator") to improve natural-keyword coverage.

Enumerate the concrete actions the skill covers (e.g., create the op class, implement shape inference and evaluate, add tests and spec) to lift specificity from one action to several.

Dimension	Reasoning	Score
Specificity	It names a concrete action and domain ("Adds a core operator to the OpenVINO toolkit") but lists only a single action rather than multiple specific concrete actions, matching the level-2 anchor.	2 / 3
Completeness	"Adds a core operator to the OpenVINO toolkit" states what it does and "Use when asked to implement a new operation into OpenVINO" gives an explicit when-trigger, clearly answering both what and when.	3 / 3
Trigger Term Quality	"asked to implement a new operation into OpenVINO" provides a relevant natural phrase and the specific domain term OpenVINO, but coverage is thin with only one phrasing and missing common variations, so it is not a 3.	2 / 3
Distinctiveness Conflict Risk	The OpenVINO core-operator niche has distinct, domain-specific triggers and is unlikely to fire for an unrelated skill, matching the level-3 anchor.	3 / 3
	Total	10 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openvinotoolkit/openvino
Path: .github/agents-prototype/skills/add-core-op/SKILL.md
Commit: 4c20980

Reviewed: 4 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.