# Doca structured tools contract

> Doca structured tools contract is an open-source agent skill for legal and government. Not for writing library code (name that library skill). It is available on Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose.

- **Kind:** Skill
- **Pricing:** Open source
- **Platforms:** Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, Goose
- **Website:** https://github.com/NVIDIA/skills/tree/main/skills/doca-structured-tools-contract
- **Repository:** https://github.com/nvidia/skills
- **GitHub stars:** 4,037
- **License:** Apache-2.0
- **Skill name:** doca-structured-tools-contract
- **Collection:** https://github.com/NVIDIA/skills
- **Categories:** legal and government
- **Listing updated:** 2026-11-17

## About

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 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.

## What it can access

From a static check of the files on GitHub; nothing was run.

- [Instructions only, no scripts](https://github.com/NVIDIA/skills/tree/HEAD/skills/doca-structured-tools-contract)
- [License: Apache-2.0](https://github.com/NVIDIA/skills/tree/HEAD/skills/doca-structured-tools-contract)

## Install

### Claude Code

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

```sh
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.

### Codex

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

```sh
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.

### Cursor

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

```sh
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.

### Gemini CLI

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

```sh
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.

### VS Code

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

```sh
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.

### Other agents

Get the folder:

```sh
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.

## 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.

## Alternatives

- [Data breach blast radius](https://ai-powered.com/skills/data-breach-blast-radius): Data breach blast radius is an open-source agent skill for legal and government.
- [Entry point analyzer](https://ai-powered.com/skills/entry-point-analyzer): Entry point analyzer is an open-source agent skill for legal and government.
- [Metronome](https://ai-powered.com/skills/metronome): Metronome is an open-source agent skill for legal and government.
- [Agent wallet policy](https://ai-powered.com/skills/agent-wallet-policy): Agent wallet policy is an open-source agent skill for finance and payments.
- [Use smart contract platform](https://ai-powered.com/skills/use-smart-contract-platform): Use smart contract platform is an open-source agent skill for legal and government.
- [Entry point analyzer](https://ai-powered.com/skills/entry-point-analyzer-plurigrid): Entry point analyzer is an open-source agent skill for legal and government.
- [Implementing gdpr data protection controls](https://ai-powered.com/skills/implementing-gdpr-data-protection-controls): Implementing gdpr data protection controls is an open-source agent skill for legal and government.
- [Analyzing ethereum smart contract vulnerabilities](https://ai-powered.com/skills/analyzing-ethereum-smart-contract-vulnerabilities): Analyzing ethereum smart contract vulnerabilities is an open-source agent skill for finance and payments.

---
Source: https://ai-powered.com/skills/doca-structured-tools-contract
