CLIP Image-Text Matching
Orchestra-Research/AI-Research-SKILLs
Explains OpenAI's CLIP model for zero-shot image classification, image-text similarity, semantic image search and content moderation, with install steps and code patterns.
Grade or filter workflow HDF5 episodes with an OpenAI-compatible vision model.
$ npx skills add NVIDIA/skills --skill i4h-workflow-dataset-annotate -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NVIDIA/skills i4h-workflow-dataset-annotate --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/i4h-workflow-dataset-annotate .claude/skills/i4h-workflow-dataset-annotate && 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 "i4h-workflow-dataset-annotate" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/i4h-workflow-dataset-annotate into .claude/skills/i4h-workflow-dataset-annotate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i4h-workflow-dataset-annotate", 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/i4h-workflow-dataset-annotateType 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 i4h-workflow-dataset-annotate -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NVIDIA/skills i4h-workflow-dataset-annotate --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/i4h-workflow-dataset-annotate .agents/skills/i4h-workflow-dataset-annotate && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "i4h-workflow-dataset-annotate" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/i4h-workflow-dataset-annotate into .agents/skills/i4h-workflow-dataset-annotate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i4h-workflow-dataset-annotate", 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 i4h-workflow-dataset-annotate -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NVIDIA/skills i4h-workflow-dataset-annotate --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/i4h-workflow-dataset-annotate .cursor/skills/i4h-workflow-dataset-annotate && 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 "i4h-workflow-dataset-annotate" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/i4h-workflow-dataset-annotate into .cursor/skills/i4h-workflow-dataset-annotate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i4h-workflow-dataset-annotate", 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/i4h-workflow-dataset-annotate--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 i4h-workflow-dataset-annotate -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NVIDIA/skills i4h-workflow-dataset-annotate --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/i4h-workflow-dataset-annotate .gemini/skills/i4h-workflow-dataset-annotate && 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 "i4h-workflow-dataset-annotate" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/i4h-workflow-dataset-annotate into .gemini/skills/i4h-workflow-dataset-annotate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i4h-workflow-dataset-annotate", 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 i4h-workflow-dataset-annotateInstalls 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 i4h-workflow-dataset-annotate -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/i4h-workflow-dataset-annotate .github/skills/i4h-workflow-dataset-annotate && 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 "i4h-workflow-dataset-annotate" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/i4h-workflow-dataset-annotate into .github/skills/i4h-workflow-dataset-annotate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i4h-workflow-dataset-annotate", 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 i4h-workflow-dataset-annotate -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 i4h-workflow-dataset-annotate --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/i4h-workflow-dataset-annotate .opencode/skills/i4h-workflow-dataset-annotate && 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 "i4h-workflow-dataset-annotate" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/i4h-workflow-dataset-annotate into .opencode/skills/i4h-workflow-dataset-annotate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i4h-workflow-dataset-annotate", 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.
i4h-workflow-dataset-annotateGrade or filter workflow HDF5 episodes with an OpenAI-compatible vision model.
I4h Workflow Dataset Annotate is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Grade or filter workflow HDF5 episodes with an OpenAI-compatible vision model. Use for visual success labels; do not use for replay, policy evaluation, or recordings without frames.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `BENCHMARK.md`, `evals/evals.json` and `skill-card.md`).
It sits in AI & LLM Engineering, covering Computer vision. It works with OpenAI. 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.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 0e0d506. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
uvgitFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
github.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
I4H_AGENT_VL_API_KEYI4H_AGENT_API_KEYOPENAI_API_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
I4h Workflow Dataset Annotate loads about 1.5k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 489 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 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.
The full file from NVIDIA/skills at commit 0e0d506, republished under its Apache-2.0 licence (© NVIDIA). 489 words, ~1,472 tokens.
.claude/skills/i4h-workflow-dataset-annotate/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.Grade sampled camera frames against a natural-language success criterion while keeping VLM labels separate from simulator success.
export I4H_WORKFLOWS_REPO_URL="${I4H_WORKFLOWS_REPO_URL:-https://github.com/isaac-for-healthcare/i4h-workflows}"
I4H_REPO_DIR_NAME="${I4H_WORKFLOWS_REPO_URL%/}"
I4H_REPO_DIR_NAME="${I4H_REPO_DIR_NAME##*/}"
I4H_REPO_DIR_NAME="${I4H_REPO_DIR_NAME##*:}"
I4H_REPO_DIR_NAME="${I4H_REPO_DIR_NAME%.git}"
[ -n "$I4H_REPO_DIR_NAME" ] || { echo "Cannot derive a checkout name from I4H_WORKFLOWS_REPO_URL" >&2; exit 2; }
ROOT="${I4H_WORKFLOWS:-$(git rev-parse --show-toplevel 2>/dev/null)}"
if [ ! -d "$ROOT/workflows/i4h_workflows" ]; then
ROOT="${I4H_WORKFLOWS:-$HOME/$I4H_REPO_DIR_NAME}"
[ -d "$ROOT/workflows/i4h_workflows" ] || git clone "$I4H_WORKFLOWS_REPO_URL" "$ROOT"
fi
export I4H_WORKFLOWS="$ROOT"
cd "$ROOT"
find runs -name '*.hdf5' -type f -printf '%T@ %p\n' | sort -nr | headTreat the resolver above as part of the skill contract: a hosted copy may run outside the base repository, so never assume the current checkout contains workflows/i4h_workflows. I4H_WORKFLOWS_REPO_URL selects the clone source. When I4H_WORKFLOWS is unset, derive the fallback directory from that URL; set I4H_WORKFLOWS only to reuse or choose a specific destination. Never replace an existing checkout.
Use the explicit/current-chain HDF5. “All recorded episodes” means every episode in that selected file, not every historical run. Inspect it and use the user's explicit success criterion when supplied; otherwise combine the source Scene manifest instruction with the workflow's visible terminal goal semantics. Phrase placement success as the object reaching and remaining at its target, not as the robot continuing to hold it.
Use a caller-provided OpenAI-compatible vision endpoint/model first. Local Agent exposes that configuration as I4H_AGENT_VL_BASE_URL, I4H_AGENT_VL_MODEL, and either I4H_AGENT_VL_API_KEY or I4H_AGENT_API_KEY. Map those generic agent variables to the annotator without printing the credential:
VLM_ARGS=()
if [ -n "${I4H_AGENT_VL_BASE_URL:-}" ] && [ -n "${I4H_AGENT_VL_MODEL:-}" ]; then
I4H_VLM_URL="${I4H_AGENT_VL_BASE_URL%/}"
case "$I4H_VLM_URL" in */v1) ;; *) I4H_VLM_URL="$I4H_VLM_URL/v1" ;; esac
export I4H_VLM_URL
export OPENAI_API_KEY="${I4H_AGENT_VL_API_KEY:-${I4H_AGENT_API_KEY:-EMPTY}}"
VLM_ARGS=(--model "$I4H_AGENT_VL_MODEL")
fiIf no caller-provided endpoint/model is available, start the repository's local service:
tools/annotator/scripts/vllm.sh ensureRecord whether this invocation started it. Do not hard-code a model name in the skill; use the CLI/service defaults unless the user supplies one.
uv run --project tools/annotator i4h-annotator \
--task "<success criterion>" \
--dry-run \
offline /absolute/path/to/recording.hdf5Use this to verify cameras and sampled frames without transmitting images.
RUN_DIR="$(pwd)/runs/<workflow>/$(date +%Y%m%d_%H%M%S)"
mkdir -p "$RUN_DIR"
uv run --project tools/annotator i4h-annotator \
--task "<success criterion>" \
"${VLM_ARGS[@]}" \
offline /absolute/path/to/recording.hdf5 \
--writeAdd global --base-url, --model, --camera, or --frames only when selected. Add offline --node only for a requested segment. Add --filter "$RUN_DIR/filtered.hdf5" only when filtering was requested; a summarize-only prompt must grade all episodes without requiring at least one success. Keep credentials in environment variables; never print them.
Stop the local VLM only if this invocation started it:
tools/annotator/scripts/vllm.sh stopInspect the annotator summary. If filtering was requested, also inspect the filtered file:
uv run --project tools/dataset i4h-dataset inspect "$RUN_DIR/filtered.hdf5" --segmentsRequire a verdict for every selected episode and reconcile pass/fail counts plus filtered counts when applicable. Treat endpoint errors, absent cameras, partial writes, and unexplained zero-episode output as failure. An all-failure verdict set is a valid completed grading run for summarize-only prompts; it is not a valid filtered dataset.
Check camera sampling before endpoint/authentication errors. Never accept partial writes or a filtered file with an unexplained zero count.
Require a readable workflow HDF5 with camera frames and, unless dry-running, a reachable OpenAI-compatible vision endpoint.
Visual grading cannot recover missing frames or prove simulator state that is not visible.
Run annotation on all recorded episodes and summarize. → select the current HDF5, grade every episode, verify the filtered file, and report pass/fail counts.Report source HDF5, selected criterion/camera/model/endpoint origin, graded pass/fail counts, filtered path/count when requested, dry-run result if used, and local-service cleanup.
© 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 4 other files in skills/i4h-workflow-dataset-annotate of NVIDIA/skills.
Open the folder on GitHubat commit 0e0d506
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.
I4h Workflow Dataset Annotate 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 |
|---|---|---|---|---|---|---|
| I4h Workflow Dataset Annotate this skillNVIDIA/skills | 3.5k | 1 repos | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| CLIP Image-Text MatchingOrchestra-Research/AI-Research-SKILLs | 13k | 8 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Openai Visionbenchflow-ai/skillsbench | 1.8k | — | ~5k | Automated safety check: Pass | Apache-2.0 | |
| Visionaiskillstore/marketplace | 430 | — | ~1.1k | Automated safety check: Pass | None | |
| ModLens Image Vision Bridgeliustack/modlens | 4.1k | — | ~1.3k | Automated safety check: Notes | MIT | |
| Visionxiincs/claude-code-vision-skill | 170 | — | ~1.2k | Automated safety check: Pass | MIT |
Orchestra-Research/AI-Research-SKILLs
Explains OpenAI's CLIP model for zero-shot image classification, image-text similarity, semantic image search and content moderation, with install steps and code patterns.
benchflow-ai/skillsbench
Analyze images and multi-frame sequences using OpenAI GPT vision models
aiskillstore/marketplace
See and understand images when you (the current model) have no native vision.
liustack/modlens
Gives text-only models sight by running the modlens CLI on an image path or URL and returning structured JSON evidence with transcribed text, layout and semantics.
xiincs/claude-code-vision-skill
Call vision models (Doubao, Qwen, DeepSeek, OpenAI) to analyze images.
QianWen-AI/qianwen-ai
Generate text, have conversations, write code, reason, and call functions with Qwen models.
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.
Works with
Categories
Grade or filter workflow HDF5 episodes with an OpenAI-compatible vision model. I4h Workflow Dataset Annotate is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Grade or filter workflow HDF5 episodes with an OpenAI-compatible vision model.
I4h Workflow Dataset Annotate fits situations like: visual success labels; do not use for replay; policy evaluation; recordings without frames.
Run `npx skills add NVIDIA/skills --skill i4h-workflow-dataset-annotate -a claude-code`. Or copy the skill folder (skills/i4h-workflow-dataset-annotate in NVIDIA/skills) into .claude/skills/i4h-workflow-dataset-annotate in your project. Claude Code loads it when a task matches its description.
Run `npx skills add NVIDIA/skills --skill i4h-workflow-dataset-annotate -a codex`. Or copy the skill folder (skills/i4h-workflow-dataset-annotate in NVIDIA/skills) into .agents/skills/i4h-workflow-dataset-annotate 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 i4h-workflow-dataset-annotate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/i4h-workflow-dataset-annotate, .gemini/skills/i4h-workflow-dataset-annotate, .github/skills/i4h-workflow-dataset-annotate and .opencode/skills/i4h-workflow-dataset-annotate in your project.
Going by SKILL.md and its folder, I4h Workflow Dataset Annotate needs the command-line tools its instructions call (uv and git) and credentials named I4H_AGENT_VL_API_KEY, I4H_AGENT_API_KEY and OPENAI_API_KEY. Our summary lists: A credential in I4H_AGENT_VL_API_KEY; A credential in I4H_AGENT_API_KEY.
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
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.
I4h Workflow Dataset Annotate 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 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with I4h Workflow Dataset Annotate: CLIP Image-Text Matching (Orchestra-Research/AI-Research-SKILLs, 13k stars), Openai Vision (benchflow-ai/skillsbench, 1.8k stars), Vision (aiskillstore/marketplace, 430 stars) and ModLens Image Vision Bridge (liustack/modlens, 4.1k 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,534 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.