add-fusion-transformation

Adds a new OpenVINO fusion transformation (subgraph to one or several operations) and corresponding tests.

Quality

71%

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-fusion-transformation/SKILL.md

Quality

Content

85%

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

The content is concise, well-structured, and offers a clear validated workflow with concrete API and layout references, but as an instruction-only skill it stops short of executable code templates, leaving actionability at the mid level.

Suggestions

Add one minimal copy-paste-ready skeleton (e.g., a MatcherPass class header/source template with the predicate and `transform()` stub) to move actionability from directive prose toward the executable anchor.

Show a concrete test snippet illustrating positive vs negative assertion patterns against a reference graph, so the testing step is fully actionable.

Optionally include the exact registration-line convention (the pipeline file and how the pass is added) so step 4 is copy-paste ready rather than descriptive.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: terse bullet directives with no padding explaining what OpenVINO or fusion is, matching the 'lean and efficient; every token earns its place' anchor rather than the level-2 'could be tightened' case.	3 / 3
Actionability	It gives concrete, specific guidance (named APIs like `ov::pass::MatcherPass`, `GraphRewrite`, `rt_info`, plus a concrete repo layout), but provides no executable code/commands or copy-paste-ready templates — only directive prose — fitting the 'some concrete guidance but incomplete; missing key details' anchor.	2 / 3
Workflow Clarity	A clearly sequenced 7-step workflow with explicit validation (dedup check in step 1, positive/negative tests in step 5, idempotency/no-duplicate-registration checks in step 7) and an error-recovery reporting loop (fully/partially/blocked), matching the 'clear sequence with explicit validation steps and feedback loops' anchor.	3 / 3
Progressive Disclosure	A single, well-sectioned instruction-only file (Goal, Scope, Architecture, Layout, Workflow, Recommendations, Notes) with no bundle files and no nested multi-level references, which is appropriate and well-organized for this scope per the simple/instruction-only skill guideline.	3 / 3
	Total	11 / 12 Passed

Description

57%

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 clearly states what the skill does within a distinct OpenVINO niche, but it omits any explicit 'use when' trigger guidance and leans on technical jargon over natural trigger terms, which caps completeness and trigger-term quality at the mid level.

Suggestions

Add an explicit 'Use when ...' clause naming natural triggers, e.g. 'Use when the user asks to fuse or optimize an OpenVINO subgraph into a single op or compact op sequence, or to add a new transformation pass.'

Include common user-facing phrasings alongside the jargon (e.g., 'graph fusion', 'op fusion', 'transformation pass') so trigger-term quality reaches the natural-terms anchor.

Optionally enumerate a couple more concrete actions (e.g., 'register the pass in the optimization pipeline, add positive and negative regression tests') to push specificity toward the comprehensive anchor.

Dimension	Reasoning	Score
Specificity	Names the OpenVINO domain and concrete actions ('subgraph to one or several operations' and 'corresponding tests'), but the action list is short rather than a comprehensive enumeration of multiple distinct concrete operations, matching the 'names domain and some actions but not comprehensive' anchor.	2 / 3
Completeness	It clearly answers 'what does this do' (adds a fusion transformation and tests) but provides no 'when should Claude use it' / 'Use when' clause, so 'when' is entirely missing — explicitly capping completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Contains relevant domain keywords ('fusion transformation', 'subgraph') but uses technical jargon rather than natural phrasings a user would actually say, and offers no common variations — fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The OpenVINO fusion-transformation niche is specific and unlikely to trigger for unrelated skills, matching the 'clear niche with distinct triggers; unlikely to conflict' anchor rather than the somewhat-generic level 2.	3 / 3
	Total	9 / 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-fusion-transformation/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.