Skip to content
Skill

Doca structured tools contract

Not for writing library code (name that library skill)

Install
Scripts
None
Platforms
Claude Code, Codex, Cursor
GitHub stars
4K
Last commit
1 day ago
License
Apache-2.0
Listing updated
today

When your agent uses it

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.

From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.

What it can access

From a static check of its 6 files (41 KB) on GitHub on 17 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.

Install

Copy the skill folder to ~/.claude/skills/doca-structured-tools-contract to use it in all your projects:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/NVIDIA/skills.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/doca-structured-tools-contract &&
cp -R "$tmp/skills/doca-structured-tools-contract" ~/.claude/skills/doca-structured-tools-contract &&
rm -rf "$tmp"

For one project only, put the folder in .claude/skills/doca-structured-tools-contract inside it instead.

Claude Code docs on skills

Copy the skill folder to ~/.agents/skills/doca-structured-tools-contract to use it in every repository:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/NVIDIA/skills.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/doca-structured-tools-contract &&
cp -R "$tmp/skills/doca-structured-tools-contract" ~/.agents/skills/doca-structured-tools-contract &&
rm -rf "$tmp"

For one repository only, put the folder in .agents/skills/doca-structured-tools-contract inside it instead.

Codex docs on skills

Copy the skill folder to ~/.cursor/skills/doca-structured-tools-contract to use it in every project:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/NVIDIA/skills.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/doca-structured-tools-contract &&
cp -R "$tmp/skills/doca-structured-tools-contract" ~/.cursor/skills/doca-structured-tools-contract &&
rm -rf "$tmp"

For one project only, put the folder in .cursor/skills/doca-structured-tools-contract inside it instead.

Cursor docs on skills

Run in a terminal (add --scope workspace to install it for the current workspace only):

gemini skills install https://github.com/NVIDIA/skills.git --path skills/doca-structured-tools-contract

Or copy the folder to ~/.gemini/skills/doca-structured-tools-contract yourself.

Gemini CLI docs on skills

For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/doca-structured-tools-contract:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/NVIDIA/skills.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/doca-structured-tools-contract &&
cp -R "$tmp/skills/doca-structured-tools-contract" ~/.copilot/skills/doca-structured-tools-contract &&
rm -rf "$tmp"

For one project only, put the folder in .github/skills/doca-structured-tools-contract inside it instead.

VS Code docs on skills

Get the folder:

git clone --depth 1 https://github.com/NVIDIA/skills.git

Then copy skills/skills/doca-structured-tools-contract into your agent's skills folder as doca-structured-tools-contract. Agents that support SKILL.md read one folder per skill.

The SKILL.md format

Doca structured tools contract FAQ

How do I install Doca structured tools contract in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/doca-structured-tools-contract to use it in all your projects, or to .claude/skills/doca-structured-tools-contract in one project.

Does Doca structured tools contract run scripts?

No. It is instructions only, with no scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.

Which AI agents can use Doca structured tools contract?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.

What are the best alternatives to Doca structured tools contract?

The closest alternatives to Doca structured tools contract are Data breach blast radius, Entry point analyzer, Metronome, Agent wallet policy and Use smart contract platform.

More from NVIDIA/skills

  1. Use for NVIDIA-related requests where an NVIDIA skill might help, even if the user did not ask for a skill

    • Open source
    • 4K GitHub stars
  2. Official NVIDIA-authored guidance for NVIDIA cuDF GPU DataFrames, pandas acceleration, dask-cuDF, ETL, joins, groupby, CSV/Parquet I/O, null

    • Open source
    • 4K GitHub stars
  3. Calibrate a new dataset from live RTSP camera streams via the AutoMagicCalib REST API

    • Open source
    • 4K GitHub stars
  4. Calibrates pre-recorded `cam_*.mp4` datasets through the AutoMagicCalib REST API

    • Open source
    • 4K GitHub stars
    • Design and media
  5. Launch AutoMagicCalib microservice and web UI from NGC release images via Docker Compose

    • Open source
    • 4K GitHub stars

Alternatives to Doca structured tools contract

  1. Pre-breach impact analysis: inventories sensitive data (PII, PHI, PCI-DSS, credentials), traces data flows, scores exposure vectors, and pro

    • Open source
    • 41.3K GitHub stars
    • Legal and government
  2. Analyzes smart contract codebases to identify state-changing entry points for security auditing

    • Open source
    • 8.2K GitHub stars
    • Legal and government
  3. Guides Metronome usage-based billing integration decisions — event ingestion (single and batch, idempotency, billable metrics), contract des

    • Open source
    • 2.1K GitHub stars
    • Legal and government
  4. View spending policy on a Circle agent wallet — per-transaction, daily, weekly, and monthly USDC caps and contract allowlists via the `circl

    • Open source
    • 168 GitHub stars
    • Finance and payments
  5. Deploy, import, interact with, and monitor smart contracts using Circle Smart Contract Platform APIs

    • Open source
    • 168 GitHub stars
    • Legal and government
  6. Analyzes smart contract codebases to identify state-changing entry points for security auditing

    • Open source
    • 72 GitHub stars
    • Legal and government