domains / families / devops / doca-structured-tools-contract

doca-structured-tools-contract

separate

Not for writing library code (name that library skill). Use this skill whenever another DOCA skill says "prefer the structured tool per doca-structured-tools-contract", or when the user wants a one-shot answer consolidating what multiple manual commands would produce — DOCA env / version / devices / capabilities / validate / host vs DPU state. Trigger even without the phrases "structured tool" or "doca-env --json" — typical phrasings include "is there one command that tells me everything about my DOCA install", "what version is X capability available since", "every PF/VF/SF visible on this BlueField with PCIe address", or "will this pipe pass validate before commit". Refuse and route elsewhere for general DOCA orientation, library API how-to, or install-from-scratch guidance — those belong to the per-library skill, doca-public-knowledge-map, or doca-setup.

When to use

• one-shot answer consolidating multiple manual commands
• DOCA env / version / devices / capabilities
• validate / host vs DPU state
• checking a spec before commit
• validate-before-commit schema
• every PF/VF/SF visible on this BlueField with PCIe address
• what version is X capability available since
• is there one command that tells me everything about my DOCA install

When not to use

• writing library code
• general DOCA orientation
• library API how-to
• install-from-scratch guidance

Skill page

Source