DGX Station AI Skills for Coding Agents
Give your coding agent (Claude Code, Codex, Gemini CLI, Cursor) DGX Station expertise via an AGENTS.md and on-demand Agent Skills
Skills don't appear in autocomplete / aren't discoverable
Each agent discovers skills from a harness-specific directory in the current directory (or a parent). Check the right one:
| Agent | Expected location |
|---|---|
| Claude Code | .claude/skills/<name>/SKILL.md |
| Codex CLI | .codex/prompts/<name>.md |
| Gemini CLI | .gemini/commands/<name>.md |
| Cursor | .cursor/rules/<name>.mdc |
# Examples — check the directory for your agent
ls -la .claude/skills/
ls -la .codex/prompts/
ls -la .gemini/commands/
ls -la .cursor/rules/
You should see entries for vllm-setup, sglang-setup, mig-configure, and dgx-diagnose.
Check you're in the right directory:
pwd
The agent must be started from the directory containing the harness directory, or a subdirectory of it.
Context file not loaded
If the agent gives generic answers without DGX Station awareness, the context file isn't being picked up. Each agent reads a different filename — verify the one for your agent exists:
| Agent | Expected filename |
|---|---|
| Claude Code | CLAUDE.md (also reads AGENTS.md as fallback) |
| Codex CLI | AGENTS.md |
| Gemini CLI | GEMINI.md |
| Cursor | AGENTS.md |
# Verify the file exists for your agent
cat AGENTS.md | head -5
cat CLAUDE.md | head -5
cat GEMINI.md | head -5
# Restart the agent in the correct directory
cd ~/your-project
claude # or codex, gemini, etc.
All four agents read the context file from the working directory (and parent directories up to the project root).
Skill gives outdated information
The skills contain validated container versions and parameters as of the publication date. If a newer container is available, edit the canonical source and re-install:
nano /path/to/playbook/assets/skills/vllm-setup/SKILL.md
/path/to/playbook/assets/install.sh all --force
Or edit the installed copy directly:
# Claude Code
nano .claude/skills/vllm-setup/SKILL.md
# Codex
nano .codex/prompts/vllm-setup.md
# Gemini CLI
nano .gemini/commands/vllm-setup.md
# Cursor
nano .cursor/rules/vllm-setup.mdc
TIP
Skills are plain markdown — you can version them in git alongside your project code.
"Both GPUs cannot be used" errors
This is the mixed-coherency constraint working as intended. If you see CUDA errors when using --gpus all:
# Find the GB300 index
nvidia-smi --query-gpu=index,name --format=csv,noheader
# Use device-specific targeting
docker run --gpus '"device=1"' ...
The AGENTS.md covers this constraint, but if you removed that section, add it back — it's the most important piece of DGX Station knowledge.
Skills conflict with existing project directory
If your project already has a .claude/, .codex/, .gemini/, or .cursor/ directory with its own contents, install.sh is additive for skill directories — it adds the new skill files alongside whatever you already have and warns on collision rather than overwriting.
For context files (AGENTS.md, CLAUDE.md, GEMINI.md), the installer refuses to overwrite an existing file. Pass --force to override, or merge the new content manually:
# See what would be written
diff /path/to/playbook/assets/AGENTS.md ./AGENTS.md
# Force overwrite
/path/to/playbook/assets/install.sh claude . --force
Installer reports "WROTE" for some files but "SKIP" for others
That's the safe-by-default behavior. The installer skips any file that already exists, prints a warning, and continues with the rest. To get a clean install, either:
- Delete the existing files first:
rm -rf .claude/skills/{vllm-setup,sglang-setup,mig-configure,dgx-diagnose} - Or pass
--force(only affects context files; skill files are still skipped if present)