ov-gguf-add-architecture
Enable a new model architecture/family in the OpenVINO GGUF frontend's native .gguf builder, or check whether a GGUF model is supported. Use when the user asks to enable, support or bring up a GGUF/llama.cpp model (llama, qwen, phi, gemma, MoE and similar decoder-only families), when a .gguf file is rejected as an unsupported architecture, or when working on arch_registry / DecoderBuilder in src/frontends/gguf/src/builder/. Do NOT use for adding a single ggml op translator or for debugging wrong output from an already-supported model.
70
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
- Read src/frontends/gguf/docs/adding_an_architecture.md — most architectures in the transformer family need no code, only a
general.architecturestring added toarch_registry.cppplus the correct RoPE type. It also lists exactly which structural features are auto-detected from the tensor table and metadata, and how to verify a new arch. - Check src/frontends/gguf/docs/supported_models.md first to see whether the architecture is already accepted and how support was verified.
- Only if the family is structurally novel, consult the "10% case" section before adding builder code.
- Verify as that document prescribes, including the graph-fingerprint check, and re-run the other supported architectures after any change to shared builder logic.
- Repository
- openvinotoolkit/openvino
- Commit
f766feb
- Last updated
- First committed
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.