Holoscan Install Container
NVIDIA/skills
Install Holoscan SDK via the NGC Docker container. An agent skill from NVIDIA/skills.
Diagnose and fix Cosmos3 environment, installation, and runtime errors.
Install Cosmos3 Env Troubleshoot
$ npx skills add NVIDIA/cosmos-framework --skill cosmos3-env-troubleshoot -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NVIDIA/cosmos-framework cosmos3-env-troubleshoot --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/cosmos-framework.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/cosmos3-env-troubleshoot .claude/skills/cosmos3-env-troubleshoot && 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 "cosmos3-env-troubleshoot" agent skill from https://github.com/NVIDIA/cosmos-framework/tree/main/.agents/skills/cosmos3-env-troubleshoot into .claude/skills/cosmos3-env-troubleshoot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cosmos3-env-troubleshoot", 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/cosmos-framework/tree/main/.agents/skills/cosmos3-env-troubleshootType 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/cosmos-framework --skill cosmos3-env-troubleshoot -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NVIDIA/cosmos-framework cosmos3-env-troubleshoot --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/cosmos-framework.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/cosmos3-env-troubleshoot .agents/skills/cosmos3-env-troubleshoot && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cosmos3-env-troubleshoot" agent skill from https://github.com/NVIDIA/cosmos-framework/tree/main/.agents/skills/cosmos3-env-troubleshoot into .agents/skills/cosmos3-env-troubleshoot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cosmos3-env-troubleshoot", 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/cosmos-framework --skill cosmos3-env-troubleshoot -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NVIDIA/cosmos-framework cosmos3-env-troubleshoot --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/cosmos-framework.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/cosmos3-env-troubleshoot .cursor/skills/cosmos3-env-troubleshoot && 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 "cosmos3-env-troubleshoot" agent skill from https://github.com/NVIDIA/cosmos-framework/tree/main/.agents/skills/cosmos3-env-troubleshoot into .cursor/skills/cosmos3-env-troubleshoot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cosmos3-env-troubleshoot", 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/cosmos-framework.git --path .agents/skills/cosmos3-env-troubleshoot--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/cosmos-framework --skill cosmos3-env-troubleshoot -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NVIDIA/cosmos-framework cosmos3-env-troubleshoot --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/cosmos-framework.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/cosmos3-env-troubleshoot .gemini/skills/cosmos3-env-troubleshoot && 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 "cosmos3-env-troubleshoot" agent skill from https://github.com/NVIDIA/cosmos-framework/tree/main/.agents/skills/cosmos3-env-troubleshoot into .gemini/skills/cosmos3-env-troubleshoot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cosmos3-env-troubleshoot", 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/cosmos-framework cosmos3-env-troubleshootInstalls 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/cosmos-framework --skill cosmos3-env-troubleshoot -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NVIDIA/cosmos-framework.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/cosmos3-env-troubleshoot .github/skills/cosmos3-env-troubleshoot && 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 "cosmos3-env-troubleshoot" agent skill from https://github.com/NVIDIA/cosmos-framework/tree/main/.agents/skills/cosmos3-env-troubleshoot into .github/skills/cosmos3-env-troubleshoot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cosmos3-env-troubleshoot", 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/cosmos-framework --skill cosmos3-env-troubleshoot -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/cosmos-framework cosmos3-env-troubleshoot --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/cosmos-framework.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/cosmos3-env-troubleshoot .opencode/skills/cosmos3-env-troubleshoot && 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 "cosmos3-env-troubleshoot" agent skill from https://github.com/NVIDIA/cosmos-framework/tree/main/.agents/skills/cosmos3-env-troubleshoot into .opencode/skills/cosmos3-env-troubleshoot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cosmos3-env-troubleshoot", 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.
Facts
- Skill name
cosmos3-env-troubleshoot- GitHub stars
- 560
- Token cost
- ~1.3k tokens
- SKILL.md length
- 364 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Diagnose and fix Cosmos3 environment, installation, and runtime errors.
- Works in 3 steps: Match against known errors → If no documented fix matches, try common… → If still unresolved, generate a bug report
- The user encounters an ImportError
- SKILL.md covers When to use this skill, Path convention, Step 1: Match against known… and Step 2: If no documented fix…, plus 1 more section
- Calls uv, python and curl; reaches astral.sh; needs HF_TOKEN
What it does
Cosmos3 Env Troubleshoot is an agent skill from NVIDIA/cosmos-framework, published by the product's own GitHub organization. Diagnose and fix Cosmos3 environment, installation, and runtime errors. Use when the user encounters an ImportError, ModuleNotFoundError, CUDA error, Docker error, checkpoint download failure, or any traceback during setup or inference.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Containers. It works with CUDA, Docker and Python. The repository describes itself as: Our inference and training framework to run on the Cosmos Models.
When your agent uses it
- The user encounters an ImportError
- ModuleNotFoundError
- Checkpoint download failure
- Any traceback during setup
Example prompts
- “/cosmos3-env-troubleshoot”
Requirements
- Python 3
- Docker
Workflow steps
3 steps, taken from the step headings in SKILL.md.
- Match against known errors
- If no documented fix matches, try common remediation
- If still unresolved, generate a bug report
What it can do on your machine
Read from SKILL.md and the folder at commit f44bc47. 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
Shell commands in SKILL.md call:
uvpythoncurlsh
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
astral.sh
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
HF_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Cosmos3 Env Troubleshoot loads about 1.3k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 364 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.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteRuns commands with sudoSKILL.md:33
docs/setup.md` § Docker Container — run `sudo nvidia-ctk runtime configure --runtime=docker` | - NotePipes a well-known installer script into a shellSKILL.md:66
curl -LsSf https://astral.sh/uv/install.sh | sh
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 364 words (~1,308 tokens).
“All paths below are relative to this file's location (.agents/skills/cosmos3-env-troubleshoot/).”
- name
- cosmos3-env-troubleshoot
Files
Just SKILL.md in .agents/skills/cosmos3-env-troubleshoot of NVIDIA/cosmos-framework.
Open the folder on GitHubat commit f44bc47
Compare with similar skills
Cosmos3 Env Troubleshoot 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 |
|---|---|---|---|---|---|---|
| Cosmos3 Env Troubleshoot this skillNVIDIA/cosmos-framework | 560 | — | ~1.3k | Automated safety check: Notes | Custom licence | |
| Holoscan Install ContainerNVIDIA/skills | 3.6k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Cuopt InstallNVIDIA/skills | 3.6k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Migrate Workflow Ec2 To Osdcpytorch/test-infra | 113 | — | ~2k | Automated safety check: Pass | Custom licence | |
| Generate Nemo Gym Envadithya-s-k/FineEnvs | 461 | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Generate Ors Envadithya-s-k/FineEnvs | 461 | — | ~2.3k | Automated safety check: Notes | Apache-2.0 |
Similar skills
- Official
- Official
Cuopt Install
NVIDIA/skills
Install cuOpt for Python, C, or server via pip, conda, or Docker; verify the install.
Migrate Workflow Ec2 To Osdc
pytorch/test-infra
Step-by-step playbook for migrating a pytorch/pytorch .github/workflows/.yml from EC2 to OSDC (ARC) runners — covers both dial-up and 100% opt-in patterns, with the inputs that must be plumbed…
Generate Nemo Gym Env
adithya-s-k/FineEnvs
Builds a NeMo Gym (NVIDIA) variant of an RL environment. An agent skill from adithya-s-k/FineEnvs.
Generate Ors Env
adithya-s-k/FineEnvs
Builds an Open Reward Standard (ORS) variant of an RL environment using the official openreward Python package.
Verify
lkmeta/txtify
Verify a Txtify change end-to-end. An agent skill from lkmeta/txtify.
More from NVIDIA/cosmos-framework
- Official
Cosmos3 Codebase Nav
NVIDIA/cosmos-framework
Navigate the Cosmos3 package codebase to find where parameters, configs, defaults, scripts, and documentation live.
- Official
Cosmos3 Inference
NVIDIA/cosmos-framework
Guide users through running Cosmos3 inference — offline batch generation, online serving with Ray and Gradio, parallelism options, input formats, sampling parameters, and prompt upsampling.
- Official
Cosmos3 Post Training
NVIDIA/cosmos-framework
Guide users through Cosmos3 supervised fine-tuning (SFT) post-training: preparing the example dataset and Wan2.2 VAE, converting the base checkpoint to DCP, launching distributed training (paired…
- Official
Cosmos3 Setup
NVIDIA/cosmos-framework
Guide users through Cosmos3 installation, environment setup, checkpoint downloading, and verification.
Related
Categories
Questions about Cosmos3 Env Troubleshoot
What does Cosmos3 Env Troubleshoot do?
Diagnose and fix Cosmos3 environment, installation, and runtime errors. Cosmos3 Env Troubleshoot is an agent skill from NVIDIA/cosmos-framework, published by the product's own GitHub organization. Diagnose and fix Cosmos3 environment, installation, and runtime errors.
When should I use Cosmos3 Env Troubleshoot?
Cosmos3 Env Troubleshoot fits situations like: the user encounters an ImportError; moduleNotFoundError; checkpoint download failure; any traceback during setup.
How do I install Cosmos3 Env Troubleshoot in Claude Code?
Run `npx skills add NVIDIA/cosmos-framework --skill cosmos3-env-troubleshoot -a claude-code`. Or copy the skill folder (.agents/skills/cosmos3-env-troubleshoot in NVIDIA/cosmos-framework) into .claude/skills/cosmos3-env-troubleshoot in your project. Claude Code loads it when a task matches its description.
How do I install Cosmos3 Env Troubleshoot in Codex?
Run `npx skills add NVIDIA/cosmos-framework --skill cosmos3-env-troubleshoot -a codex`. Or copy the skill folder (.agents/skills/cosmos3-env-troubleshoot in NVIDIA/cosmos-framework) into .agents/skills/cosmos3-env-troubleshoot in your project. Codex loads it when a task matches its description.
Can I use Cosmos3 Env Troubleshoot 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/cosmos-framework --skill cosmos3-env-troubleshoot -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cosmos3-env-troubleshoot, .gemini/skills/cosmos3-env-troubleshoot, .github/skills/cosmos3-env-troubleshoot and .opencode/skills/cosmos3-env-troubleshoot in your project.
What does Cosmos3 Env Troubleshoot need to run?
Going by SKILL.md and its folder, Cosmos3 Env Troubleshoot needs the command-line tools its instructions call (uv, python, curl and sh) and credentials named HF_TOKEN. Our summary lists: Python 3; Docker.
Does Cosmos3 Env Troubleshoot access the network?
SKILL.md names 1 domain. In commands or code: astral.sh; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Cosmos3 Env Troubleshoot safe to install?
Our automated static check of SKILL.md found notes only (runs commands with sudo; pipes a well-known installer script into a shell), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Cosmos3 Env Troubleshoot use?
Cosmos3 Env Troubleshoot has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Cosmos3 Env Troubleshoot use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Cosmos3 Env Troubleshoot?
Skills that share tags, products or a category with Cosmos3 Env Troubleshoot: Holoscan Install Container (NVIDIA/skills, 3.6k stars), Cuopt Install (NVIDIA/skills, 3.6k stars), Migrate Workflow Ec2 To Osdc (pytorch/test-infra, 113 stars) and Generate Nemo Gym Env (adithya-s-k/FineEnvs, 461 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cosmos3 Env Troubleshoot?
NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/cosmos-framework, which has 560 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 10, 2026.
Source: NVIDIA/cosmos-framework on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.