What problem does it solve?
Writing a first DOCA application is hard because the SDK spans many libraries, build flavors, and a strict object lifecycle, and mistakes surface as cryptic DOCA_ERROR_* codes. This Skill gives agents the library-agnostic programming shape every DOCA program shares so they can derive, build, test, and debug applications correctly without inventing unverified code.
Core Features & Use Cases
- First-app derivation: Copy a shipped sample from /opt/mellanox/doca/samples and apply a minimum-diff modification using a five-slot modify-schema, never authoring DOCA source from scratch.
- Canonical build pattern: Wire pkg-config doca-<library> with meson for C/C++, or FFI/bindings against the public C ABI from Rust, Go, or Python.
- Lifecycle and error guidance: Apply the universal cfg-create → init → start → use → stop → destroy lifecycle and decode any doca_error_t with doca_error_get_descr().
- Use Case: A developer says "write my first DOCA Flow program" — the agent picks the smallest shipped sample, fills the modify-schema, builds with the trace flavor, validates before commit, and runs staged against one representor.
Quick Start
Ask your agent to help you write your first DOCA program by deriving it from a shipped sample and building it with pkg-config and meson.