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

Agent skill

Nvwb Project

by brevdev in brevdev/workshop-build-an-agent

Apply when working in a directory containing .project/spec.yaml — provides NVIDIA AI Workbench project awareness for in-container development.

Apache-2.0Auto-check: warnings

Install Nvwb Project

The automated check flagged lines worth reading first. See the safety section below.

skills CLI
$ npx skills add brevdev/workshop-build-an-agent --skill nvwb-project -a claude-code

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

GitHub CLI
$ gh skill install brevdev/workshop-build-an-agent nvwb-project --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/brevdev/workshop-build-an-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/nvwb-project .claude/skills/nvwb-project && 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
nvwb-project
GitHub stars
144
Token cost
~1.5k tokens
SKILL.md length
763 words
Files
13 (incl. references)
Skills in repo
11
Repo updated
First seen
Licence
Apache-2.0

At a glance

Apply when working in a directory containing .project/spec.yaml — provides NVIDIA AI Workbench project awareness for in-container development.

  • Works in 4 steps: Read common-context/context.md for… → Write a clear request to… → Wait for the user to relay it to outer… → …
  • SKILL.md covers Detection, Key Facts, What's Safe to Edit and When Informing the User, plus 5 more sections
  • Runs Shell scripts from its folder; calls curl and npm

What it does

Nvwb Project is an agent skill from brevdev/workshop-build-an-agent. Apply when working in a directory containing .project/spec.yaml — provides NVIDIA AI Workbench project awareness for in-container development. This skill provides context about project structure, environment configuration, and rebuild/restart requirements.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 14 other files, including reference files (for example `hooks/cursor-inner-files.sh`, `hooks/cursor-inner-read.sh` and `hooks/cursor-inner-shell.sh`).

It works with NVIDIA AI Platform. The licence is Apache-2.0.

Example prompts

  • “/nvwb-project”

Requirements

  • Node.js
  • A Bash shell
  • Docker

Workflow steps

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

  1. Read common-context/context.md for current task state
  2. Write a clear request to /project/agent-bridge/inner.md
  3. Wait for the user to relay it to outer agent on their local machine
  4. Read the response from /project/agent-bridge/outer.md

What it can do on your machine

Read from SKILL.md and the folder at commit b5689a7. 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

    Ships script files (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • curl
    • npm

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

  • Network

    No URLs in SKILL.md. Its commands use curl and npm, which can reach the network depending on how they are called.

    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.

Context cost

Nvwb Project loads about 1.5k tokens when it runs, and up to ~6.6k if it reads all its reference files. Until then it costs about 67 tokens; SKILL.md has 763 words of instructions outside code blocks.

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

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: warnings

The automated check found patterns that need a careful read before installing.

  • WarningMentions a credentials file (SSH keys, cloud or package-manager tokens)SKILL.md:74
    s — Workbench adds a matching entry to `~/.ssh/config`. Outer agent can SSH directly using the context name to read and
  • NoteRuns commands with sudoSKILL.md:89
    , `>>`) also run as `workbench`, so use `sudo tee` instead of `sudo command > /path`.

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 brevdev/workshop-build-an-agent at commit b5689a7, republished under its Apache-2.0 licence (© brevdev). 763 words, ~1,466 tokens.

Download SKILL.mdSave it as .claude/skills/nvwb-project/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.
name
nvwb-project
description
Apply when working in a directory containing .project/spec.yaml — provides NVIDIA AI Workbench project awareness for in-container development. This skill provides context about project structure, environment configuration, and rebuild/restart requirements.
user-invocable
false

NVIDIA AI Workbench — In-Container Project Awareness

This skill activates when Codex is working inside an AI Workbench project container (detected by .project/spec.yaml existing in or above the current working directory).

Detection

If .project/spec.yaml exists in the project root, this is a Workbench project. Read it first to understand the project's layout, apps, mounts, and resources.

