# Doca pipeline language developer tools

> Doca pipeline language developer tools is an open-source agent skill for developer tools. Use this skill when the operator is driving the DOCA Pipeline Language (DPL) Developer Tools to inspect or debug DPL programs on a BlueField. 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-pipeline-language-developer-tools
- **Repository:** https://github.com/nvidia/skills
- **GitHub stars:** 4,037
- **License:** Apache-2.0
- **Skill name:** doca-pipeline-language-developer-tools
- **Collection:** https://github.com/NVIDIA/skills
- **Categories:** developer tools
- **Listing updated:** 2026-11-17

## About

Use this skill when the operator is driving the DOCA Pipeline Language (DPL) Developer Tools to inspect or debug DPL programs on a BlueField DPU — DPL Nspect for runtime state such as tables, keys, and counters, DPL Debugger for packet flow, DPL Admin for dynamic configuration changes in the DPL Runtime Daemon, P4 Runtime Shell as a P4Runtime control plane manager, or DPL Runtime Controller SDK for custom P4Runtime applications and DPL shared memory APIs. Trigger even when the user does not explicitly mention "DPL Developer Tools" — implicit phrasings include "inspect the DPL tables on the DPU", "why can't I start a DPL debug session", "change a dpl_rtd configuration item without restarting", "build my own P4Runtime app for DPL", or "visualize packet flow through my DPL program". Refuse and route elsewhere: authoring, compiling and deploying DPL programs to the DOCA Pipeline Language Service Guide, DOCA install/bring-up to doca-setup, and hardware or firmware state changes to doca-hardware-safety.

## When your agent uses it

> Use this skill when the operator is driving the DOCA Pipeline Language (DPL) Developer Tools to inspect or debug DPL programs on a BlueField DPU — DPL Nspect for runtime state such as tables, keys, and counters, DPL Debugger for packet flow, DPL Admin for dynamic configuration changes in the DPL Runtime Daemon, P4 Runtime Shell as a P4Runtime control plane manager, or DPL Runtime Controller SDK for custom P4Runtime applications and DPL shared memory APIs. Trigger even when the user does not explicitly mention "DPL Developer Tools" — implicit phrasings include "inspect the DPL tables on the DPU", "why can't I start a DPL debug session", "change a dpl_rtd configuration item without restarting", "build my own P4Runtime app for DPL", or "visualize packet flow through my DPL program". Refuse and route elsewhere: authoring, compiling and deploying DPL programs to the DOCA Pipeline Language Service Guide, DOCA install/bring-up to doca-setup, and hardware or firmware state changes to doca-hardware-safety.

## 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-pipeline-language-developer-tools)
- [License: Apache-2.0](https://github.com/NVIDIA/skills/tree/HEAD/skills/doca-pipeline-language-developer-tools)

## Install

### Claude Code

Copy the skill folder to `~/.claude/skills/doca-pipeline-language-developer-tools` 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-pipeline-language-developer-tools &&
cp -R "$tmp/skills/doca-pipeline-language-developer-tools" ~/.claude/skills/doca-pipeline-language-developer-tools &&
rm -rf "$tmp"
```

For one project only, put the folder in `.claude/skills/doca-pipeline-language-developer-tools` inside it instead.

### Codex

Copy the skill folder to `~/.agents/skills/doca-pipeline-language-developer-tools` 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-pipeline-language-developer-tools &&
cp -R "$tmp/skills/doca-pipeline-language-developer-tools" ~/.agents/skills/doca-pipeline-language-developer-tools &&
rm -rf "$tmp"
```

For one repository only, put the folder in `.agents/skills/doca-pipeline-language-developer-tools` inside it instead.

### Cursor

Copy the skill folder to `~/.cursor/skills/doca-pipeline-language-developer-tools` 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-pipeline-language-developer-tools &&
cp -R "$tmp/skills/doca-pipeline-language-developer-tools" ~/.cursor/skills/doca-pipeline-language-developer-tools &&
rm -rf "$tmp"
```

For one project only, put the folder in `.cursor/skills/doca-pipeline-language-developer-tools` 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-pipeline-language-developer-tools
```

Or copy the folder to `~/.gemini/skills/doca-pipeline-language-developer-tools` yourself.

### VS Code

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

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

For one project only, put the folder in `.github/skills/doca-pipeline-language-developer-tools` inside it instead.

### Other agents

Get the folder:

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

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

## FAQ

### How do I install Doca pipeline language developer tools in Claude Code?

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

### Does Doca pipeline language developer tools 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 pipeline language developer tools?

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 pipeline language developer tools?

The closest alternatives to Doca pipeline language developer tools are Rea changelog update, Code review, Gem devops guidelines, PR screenshots and Make repo contribution.

## Alternatives

- [Rea changelog update](https://ai-powered.com/skills/rea-changelog-update): Rea changelog update is an open-source agent skill for developer tools.
- [Code review](https://ai-powered.com/skills/code-review-mattpocock): Code review is an open-source agent skill for developer tools.
- [Gem devops guidelines](https://ai-powered.com/skills/gem-devops-guidelines): Gem devops guidelines is an open-source agent skill for cloud and infrastructure.
- [PR screenshots](https://ai-powered.com/skills/pr-screenshots): PR screenshots is an open-source agent skill for developer tools.
- [Make repo contribution](https://ai-powered.com/skills/make-repo-contribution): Make repo contribution is an open-source agent skill for developer tools.
- [Create github issues for unmet specification requirements](https://ai-powered.com/skills/create-github-issues-for-unmet-specification-requirements): Create github issues for unmet specification requirements is an open-source agent skill for developer tools.
- [Github actions hardening](https://ai-powered.com/skills/github-actions-hardening): Github actions hardening is an open-source agent skill for developer tools.
- [Github codespaces efficiency](https://ai-powered.com/skills/github-codespaces-efficiency): Github codespaces efficiency is an open-source agent skill for developer tools.

---
Source: https://ai-powered.com/skills/doca-pipeline-language-developer-tools
