Logfire Infrastructure
pydantic/skills
Monitor hosts, Docker containers, Kubernetes clusters, database/queue/cache servers, and cloud-provider metrics with Pydantic Logfire — no application code required.
The data-mover for TAO jobs — decides the storage tier (A pre-positioned mount with zero fetch / B volume-from-S3 / C ephemeral in-compute fetch), stages inputs (bulk + annotation-selective +…
The automated check flagged lines worth reading first. See the safety section below.
$ npx skills add NVIDIA/skills --skill tao-data-io -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NVIDIA/skills tao-data-io --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tao-data-io .claude/skills/tao-data-io && rm -rf skills-srcUse ~/.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/
Install the "tao-data-io" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/tao-data-io into .claude/skills/tao-data-io/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tao-data-io", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/NVIDIA/skills/tree/main/skills/tao-data-ioType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add NVIDIA/skills --skill tao-data-io -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NVIDIA/skills tao-data-io --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/tao-data-io .agents/skills/tao-data-io && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "tao-data-io" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/tao-data-io into .agents/skills/tao-data-io/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tao-data-io", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NVIDIA/skills --skill tao-data-io -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NVIDIA/skills tao-data-io --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/tao-data-io .cursor/skills/tao-data-io && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "tao-data-io" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/tao-data-io into .cursor/skills/tao-data-io/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tao-data-io", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/NVIDIA/skills.git --path skills/tao-data-io--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add NVIDIA/skills --skill tao-data-io -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NVIDIA/skills tao-data-io --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/tao-data-io .gemini/skills/tao-data-io && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "tao-data-io" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/tao-data-io into .gemini/skills/tao-data-io/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tao-data-io", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install NVIDIA/skills tao-data-ioInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add NVIDIA/skills --skill tao-data-io -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/tao-data-io .github/skills/tao-data-io && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "tao-data-io" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/tao-data-io into .github/skills/tao-data-io/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tao-data-io", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NVIDIA/skills --skill tao-data-io -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install NVIDIA/skills tao-data-io --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/tao-data-io .opencode/skills/tao-data-io && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "tao-data-io" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/tao-data-io into .opencode/skills/tao-data-io/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tao-data-io", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
tao-data-ioThe data-mover for TAO jobs — decides the storage tier (A pre-positioned mount with zero fetch / B volume-from-S3 / C ephemeral in-compute fetch), stages inputs (bulk + annotation-selective +…
Tao Data Io is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. The data-mover for TAO jobs — decides the storage tier (A pre-positioned mount with zero fetch / B volume-from-S3 / C ephemeral in-compute fetch), stages inputs (bulk + annotation-selective + archive extract + HF/NGC PTM), maps credentials to env, routes outputs 3-way with upload-excludes, and runs the compute-frame verify gate. A support skill other platform skills (docker, kubernetes, slurm, brev, virtualenv) call to get data to and from the compute container without the TAO SDK. Trigger phrases include "stage…
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `BENCHMARK.md`, `config/skillspector-baseline.yaml` and `evals/evals.json`). Compatibility notes: Requires aws CLI or s5cmd on the staging host, plus Python 3.10+ with boto3 and pandas/pyarrow for annotation-selective download. No nvidia-tao-sdk, no…
It sits in DevOps & Cloud, covering File uploads and storage, Container orchestration and Containers. It works with NVIDIA AI Platform, Docker, Kubernetes and Amazon Web Services. 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.
Read from SKILL.md and the folder at commit 67a13c0. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadBashFrom allowed-tools in the SKILL.md frontmatter.
Ships script files (Python), which the agent can run.
Shell commands in SKILL.md call:
awspythonkubectlhuggingface-cliFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use aws and kubectl, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
AWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEYACCESS_KEYSECRET_KEYHF_TOKENNGC_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Requires aws CLI or s5cmd on the staging host, plus Python 3.10+ with boto3 and pandas/pyarrow for annotation-selective download. No nvidia-tao-sdk, no fsspec/s3fs. Credentials are read from the process environment, whether exported in the user's shell or sourced from a user-approved env file.
From compatibility in the SKILL.md frontmatter.
Tao Data Io loads about 1.5k tokens when it runs, and up to ~5.2k if it reads all its reference files. Until then it costs about 170 tokens; SKILL.md has 590 words of instructions outside code blocks.
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.
The automated check found patterns that need a careful read before installing.
and **never** write `~/.aws/credentials`:set -a; source /path/to/.env; set +a # omit if already exportedset -a; source /path/to/.env; set +a # omit if already exportedallowed-tools: Read, BashAutomated 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.
The full file from NVIDIA/skills at commit 67a13c0, republished under its Apache-2.0 licence (© NVIDIA). 590 words, ~1,501 tokens.
.claude/skills/tao-data-io/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.Get data to and from the compute container. Decide the storage tier first —
under strategy A (pre-positioned mount) no bytes move at all — and when a
fetch is needed, move it host-side with aws/s5cmd/boto3/huggingface-cli/ngc
directly — no nvidia-tao-sdk, no in-container runtime. Other platform skills
call this skill to stage inputs before launch and sync outputs after. It never
launches a container itself. The chosen tier is stamped into the job-record at
submit.
When NOT to invoke this skill: if the inputs are already readable from the compute frame (a local path on the execution host, an existing Lustre/PVC/bind mount), that IS tier A — record it and skip this skill entirely; there is nothing to move. Air-gapped hosts: tier A is the only tier — never attempt an S3/HF/NGC fetch; anything missing (datasets, checkpoints, and the container images themselves) must be pre-positioned by the operator, and the preflight's readability check is the only data step that runs.
S3 credentials use the officially documented AWS env vars, read from the
session environment: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and (for
S3-compatible stores) AWS_ENDPOINT_URL, AWS_DEFAULT_REGION. The aws
CLI and boto3 pick the variables up natively — never run aws configure
and never write ~/.aws/credentials:
set -a; source /path/to/.env; set +a # omit if already exported
aws s3 ls "s3://$S3_BUCKET_NAME/..." # reads AWS_* from the environmentIf a session provides only the legacy TAO names (ACCESS_KEY, SECRET_KEY,
S3_ENDPOINT_URL, CLOUD_REGION), map them once, scoped to the command:
AWS_ACCESS_KEY_ID="$ACCESS_KEY" AWS_SECRET_ACCESS_KEY="$SECRET_KEY" aws s3 ...
HF_TOKEN / NGC_KEY pass through unchanged for PTM pulls. Never pass a
credential as a CLI argument (-p, --token, -e KEY=value); use
--password-stdin or -e VAR (no value).
Pick per backend from what the cluster/daemon actually offers:
The path the spec references is readable from the compute frame (not the launcher's), and the output destination persists after the container exits.
Probe in the compute's frame of reference (in-container aws s3 cp/touch on
the resolved results_dir, or a kubectl run/srun probe) — a green aws s3 ls on the launcher is not proof the pod can read the data (managed
backends inject different creds into the compute container).
s5cmd cp 's3://.../*' <stage> or aws s3 sync.aws s3 cp.references/selective_download.py (below).tar -xzf X -C <dir> --strip-components=1 guarded by a .extracted marker (idempotent).ngc:// / hf://): huggingface-cli download / ngc registry model download-version, then author the local path.After staging, author the spec with local paths and run the verify gate.
TAO_RESULTS_ROOT set → write to that mount, no upload.S3_BUCKET_NAME set → upload to s3://$S3_BUCKET_NAME/results/$TAO_JOB_ID/.SLURM: never set S3_BUCKET_NAME (Lustre-only); run any upload on the login
node, not inside the GPU allocation. Upload with excludes:
aws s3 sync <local>/ s3://... --exclude '.tao/*' <upload_excludes...>.
Download only the files an annotation references (e.g. the video column),
preserving relative paths, into a local staging dir:
set -a; source /path/to/.env; set +a # omit if already exported
python references/selective_download.py \
--annotation /path/to/annotation.parquet \
--key video \
--bucket "$S3_BUCKET_NAME" --src-prefix datasets/clips \
--dest /data/stage/clips--key is repeatable or comma-separated; --format overrides extension
inference (parquet/jsonl/json/csv).
references/selective_download.py — annotation-driven selective download (boto3 + pandas). Unit tests live in references/tests/; run with python -m pytest.© 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
SKILL.md and 7 other files (references) in skills/tao-data-io of NVIDIA/skills.
Open the folder on GitHubat commit 67a13c0
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in NVIDIA/skills, which our catalogue first saw on October 7, 2026.
Tao Data Io 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Tao Data Io this skillNVIDIA/skills | 3.5k | 1 repos | ~1.5k | Automated safety check: Warn | Apache-2.0 | |
| Logfire Infrastructurepydantic/skills | 140 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Ksaildevantler-tech/ksail | 165 | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| Aspire DeploymentCommunityToolkit/Aspire | 629 | — | ~4.5k | Automated safety check: Notes | MIT | |
| Container Orchestrationaiskillstore/marketplace | 430 | — | ~1.4k | Automated safety check: Notes | MIT | |
| Deployment Automationaiskillstore/marketplace | 430 | 1 repos | ~3k | Automated safety check: Notes | None |
pydantic/skills
Monitor hosts, Docker containers, Kubernetes clusters, database/queue/cache servers, and cloud-provider metrics with Pydantic Logfire — no application code required.
devantler-tech/ksail
Use the ksail CLI to spin up and manage Kubernetes clusters (Kind/K3d/Talos/vCluster/KWOK — local via Docker; EKS — cloud via AWS) and GitOps workloads declaratively.
CommunityToolkit/Aspire
WORKFLOW SKILL — Deploy Aspire apps from AppHost models to Docker Compose, Kubernetes, Azure, AWS, or preview Radius.
aiskillstore/marketplace
Docker, Kubernetes, and AWS ECS/Fargate patterns. An agent skill from aiskillstore/marketplace.
aiskillstore/marketplace
Automate application deployment to cloud platforms and servers.
LeoYeAI/openclaw-master-skills
Scan infrastructure-as-code, cloud configurations, and find secrets.
NVIDIA/skills
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.
NVIDIA/skills
Generates, validates, compares and explains HOLOLINK_def.svh macro files for the HSB IP, using bundled Python scripts and asking before it writes anything.
NVIDIA/skills
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.
NVIDIA/skills
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.
NVIDIA/skills
Orchestrates video data augmentation and auto-labeling workflows on OSMO, from flow selection and preflight checks to submission, monitoring and output download.
NVIDIA/skills
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.
Categories
The data-mover for TAO jobs — decides the storage tier (A pre-positioned mount with zero fetch / B volume-from-S3 / C ephemeral in-compute fetch), stages inputs (bulk + annotation-selective +…. Tao Data Io is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. The data-mover for TAO jobs — decides the storage tier (A pre-positioned mount with zero fetch / B volume-from-S3 / C ephemeral in-compute fetch), stages inputs (bulk + annotation-selective + archive extract + HF/NGC PTM), maps credentials to env, routes outputs 3-way with upload-excludes, and runs the compute-frame verify gate.
Tao Data Io fits situations like: phrases include stage inputs; mount the dataset; upload TAO results; download only referenced files.
Run `npx skills add NVIDIA/skills --skill tao-data-io -a claude-code`. Or copy the skill folder (skills/tao-data-io in NVIDIA/skills) into .claude/skills/tao-data-io in your project. Claude Code loads it when a task matches its description.
Run `npx skills add NVIDIA/skills --skill tao-data-io -a codex`. Or copy the skill folder (skills/tao-data-io in NVIDIA/skills) into .agents/skills/tao-data-io in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/skills --skill tao-data-io -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tao-data-io, .gemini/skills/tao-data-io, .github/skills/tao-data-io and .opencode/skills/tao-data-io in your project.
Going by SKILL.md and its folder, Tao Data Io needs Python for the scripts in its folder, the command-line tools its instructions call (aws, python, kubectl and huggingface-cli) and credentials named AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, ACCESS_KEY and SECRET_KEY. Our summary lists: Python 3; Docker; A credential in AWS_SECRET_ACCESS_KEY; A credential in ACCESS_KEY. Its frontmatter pre-approves these tools: Read, Bash. Compatibility (from SKILL.md): Requires aws CLI or s5cmd on the staging host, plus Python 3.10+ with boto3 and pandas/pyarrow for annotation-selective download. No nvidia-tao-sdk, no fsspec/s3fs. Credentials are read from the process environment, whether exported in the user's shell or sourced from a user-approved env file..
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.
Our automated static check of SKILL.md flagged 1 warning(s): mentions a credentials file (ssh keys, cloud or package-manager tokens). Read the flagged lines before installing; the check is not a guarantee either way.
Tao Data Io 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.
About 1.5k tokens (SKILL.md is roughly 6k 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 3.7k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Tao Data Io: Logfire Infrastructure (pydantic/skills, 140 stars), Ksail (devantler-tech/ksail, 165 stars), Aspire Deployment (CommunityToolkit/Aspire, 629 stars) and Container Orchestration (aiskillstore/marketplace, 430 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.