Skip to content
Skill

Doca pipeline language 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

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

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.

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 8 files (68 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-pipeline-language-developer-tools 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-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.

Claude Code docs on skills

Copy the skill folder to ~/.agents/skills/doca-pipeline-language-developer-tools 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-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.

Codex docs on skills

Copy the skill folder to ~/.cursor/skills/doca-pipeline-language-developer-tools 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-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.

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

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

Gemini CLI docs on skills

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

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.

VS Code docs on skills

Get the folder:

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.

The SKILL.md format

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

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

  1. Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Ple

    • Open source
    • 465K GitHub stars
    • Developer tools
  2. Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's docu

    • Open source
    • 326K GitHub stars
    • Developer tools
  3. Design or review infrastructure, deployment, CI/CD, Docker, Kubernetes, health checks, rollback, feature flags, production readiness, and mo

    • Open source
    • 41.3K GitHub stars
    • Cloud and infrastructure
  4. Embed before/after screenshots and annotated images in pull request descriptions

    • Open source
    • 41.3K GitHub stars
    • Developer tools
  5. All changes to code must follow the guidance documented in the repository

    • Open source
    • 41.3K GitHub stars
    • Developer tools