What problem does it solve?
Agents answering DOCA environment, version, device, capability, and validation questions often run many manual commands inconsistently across hosts. This Skill defines a shared contract so agents detect structured helper tools first, prefer their JSON output when present, fall back to documented manual command chains when absent, and always report which path was taken.
Core Features & Use Cases
- Detect-Prefer-Fallback-Report loop: A four-step agent behavior contract with read-only probe commands (e.g.,
command -v doca-env) that decide between structured JSON output and manual command chains.
- Locked JSON schemas: Authoritative schemas for
doca-env --json, version-matrix.json, capability-snapshot, validate-before-commit, and host/DPU state collection, each with an ordered manual fallback chain.
- Use Case: A user asks "is there one command that tells me everything about my DOCA install?" The agent probes for
doca-env, uses its JSON if valid, otherwise walks the pkg-config, doca_caps, lsmod, and meminfo fallback chain, and reports which path it took.
Quick Start
Ask your agent whether a single command can show the full DOCA environment including version, devices, libraries, drivers, and hugepages on this host.