New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Doca Collectx Deployment

by NVIDIA in NVIDIA/skills

A skill your agent uses to deploy and operate a CollectX (clx) based DOCA telemetry collector on a host or BlueField — wiring providers / counters into the collector, running the collection daemon…

OfficialApache-2.0Auto-check passedDevOps & Cloud

Install Doca Collectx Deployment

skills CLI
$ npx skills add NVIDIA/skills --skill doca-collectx-deployment -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NVIDIA/skills doca-collectx-deployment --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/doca-collectx-deployment .claude/skills/doca-collectx-deployment && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
doca-collectx-deployment
GitHub stars
3.5k
Token cost
~2.8k tokens
SKILL.md length
1,140 words
Files
8 (incl. references)
Skills in repo
380
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses to deploy and operate a CollectX (clx) based DOCA telemetry collector on a host or BlueField — wiring providers / counters into the collector, running the collection daemon…

  • Works in 3 steps: Read this SKILL.md first to confirm the… → **For the four-surface decomposition,… → **For step-by-step workflows —…
  • Deploy and operate a CollectX (clx) based DOCA telemetry collector on a host
  • SKILL.md covers The scope boundary (read this…, Audience, When to load this skill and What this skill provides, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Doca Collectx Deployment is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Use this skill to deploy and operate a CollectX (clx) based DOCA telemetry collector on a host or BlueField — wiring providers / counters into the collector, running the collection daemon, and shaping its exporters (Prometheus pull, Fluent Bit push, NetFlow, file / IPC) so the metrics actually leave the box. Trigger even when the user never says CollectX or clx — implicit phrasings: {collector emits nothing downstream}, {add a provider to the clx collector}, {turn on the Prometheus endpoint}, {ship counters to…

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including reference files (for example `BENCHMARK.md`, `CAPABILITIES.md` and `TASKS.md`). Compatibility notes: No DOCA install required to read this skill (it is a deployment / operation overlay over the DOCA telemetry libraries and the CollectX collection mechanism)…

It sits in DevOps & Cloud, covering Deployment, Monitoring and alerting and Agent instruction files. It works with Prometheus and NVIDIA AI Platform. The repository describes itself as: Agent Skills for NVIDIA products — install into Claude Code, Codex, and other coding agents to run Physical AI, robotics, simulation, CUDA, and RAG workflows end to end. The licence is Apache-2.0.

When your agent uses it

  • Deploy and operate a CollectX (clx) based DOCA telemetry collector on a host
  • BlueField — wiring providers / counters into the collector
  • Running the collection daemon
  • Shaping its exporters (Prometheus pull

Example prompts

  • “/doca-collectx-deployment”

Requirements

  • Compatibility (from SKILL.md): No DOCA install required to read this skill (it is a deployment / operation overlay over the DOCA telemetry libraries and the CollectX collection mechanism). The hands-on steps DO require a live DOCA install at /opt/mellanox/doca on a host or BlueField, an operator account that can run the collector and reach its exporter sinks, and the public DOCA Telemetry / DTS guides on docs.nvidia.com for any concrete provider name, schema field, flag, or config path (this skill never invents those).

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Read this SKILL.md first to confirm the user's question is
  2. **For the four-surface decomposition, the collection pipeline
  3. **For step-by-step workflows — configure, build (routing

What it can do on your machine

Read from SKILL.md and the folder at commit 67a13c0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    No DOCA install required to read this skill (it is a deployment / operation overlay over the DOCA telemetry libraries and the CollectX collection mechanism). The hands-on steps DO require a live DOCA install at /opt/mellanox/doca on a host or BlueField, an operator account that can run the collector and reach its exporter sinks, and the public DOCA Telemetry / DTS guides on docs.nvidia.com for any concrete provider name, schema field, flag, or config path (this skill never invents those).

    From compatibility in the SKILL.md frontmatter.

Context cost

Doca Collectx Deployment loads about 2.8k tokens when it runs, and up to ~5.1k if it reads all its reference files. Until then it costs about 261 tokens; SKILL.md has 1,140 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~261
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NVIDIA/skills at commit 67a13c0, republished under its Apache-2.0 licence (© NVIDIA). 1,140 words, ~2,834 tokens.

Download SKILL.mdSave it as .claude/skills/doca-collectx-deployment/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
doca-collectx-deployment
description
Use this skill to deploy and operate a CollectX (clx) based DOCA telemetry collector on a host or BlueField — wiring providers / counters into the collector, running the collection daemon, and shaping its exporters (Prometheus pull, Fluent Bit push, NetFlow, file / IPC) so the metrics actually leave the box. Trigger even when the user never says CollectX or clx — implicit phrasings: {collector emits nothing downstream}, {add a provider to the clx collector}, {turn on the Prometheus endpoint}, {ship counters to Fluent Bit from the DPU}, {daemon starts but no schema rows appear}. This skill owns the CollectX collection mechanism plus the operator's own doca-telemetry / doca-telemetry-exporter usage; it ROUTES the productized DOCA Telemetry Service (DTS) to public docs (AGENTS.md Non-goal #7), the reader API to doca-telemetry, and the publisher API to doca-telemetry-exporter. Refuse to invent clx symbols, provider names, schema fields, flags, or config paths — describe the class and route to the live source.
compatibility
No DOCA install required to read this skill (it is a deployment / operation overlay over the DOCA telemetry libraries and the CollectX collection mechanism). The hands-on steps DO require a live DOCA install at /opt/mellanox/doca on a host or BlueField, an operator account that can run the collector and reach its exporter sinks, and the public DOCA Telemetry / DTS guides on docs.nvidia.com for any concrete provider name, schema field, flag, or config path (this skill never invents those).
license
Apache-2.0
metadata.kind
library

DOCA CollectX telemetry deployment

Where to start: This skill is the bundle's home for operating a CollectX (clx) based telemetry collector — the collection framework that gathers provider counters into a schema and ships them out through one or more exporters. It is a deployment / operation skill, parallel to doca-bare-metal-deployment and doca-container-deployment: it owns the runtime shape of a telemetry collector on the operator's host or BlueField, not the library APIs the operator's own program calls. If the user wants to stand up, wire, or debug a collector and its exporters, open TASKS.md and start at ## configure. If the question is what surfaces does the collector even have and where is the scope boundary, start at CAPABILITIES.md. If the user has not installed DOCA yet, route to doca-setup first.

The scope boundary (read this before anything else)

CollectX (clx) is NVIDIA's telemetry collection framework. It underpins the DOCA Telemetry Service (DTS) — and DTS as-deployed (the productized, NGC-shipped / kubelet-started service container) is out of scope for this bundle per AGENTS.md Non-goal #7. This skill therefore draws a hard line and the agent MUST state it up front:

  • In scope here: the CollectX collection mechanism as a class (providers / counters → schema → collector daemon → exporters), and the operator deploying / running / debugging a collector that they own, plus the operator's own usage of the two in-bundle telemetry libraries when those feed or consume the collector.
  • Routed to the DOCA telemetry libraries: the hardware-counter reader API is owned by doca-telemetry; the application-side publisher API (emit counters / events from a DOCA program) is owned by doca-telemetry-exporter. This skill does not re-document either API surface.
  • Routed to public docs (Non-goal #7): the productized DTS container — its packaged config schema, its built-in provider set, its kubelet manifest, its NGC image — is externally productized. Route every "operate the DTS service" question to the doca-public-knowledge-map externally-productized routing row and the public DTS guide it points at. The agent must NOT synthesize DTS config file names, provider knob names, or paths from memory.

The load-bearing first-touch failure this skill exists to prevent is collapsing these four surfaces into "DOCA telemetry": the clx collection mechanism, the doca-telemetry reader library, the doca-telemetry-exporter publisher library, and the productized DTS container are four different things with four different owners. The agent surfaces the decomposition BEFORE any config-level guidance.

Audience

This skill serves external operators standing up or running a CollectX-based telemetry collector on a host or BlueField they administer — people who already have:

  • a DOCA install on the side they are collecting from (host x86 or BlueField Arm), verified per doca-setup ## test,
  • a goal of getting counters off the box through a collector + exporter, not of writing the reader / publisher library code (that is the two libs/ skills above), and
  • access to the public DOCA Telemetry and DTS guides on docs.nvidia.com as the authoritative source for any concrete provider name, schema field, flag, or config path.

It is not for:

  • developers writing the hardware-counter reader API (route to doca-telemetry) or the publisher API (route to doca-telemetry-exporter),
  • operators deploying / configuring the productized DTS container as a turnkey service — that is externally productized (Non-goal #7); route to the public DTS guide,
  • fresh-no-install users — those belong on doca-setup ## no-install.

The skill teaches the agent the procedure and the scope boundary; it does not invent clx symbol names, provider names, schema field names, exporter flag names, or config paths from memory — those come from the live install and the public docs via doca-public-knowledge-map.

Show full SKILL.md (567 more words)Show less

When to load this skill

Load this skill when the user is doing hands-on deployment or operation of a CollectX-based telemetry collector and the question is about the collector runtime shape, not a library API. Concretely:

  • Standing up a collector that gathers provider counters into a schema and ships them out — and deciding which export backend (Prometheus pull, Fluent Bit push, NetFlow, file / IPC) fits the downstream consumer.
  • Wiring a provider / counter family into the collector and confirming the device actually exposes it before the config commits (the gate-before-commit rule, shared with doca-telemetry-utils).
  • Turning on / shaping an exporter so the metrics actually leave the box, and confirming the downstream consumer receives them end-to-end (not just "the daemon is running").
  • Diagnosing a collector that starts but produces no schema rows, or ships nothing downstream, or whose exporter endpoint is silent — walking the layered ladder rather than guessing.
  • Recognising when the user is actually asking about the productized DTS container (route to public docs, Non-goal #7), the reader library (route to doca-telemetry), or the publisher library (route to doca-telemetry-exporter) instead of the collection mechanism this skill owns.

Do not load this skill for: the hardware-counter reader API (use doca-telemetry); the publisher API (use doca-telemetry-exporter); operating the productized DTS container (route via doca-public-knowledge-map Non-goal #7); installing DOCA or preparing the env (use doca-setup); or any hardware-state change (use doca-hardware-safety).

What this skill provides

This is a thin loader. The substantive material lives in two companion files:

  • CAPABILITIES.md — the collector deployment contract as a class: the four-surface decomposition (clx collection mechanism vs reader library vs publisher library vs productized DTS), the collection pipeline shape (providers / counters → schema → collector daemon → exporters), the export-backend surface (Prometheus pull, Fluent Bit push, NetFlow, file / IPC) at class level, the version overlay on doca-version, the error taxonomy (collector won't start → no provider rows → schema mismatch → exporter silent → downstream skew → transport), the observability surface, and the safety policy (gate provider support before commit; collector is read-only against the device; route any mutating step to doca-hardware-safety; do not invent clx names / paths).
  • TASKS.md — step-by-step workflows for the deployment verbs: configure, build (routing stub), modify, run, test, debug, plus a Deferred task verbs block that routes out-of-scope questions (the two libraries, the productized DTS container, env prep, hardware-state change) to their owners.

The skill assumes a host or BlueField where DOCA is already installed and healthy (per doca-setup ## test) and the operator can run the collector and reach its exporter sinks. It does not cover installing DOCA — that path goes through doca-setup — and it does not cover the reader / publisher library APIs or the productized DTS container.

Loading order

  1. Read this SKILL.md first to confirm the user's question is in scope (operating a CollectX-based collector and its exporters — NOT the reader / publisher library APIs, NOT the productized DTS container).
  2. For the four-surface decomposition, the collection pipeline shape, the export-backend class surface, the version overlay, the error taxonomy, the observability surface, and the safety policy, see CAPABILITIES.md.
  3. For step-by-step workflows — configure, build (routing stub), modify, run, test, debug, and the Deferred task verbs block — see TASKS.md.

Both companion files cross-link to each other, doca-version for the canonical version-handling rules, and doca-public-knowledge-map whenever the right answer is "read the live config / public docs" rather than collector-specific guidance.

Example questions this skill answers well

See references/details.md.

What this skill deliberately does not ship

See references/details.md.

See references/details.md.

© NVIDIA, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (references) in skills/doca-collectx-deployment of NVIDIA/skills.

  • SKILL.md
  • BENCHMARK.md
  • CAPABILITIES.md
  • TASKS.md
  • evals/evals.json
  • references/details.md
  • skill-card.md
  • skill.oms.sig

Open the folder on GitHubat commit 67a13c0

Compare with similar skills

Doca Collectx Deployment next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Doca Collectx Deployment compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Doca Collectx Deployment this skillNVIDIA/skills3.5k—~2.8kAutomated safety check: PassApache-2.0
Optimize Slurm TopologyNVlabs/alpasim1.3k—~1.6kAutomated safety check: PassApache-2.0
Dashboard Previewm4r1k/Eneru149—~1.4kAutomated safety check: PassMIT
Alicloud Acs Agent Sandboxcinience/alicloud-skills397—~2.7kAutomated safety check: PassMIT
Aqua Metricsoracle/accelerated-data-science125—~1.5kAutomated safety check: PassUPL-1.0
Analyzing Experiment Precompute CanaryPostHog/posthog40k—~3.5kAutomated safety check: PassCustom licence

Similar skills

  • Optimize Slurm Topology

    NVlabs/alpasim

    Optimize AlpaSim Slurm topology throughput using persistent local Prometheus/Grafana telemetry and run artifacts.

    1.3k GitHub stars~1.6k tokensUpdated 20 days ago
    DevOps & CloudAuto-check passed

  • Dashboard Preview

    m4r1k/Eneru

    Visually verify Eneru browser-dashboard changes against a live daemon or audit an exact deployment.

    149 GitHub stars~1.4k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Alicloud Acs Agent Sandbox

    cinience/alicloud-skills

    Bootstrap, create, connect to, operate, secure, scale, upgrade, troubleshoot, inspect, and tear down Alibaba Cloud Container Compute Service (ACS) Agent Sandbox environments.

    397 GitHub stars~2.7k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

  • Aqua Metrics

    oracle/accelerated-data-science

    Official

    Set up Prometheus and Grafana monitoring for AQUA vLLM model deployments on OCI.

    125 GitHub stars~1.5k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

  • Analyzing Experiment Precompute Canary

    PostHog/posthog

    Official

    Analyze the experiment precompute result-consistency canary across prod-US and prod-EU, deep-dive any issues, and produce an actionable report.

    40k GitHub stars~3.5k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Deepgram Prod Checklist

    jeremylongshore/tons-of-skills-marketplace

    Execute Deepgram production deployment checklist. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2.3k tokensUpdated today
    DevOps & CloudAuto-check passed

More from NVIDIA/skills

All 380 skills in this repo

  • Vss Deploy Detection Tracking 2D

    NVIDIA/skills

    Official

    A skill your agent uses when the user wants to deploy, run, debug, tear down, or call the REST API of the RTVI-CV 2D detection / tracking microservice.

    3.5k GitHub starsUsed in 1 repo~4.5k tokens
    Auto-check passed

  • HSB IP Def File Tool

    NVIDIA/skills

    Official

    Generates, validates, compares and explains HOLOLINK_def.svh macro files for the HSB IP, using bundled Python scripts and asking before it writes anything.

    3.5k GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed

  • Isaac Sim Mission Control Showcase

    NVIDIA/skills

    Official

    Runs and validates an end-to-end Mission Control demo in a locally installed Isaac Sim, with a Nova Carter robot driven through a Python server.

    3.5k GitHub stars~4.8k tokensUpdated yesterday
    Auto-check passed

  • Defect Image Generation with Cosmos AnomalyGen

    NVIDIA/skills

    Official

    Orchestrates defect image generation for PCBA, metal surface and glass inspection with NVIDIA Cosmos AnomalyGen on OSMO, from cold-start Day 0 to real-photo Day 1 labeling.

    3.5k GitHub stars~5k tokensUpdated yesterday
    Auto-check: notes

  • Physical AI Video Augmentation on OSMO

    NVIDIA/skills

    Official

    Orchestrates video data augmentation and auto-labeling workflows on OSMO, from flow selection and preflight checks to submission, monitoring and output download.

    3.5k GitHub stars~4.7k tokensUpdated yesterday
    Auto-check: notes

  • TAO Detection KPI Analysis

    NVIDIA/skills

    Official

    Runs NVIDIA TAO Data Services KPI analysis on object detection results, comparing predictions to ground truth and writing per-class precision, recall and AP to a CSV.

    3.5k GitHub stars~2.7k tokensUpdated yesterday
    Auto-check: notes

Works with

Categories

Questions about Doca Collectx Deployment

What does Doca Collectx Deployment do?

A skill your agent uses to deploy and operate a CollectX (clx) based DOCA telemetry collector on a host or BlueField — wiring providers / counters into the collector, running the collection daemon…. Doca Collectx Deployment is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Use this skill to deploy and operate a CollectX (clx) based DOCA telemetry collector on a host or BlueField — wiring providers / counters into the collector, running the collection daemon, and shaping its exporters (Prometheus pull, Fluent Bit push, NetFlow, file / IPC) so the metrics actually leave the box.

When should I use Doca Collectx Deployment?

Doca Collectx Deployment fits situations like: deploy and operate a CollectX (clx) based DOCA telemetry collector on a host; blueField — wiring providers / counters into the collector; running the collection daemon; shaping its exporters (Prometheus pull.

How do I install Doca Collectx Deployment in Claude Code?

Run `npx skills add NVIDIA/skills --skill doca-collectx-deployment -a claude-code`. Or copy the skill folder (skills/doca-collectx-deployment in NVIDIA/skills) into .claude/skills/doca-collectx-deployment in your project. Claude Code loads it when a task matches its description.

How do I install Doca Collectx Deployment in Codex?

Run `npx skills add NVIDIA/skills --skill doca-collectx-deployment -a codex`. Or copy the skill folder (skills/doca-collectx-deployment in NVIDIA/skills) into .agents/skills/doca-collectx-deployment in your project. Codex loads it when a task matches its description.

Can I use Doca Collectx Deployment in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/skills --skill doca-collectx-deployment -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/doca-collectx-deployment, .gemini/skills/doca-collectx-deployment, .github/skills/doca-collectx-deployment and .opencode/skills/doca-collectx-deployment in your project.

What does Doca Collectx Deployment need to run?

SKILL.md names no scripts, command-line tools or credentials: Doca Collectx Deployment is instructions for the agent only. Compatibility (from SKILL.md): No DOCA install required to read this skill (it is a deployment / operation overlay over the DOCA telemetry libraries and the CollectX collection mechanism). The hands-on steps DO require a live DOCA install at /opt/mellanox/doca on a host or BlueField, an operator account that can run the collector and reach its exporter sinks, and the public DOCA Telemetry / DTS guides on docs.nvidia.com for any concrete provider name, schema field, flag, or config path (this skill never invents those). .

Does Doca Collectx Deployment access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Doca Collectx Deployment safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Doca Collectx Deployment use?

Doca Collectx Deployment is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Doca Collectx Deployment use?

About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.3k tokens, read only when the agent opens those files.

What are the alternatives to Doca Collectx Deployment?

Skills that share tags, products or a category with Doca Collectx Deployment: Optimize Slurm Topology (NVlabs/alpasim, 1.3k stars), Dashboard Preview (m4r1k/Eneru, 149 stars), Alicloud Acs Agent Sandbox (cinience/alicloud-skills, 397 stars) and Aqua Metrics (oracle/accelerated-data-science, 125 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Doca Collectx Deployment?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/skills, which has 3,539 GitHub stars. The repository holds 380 skills in this directory. The repository was last updated on October 7, 2026.

Source: NVIDIA/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.