add-fusion-transformation

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

Quality

73%

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

75%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-structured, instruction-only workflow with a concrete repository layout, specific API guidance, and a properly sequenced 7-step process ending in validation. The main gaps are the absence of executable build/test commands and a stray closing code fence at the end of the file, plus mild redundancy in the Scope section.

Suggestions

Add the concrete commands to build and run the transformation tests (e.g., the test binary invocation with a --gtest_filter example) so step 5's validation is operationalized.

Remove the stray unmatched ``` fence at the very end of the file and tighten the duplicated decomposition rationale in the Scope section to one statement.

Consider moving the test-writing checklist and design recommendations into a references/ file if the skill grows, keeping SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is tight bullet-style instruction with no re-explanation of concepts Claude already knows, but it has minor redundancy: the decomposition rationale is stated twice in Scope ("Purpose: enablement prerequisite" and "Decomposition is the first thing to evaluate..."), and Notes/Recommendations partially repeat workflow steps. It is efficient with minor trimmable instances — anchor 4 — rather than anchor 5 where every token earns its place.	4 / 5
Actionability	Guidance is concrete for an instruction-only skill: an exact repository layout tree ("src/common/transformations/... <domain>/<fusion_name>.cpp"), specific API choices ("Prefer `ov::pass::MatcherPass`... use `GraphRewrite` only when..."), and explicit test categories. It is not a 5 because there are no executable commands (e.g., how to build and run the transformation tests) or a minimal matcher skeleton to copy.	4 / 5
Workflow Clarity	A clear 7-step sequence with an explicit validation step (step 7: determinism, idempotence, no duplicate matcher registration, and a required status report) and positive/negative test gates in step 5. It falls short of anchor 5 because the validation checkpoints are described but not operationalized — no build/test command is given, so the loop from "tests fail" back to "fix" is implicit.	4 / 5
Progressive Disclosure	The skill is a single well-sectioned file (Goal, Scope, Architecture, layout, 7-step workflow, Recommendations, Notes) with no bundle files and no nested references, so there is no navigation debt. It is not a 5 because at ~135 lines it exceeds the simple-skill threshold and some material (e.g., the test-writing checklist or design recommendations) could be split into a reference file; it is not a 3 because nothing is buried and no separate-file content is inappropriately inline.	4 / 5
	Total	16 / 20 Passed

Description

57%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 concise, third-person description that clearly identifies a narrow, distinctive niche, but it is missing an explicit "when to use" clause and common trigger synonyms (pass, pattern, graph rewrite). Adding a Use-when clause would raise completeness, and slight expansion of the action list would improve specificity.

Suggestions

Add an explicit trigger clause, e.g. "Use when adding or extending an OpenVINO graph fusion pass, matcher pattern, or subgraph replacement in openvino/src/common/transformations/."

Include natural synonyms developers actually say — "pass", "pattern", "graph fusion", "matcher" — so the description matches phrasing like "add a fusion pass" or "pattern-based optimization".

Optionally mention pass registration and test coverage as distinct actions to round out the what (e.g. "...registers the pass in the optimization pipeline and adds positive/negative tests").

Dimension	Reasoning	Score
Specificity	The description names the domain ("OpenVINO fusion transformation") and two concrete actions — "(subgraph to one or several operations)" and "corresponding tests" — but stops there, omitting other covered actions like pass registration and pipeline placement. It matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) rather than anchor 4, which expects several listed actions.	3 / 5
Completeness	The "what" is clear ("Adds a new OpenVINO fusion transformation ... and corresponding tests"), but there is no "Use when..." clause or equivalent trigger guidance, so completeness is capped at 3 per the judging guidelines. It is not a 2 because the "what" is explicit and specific rather than vague.	3 / 5
Trigger Term Quality	Relevant natural terms are present ("OpenVINO", "fusion transformation", "subgraph", "tests"), but common variations a developer would actually say — "pass", "pattern", "graph rewrite", "fuse", "optimization" — are missing. This sits between anchor 3 (relevant keywords, missing variations) and anchor 4, closer to 3 given the synonym gaps.	3 / 5
Distinctiveness Conflict Risk	The phrase "OpenVINO fusion transformation (subgraph to one or several operations)" carves out a clear niche with distinct triggers; it would not plausibly fire for unrelated skills. This matches anchor 5 (clear niche with distinct triggers, minimal conflict risk) rather than anchor 4, which implies residual overlap with closely related skills.	5 / 5
	Total	14 / 20 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: 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.