CtrlK
BlogDocsLog inGet started
Tessl Logo

ov-gguf-enable-op

Enable a ggml operation in the OpenVINO GGUF frontend by adding or fixing an op translator. Use when conversion fails with "Translation for operation type GGML_OP_* is not implemented", when the user asks to add/implement/fix a GGUF or ggml op translator or an op_case, or when working on src/frontends/gguf/src/op/. Do NOT use for enabling a new model architecture (that is usually just a name in arch_registry.cpp), for wrong numerical output from an op that already converts, or for GGUF quantization format work.

77

Quality

97%

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

100%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 exceptionally lean, actionable body that gives concrete grep/build/test commands, a clear numbered workflow with an explicit verification loop, and a single well-signaled external reference. It assumes Claude's competence and adds only non-obvious project-specific detail.

DimensionReasoningScore

Conciseness

Four lean numbered steps with no padding and no explanation of concepts Claude already knows (no 'what is GGUF' filler). Every token earns its place. Not below 5 since there is no over-explanation to trim.

5 / 5

Actionability

Provides concrete executable commands (grep patterns, exact file paths, build flag '-DENABLE_OV_GGUF_FRONTEND=ON', test binary 'ov_gguf_frontend_tests') and a pointer to a checklist doc. Copy-paste-ready guidance covering the common case.

5 / 5

Workflow Clarity

Clear numbered sequence (1-4) with an explicit validation/feedback loop: 'build and run ov_gguf_frontend_tests — filtered while iterating, unfiltered before finishing so the coverage gate runs', plus the mandatory op-coverage gate. Matches the anchor 5 example with explicit validation steps and error-recovery guidance.

5 / 5

Progressive Disclosure

Body is a concise overview pointing to a single one-level-deep reference (how_to_add_op.md) that is clearly signaled with its relative path. No bundle files exist for this skill; for a simple single-purpose skill this well-organized structure is appropriate per the simple-skills note.

5 / 5

Total

20

/

20

Passed

Description

95%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 highly specific, well-scoped description with explicit positive triggers, an exact error-string trigger, and clear negative boundaries. It uses correct third-person voice and avoids verbosity. Minor gap is that the capability list is narrowly focused on a single task type.

DimensionReasoningScore

Specificity

Names the domain and concrete actions ('adding or fixing an op translator') with several specific triggers, but coverage is narrow to a single op-translator task rather than multiple distinct capabilities. Not a 5 because it does not list multiple comprehensive concrete actions, and not a 3 because it clearly states more than 1-2 specific actions.

4 / 5

Completeness

Explicitly answers 'what' (enable a ggml op by adding/fixing a translator) and 'when' via a concrete 'Use when...' clause with multiple trigger phrases, plus negative boundary guidance ('Do NOT use for...'). Clearly and explicitly answers both what and when.

5 / 5

Trigger Term Quality

Includes the exact error string 'Translation for operation type GGML_OP_* is not implemented' plus natural user phrasings ('add/implement/fix a GGUF or ggml op translator or an op_case') and a concrete file path, covering synonyms (GGUF/ggml). Comprehensive natural trigger coverage matching the anchor 5 example.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (OpenVINO GGUF op translators) with explicit exclusions (new model architectures, numerical output, quantization format work) minimizing conflict with sibling skills. Minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

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.