Add Cpu Op
Developmentadd-cpu-opAdd Cpu Op is an Agent Skill for development published in the openvinotoolkit/openvino repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Add a new operation to the OpenVINO CPU plugin — node registration, JIT/oneDNN executors (AVX2/AVX-512/AMX), and functional tests.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/openvinotoolkit/openvino/blob/HEAD/.github/agents-prototype/skills/add-cpu-op/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/add-cpu-op, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Skill: Add CPU Op
When to use
When the Core OpSpec agent has produced a new op spec and you need to implement CPU plugin support: node class, executor strategy, and single-layer tests.
Steps
Execute in order — each step produces artifacts consumed by the next.
| Step | File | Purpose |
|---|---|---|
| 1 | step1-analysis.md | Read op spec, determine implementation strategy (reference / JIT / oneDNN), identify ISA targets and precision requirements |
| 2 | step2-implementation.md | Create node class (header + source), register in factory, hook up shape inference |
| 3 | step3-optimization.md | Write JIT executor (AVX2/AVX-512/AMX) or oneDNN-backed path; CpuParallel integration |
| 4 | step4-testing.md | Shared single-layer tests, custom CPU tests, dynamic shapes |