Key Facts

  • The project root is bind-mounted at /project/ inside the container
  • The nvwb CLI is NOT available inside the container — all nvwb commands must run on the user's local machine (the control plane)
  • This container may be running locally or on a remote — it does not matter for in-container work; the project files are always at /project/
  • Code in layout directories is live-mounted — edits take effect immediately
  • The environment variable AI_WORKBENCH_FLAG=true may be set to detect Workbench context
  • Compose services are reachable by service name (e.g. curl http://api:8080/) via the shared workbench network

What's Safe to Edit

Freely editable — no action needed:

  • Any files in layout directories (code/, data/, models/ or custom paths from spec.yaml)
  • Application code, scripts, notebooks

Requires rebuild — inform user to run nvwb build on the host:

  • apt.txt — system packages
  • requirements.txt — pip packages
  • preBuild.bash — pre-install build script
  • postBuild.bash — post-install build script

Requires restart — inform user to run nvwb close then nvwb open on the host:

  • variables.env — runtime environment variables
  • Mount configuration changes in .project/spec.yaml
  • App definitions in .project/spec.yaml

Edit carefully — validate format:

  • .project/spec.yaml — do not break YAML structure; suggest nvwb validate project-spec after changes

When Informing the User

After editing a build-time or runtime file, always tell the user what action is needed. Examples:

I've updated requirements.txt to add the transformers package. You'll need to run nvwb build on the host to rebuild the container with this change.

I've added CUDA_VISIBLE_DEVICES=0 to variables.env. This will take effect after a container restart — run nvwb close then nvwb open on the host.

Compose Awareness

If compose.yaml or docker-compose.yaml exists, multi-container services may be running alongside the project container:

  • Services communicate over a shared Docker network — use service names as hostnames (e.g. http://api:8080/)
  • /nvwb-shared-volume/ is shared between containers
  • Changes to compose files require nvwb compose down + nvwb compose up on the host — request this via the bridge if running as inner agent
  • Compose services exposed through the Workbench proxy use NVWB_TRIM_PREFIX=true as an environment variable in the service definition (not in spec.yaml)
Show full SKILL.md (375 more words)Show less

Host↔Container Bridge

If /project/agent-bridge/ exists, this project is set up for communication between inner agent (here, in the container) and outer agent (on the user's local machine, where nvwb is installed).

When you need a local-machine action (compose restart, rebuild, nvwb command):

  1. Read common-context/context.md for current task state
  2. Write a clear request to /project/agent-bridge/inner.md
  3. Wait for the user to relay it to outer agent on their local machine
  4. Read the response from /project/agent-bridge/outer.md

Rules: Do not copy files into or out of agent-bridge/ — it is a communication channel, not a file staging area. The content of inner.md and outer.md is unrestricted — include logs, snippets, and diagnostics as needed.

Sandbox: If hooks are configured, your actions are enforced — nvwb commands are blocked (use the bridge), sensitive environment variables are scrubbed from your shell commands, writes inside agent-bridge/ are restricted to your designated files, and reads of sensitive files and hook configuration are blocked. Do not attempt to modify hook configuration or settings files.

Note: if this project is running in a remote context, the bridge files live on the remote machine. The context name (from nvwb list contexts) is also the SSH alias — Workbench adds a matching entry to ~/.ssh/config. Outer agent can SSH directly using the context name to read and write bridge files without involving the user as a relay.

Requests can be rich prose — include what you changed, what you need done, and what you want reported back (logs, curl output, etc.).

See references/agent-bridge.md for templates and the full format guide.

Runtime Constraints

sudo is NOT available in the running container — the container runs as the workbench user without elevated privileges at runtime. If a task requires system-level changes, it must go in preBuild.bash or postBuild.bash.

Build Script Constraints

Build scripts (preBuild.bash, postBuild.bash) run during container image build:

  • They CANNOT reference /project/ — the project directory is not mounted during build
  • Available variables: $NVWB_UID, $NVWB_GID for file ownership
  • Both scripts run as the workbench user (not root) — any write to a system directory requires sudo. This includes mkdir, npm install -g, writing to /usr/local/, etc. Shell redirections (>, >>) also run as workbench, so use sudo tee instead of sudo command > /path.

References

See references/config-files.md for detailed information about each configuration file.

© brevdev, 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 12 other files (references) in .agents/skills/nvwb-project of brevdev/workshop-build-an-agent.

  • SKILL.md
  • hooks/cursor-inner-files.sh
  • hooks/cursor-inner-read.sh
  • hooks/cursor-inner-shell.sh
  • hooks/inner-agent-bash.sh
  • hooks/inner-agent-files.sh
  • hooks/inner-agent-read.sh
  • hooks/outer-agent-bash.sh
  • hooks/outer-agent-files.sh
  • hooks/sensitive-patterns.sh
  • hooks/test-hooks.sh
  • references/agent-bridge.md
  • references/config-files.md

Open the folder on GitHubat commit b5689a7

Compare with similar skills

Nvwb Project 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.

Nvwb Project compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nvwb Project this skillbrevdev/workshop-build-an-agent144—~1.5kAutomated safety check: WarnApache-2.0
Skill InspectorNVIDIA/SkillSpector20k1 repos~1.8kAutomated safety check: PassApache-2.0
LLM Torch Profiler Analysissgl-project/sglang37k2 repos~6.4kAutomated safety check: PassApache-2.0
Embeddings via 9Routerdecolua/9router30k—~604Automated safety check: PassMIT
NEAR AI Cloud Private Inferenceinternet-court/internet-court-skill6.4k2 repos~1.3kAutomated safety check: PassCustom licence
Nemoclaw Maintainer Normalize Title TagsNVIDIA/NemoClaw23k—~693Automated safety check: PassApache-2.0

Similar skills

  • Skill Inspector

    NVIDIA/SkillSpector

    Official

    Decides whether an agent skill is safe to install by combining a SkillSpector static scan with the agent's own source review, ending in APPROVE, CAUTION or REJECT.

    20k GitHub starsUsed in 1 repo~1.8k tokens
    SecurityAuto-check passed

  • LLM Torch Profiler Analysis

    sgl-project/sglang

    Unified LLM torch-profiler triage skill for sglang, vllm, TensorRT-LLM, and TokenSpeed.

    37k GitHub starsUsed in 2 repos~6.4k tokens
    DevelopmentAuto-check passed

  • Embeddings via 9Router

    decolua/9router

    Generates vector embeddings through the 9Router /v1/embeddings endpoint, using models from providers such as OpenAI, Gemini, Mistral and Voyage for RAG and semantic search.

    30k GitHub stars~604 tokensUpdated 7 days ago
    AI & LLM EngineeringAuto-check passed

  • NEAR AI Cloud Private Inference

    internet-court/internet-court-skill

    Shows how to call NEAR AI Cloud through an OpenAI-compatible API and verify that inference ran in a TEE, using attestation checks and signed chat responses.

    6.4k GitHub starsUsed in 2 repos~1.3k tokens
    AI & LLM EngineeringAuto-check passed

  • Nemoclaw Maintainer Normalize Title Tags

    NVIDIA/NemoClaw

    Official

    Remove bracketed NemoClaw tags from GitHub issue and PR titles.

    23k GitHub stars~693 tokensUpdated today
    Marketing & SEOAuto-check passed

  • Nemoclaw Contributor Update Dependencies

    NVIDIA/NemoClaw

    Official

    Audit and implement a NemoClaw dependency version upgrade, including Hermes and base images.

    23k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed

More from brevdev/workshop-build-an-agent

All 11 skills in this repo

  • Setup Workshop

    brevdev/workshop-build-an-agent

    This skill should be used when the user wants to set up, install, deploy, bootstrap, or "spin up" the Build-an-Agent workshop (a.k.a.

    144 GitHub stars~2.3k tokensUpdated yesterday
    Auto-check: notes

  • Setup Workshop Nemoclaw

    brevdev/workshop-build-an-agent

    Set up the NVIDIA "Build an Agent" DevX workshop as a working JupyterLab environment from INSIDE a locked-down OpenShell/NemoClaw sandbox, and hand the user the token URL + access commands.

    144 GitHub stars~5.2k tokensUpdated yesterday
    Auto-check passed

  • Nvwb

    brevdev/workshop-build-an-agent

    Manage NVIDIA AI Workbench projects, contexts, builds, and environments via the nvwb CLI.

    144 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Module 1

    brevdev/workshop-build-an-agent

    This skill should be used when a learner is working through Module 1 ("Build an Agent") of the Build-an-Agent workshop and wants help understanding the concepts, notebooks, or code — e.g.

    144 GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed

  • Module 1

    brevdev/workshop-build-an-agent

    This skill should be used when a learner is working through Module 1 ("Build an Agent") of the Build-an-Agent workshop and wants help understanding the concepts, notebooks, or code — e.g.

    144 GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed

  • Workshop

    brevdev/workshop-build-an-agent

    This skill should be used when a learner wants to navigate or understand the Build-an-Agent workshop as a whole — e.g.

    144 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

Works with

Questions about Nvwb Project

What does Nvwb Project do?

Apply when working in a directory containing .project/spec.yaml — provides NVIDIA AI Workbench project awareness for in-container development. Nvwb Project is an agent skill from brevdev/workshop-build-an-agent.yaml — provides NVIDIA AI Workbench project awareness for in-container development.

How do I install Nvwb Project in Claude Code?

Run `npx skills add brevdev/workshop-build-an-agent --skill nvwb-project -a claude-code`. Or copy the skill folder (.agents/skills/nvwb-project in brevdev/workshop-build-an-agent) into .claude/skills/nvwb-project in your project. Claude Code loads it when a task matches its description.

How do I install Nvwb Project in Codex?

Run `npx skills add brevdev/workshop-build-an-agent --skill nvwb-project -a codex`. Or copy the skill folder (.agents/skills/nvwb-project in brevdev/workshop-build-an-agent) into .agents/skills/nvwb-project in your project. Codex loads it when a task matches its description.

Can I use Nvwb Project 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 brevdev/workshop-build-an-agent --skill nvwb-project -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nvwb-project, .gemini/skills/nvwb-project, .github/skills/nvwb-project and .opencode/skills/nvwb-project in your project.

What does Nvwb Project need to run?

Going by SKILL.md and its folder, Nvwb Project needs a shell for the scripts in its folder and the command-line tools its instructions call (curl and npm). Our summary lists: Node.js; A Bash shell; Docker.

Does Nvwb Project access the network?

SKILL.md contains no URLs. Its commands use curl and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Nvwb Project safe to install?

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.

What licence does Nvwb Project use?

Nvwb Project is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Nvwb Project use?

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. Its references folder adds about 5.1k tokens, read only when the agent opens those files.

What are the alternatives to Nvwb Project?

Skills that share tags, products or a category with Nvwb Project: Skill Inspector (NVIDIA/SkillSpector, 20k stars), LLM Torch Profiler Analysis (sgl-project/sglang, 37k stars), Embeddings via 9Router (decolua/9router, 30k stars) and NEAR AI Cloud Private Inference (internet-court/internet-court-skill, 6.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nvwb Project?

brevdev (a GitHub organization) maintains it in brevdev/workshop-build-an-agent, which has 144 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 7, 2026.

Source: brevdev/workshop-build-an-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.