Backend Gap Report
AMD-AGI/Primus
Compare a Primus backend against an upstream repository or reference, verify git state, dependencies, directory changes, and integration coupling, then generate comparison reports, dashboard…
Manage NVIDIA AI Workbench projects, contexts, builds, and environments via the nvwb CLI.
$ npx skills add brevdev/workshop-build-an-agent --skill nvwb -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brevdev/workshop-build-an-agent nvwb --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/brevdev/workshop-build-an-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/nvwb .claude/skills/nvwb && 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 "nvwb" agent skill from https://github.com/brevdev/workshop-build-an-agent/tree/main/.agents/skills/nvwb into .claude/skills/nvwb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvwb", 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/brevdev/workshop-build-an-agent/tree/main/.agents/skills/nvwbType 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 brevdev/workshop-build-an-agent --skill nvwb -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brevdev/workshop-build-an-agent nvwb --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brevdev/workshop-build-an-agent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/nvwb .agents/skills/nvwb && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "nvwb" agent skill from https://github.com/brevdev/workshop-build-an-agent/tree/main/.agents/skills/nvwb into .agents/skills/nvwb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvwb", 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 brevdev/workshop-build-an-agent --skill nvwb -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brevdev/workshop-build-an-agent nvwb --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brevdev/workshop-build-an-agent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/nvwb .cursor/skills/nvwb && 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 "nvwb" agent skill from https://github.com/brevdev/workshop-build-an-agent/tree/main/.agents/skills/nvwb into .cursor/skills/nvwb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvwb", 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/brevdev/workshop-build-an-agent.git --path .agents/skills/nvwb--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 brevdev/workshop-build-an-agent --skill nvwb -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brevdev/workshop-build-an-agent nvwb --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brevdev/workshop-build-an-agent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/nvwb .gemini/skills/nvwb && 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 "nvwb" agent skill from https://github.com/brevdev/workshop-build-an-agent/tree/main/.agents/skills/nvwb into .gemini/skills/nvwb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvwb", 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 brevdev/workshop-build-an-agent nvwbInstalls 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 brevdev/workshop-build-an-agent --skill nvwb -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brevdev/workshop-build-an-agent.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/nvwb .github/skills/nvwb && 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 "nvwb" agent skill from https://github.com/brevdev/workshop-build-an-agent/tree/main/.agents/skills/nvwb into .github/skills/nvwb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvwb", 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 brevdev/workshop-build-an-agent --skill nvwb -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brevdev/workshop-build-an-agent nvwb --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brevdev/workshop-build-an-agent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/nvwb .opencode/skills/nvwb && 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 "nvwb" agent skill from https://github.com/brevdev/workshop-build-an-agent/tree/main/.agents/skills/nvwb into .opencode/skills/nvwb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvwb", 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.
nvwbManage NVIDIA AI Workbench projects, contexts, builds, and environments via the nvwb CLI.
Nvwb is an agent skill from brevdev/workshop-build-an-agent. Manage NVIDIA AI Workbench projects, contexts, builds, and environments via the nvwb CLI. This skill should be used when the user wants to create, clone, build, manage, or configure AI Workbench projects, contexts, or environments.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `references/cli-reference.md`, `references/codex-in-container.md` and `references/nvwb-brev.md`).
It sits in Development. It works with NVIDIA AI Platform and Git. The licence is Apache-2.0.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit b5689a7. 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:
sshFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use ssh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Nvwb loads about 1.1k tokens when it runs, and up to ~13k if it reads all its reference files. Until then it costs about 59 tokens; SKILL.md has 468 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 brevdev/workshop-build-an-agent at commit b5689a7, republished under its Apache-2.0 licence (© brevdev). 468 words, ~1,115 tokens.
.claude/skills/nvwb/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.NVIDIA AI Workbench is a lightweight, containerized development platform for GPU-accelerated AI/ML workflows. Every project is a Git repo with a .project/spec.yaml that defines the container environment. It supports Docker and Podman as container runtimes.
The nvwb CLI always runs on the local machine — the user's laptop or desktop. From there it manages contexts, which may be local (container on the same machine) or remote (container on a server or cloud instance accessed via SSH). Codex using this skill is on the local machine.
The user wants help with: $ARGUMENTS
.project/spec.yaml)--is-sensitive) are masked in output. Values are never committed to Git. Projects may declare required secret variable names in spec.yaml under execution.secrets.Before taking action, check the current state:
nvwb list contexts # What locations are configured?
nvwb status # Is a project open? Is the container running?
nvwb list projects # What projects exist in the active context?Build-time (changes require nvwb build):
apt.txt — system packagesrequirements.txt — pip packagespreBuild.bash / postBuild.bash — custom build scriptsspec.yamlRuntime (changes require container restart: nvwb close + nvwb open):
variables.env — environment variablesspec.yamlNo action needed:
/project/| Variable | Available | Description |
|---|---|---|
$NVWB_UID | Build-time | User ID for file ownership in build scripts |
$NVWB_GID | Build-time | Group ID for file ownership in build scripts |
$PROXY_PREFIX | Runtime | URL prefix for proxied web apps |
When a build fails:
requirements.txt, missing apt dependency, bash syntax error in build scriptsproject-runtime-info/ inside the context's workbench directory — this is on the machine running the Workbench service, not necessarily the local machine. Find the right path first:cat ~/.nvwb/contexts.json # workbenchDir field for each context~/.nvwb/project-runtime-info/<workbenchDir>/project-runtime-info/ on the remote — access via ssh <context-name> "ls <workbenchDir>/project-runtime-info/"nvwb build againnvwb build --full-build for a clean rebuild| Change | Action |
|---|---|
| Edit code files | Nothing |
Edit apt.txt, requirements.txt, build scripts | nvwb build |
Edit variables.env | nvwb close then nvwb open |
Change mounts or app config in spec.yaml | nvwb close then nvwb open |
| Change compose services | nvwb compose down then nvwb compose up |
See the reference files for detailed information:
references/cli-reference.md — Complete CLI command referencereferences/spec-reference.md — spec.yaml structure and fieldsreferences/project-structure.md — Project file layout and rolesreferences/workflows.md — Multi-step workflow recipesreferences/nvwb-brev.md — Brev cloud GPU integration: stoppability, interactive vs manual bootstrap, org management, Brev CLI referencereferences/codex-in-container.md — Running Codex inside the container, credential persistence, and the host↔container bridge pattern© 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
SKILL.md and 6 other files (references) in .agents/skills/nvwb of brevdev/workshop-build-an-agent.
Open the folder on GitHubat commit b5689a7
Nvwb 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 |
|---|---|---|---|---|---|---|
| Nvwb this skillbrevdev/workshop-build-an-agent | 143 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Backend Gap ReportAMD-AGI/Primus | 130 | — | ~3.4k | Automated safety check: Pass | Custom licence | |
| Respond To IssueNVIDIA/Megatron-LM | 18k | — | ~913 | Automated safety check: Pass | Custom licence | |
| Jetson Promote ImageNVIDIA/skills | 3.5k | — | ~5k | Automated safety check: Notes | Apache-2.0 | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT |
AMD-AGI/Primus
Compare a Primus backend against an upstream repository or reference, verify git state, dependencies, directory changes, and integration coupling, then generate comparison reports, dashboard…
NVIDIA/Megatron-LM
Research and draft a response to a GitHub issue or question from an external contributor.
NVIDIA/skills
A skill your agent uses to promote overlay files and built artifacts into the staged BSP image.
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Egonex-AI/Understand-Anything
Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.
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.
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.
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.
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.
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.
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.
Works with
Categories
Manage NVIDIA AI Workbench projects, contexts, builds, and environments via the nvwb CLI. Nvwb is an agent skill from brevdev/workshop-build-an-agent. Manage NVIDIA AI Workbench projects, contexts, builds, and environments via the nvwb CLI.
Nvwb fits situations like: wants to create; configure AI Workbench projects.
Run `npx skills add brevdev/workshop-build-an-agent --skill nvwb -a claude-code`. Or copy the skill folder (.agents/skills/nvwb in brevdev/workshop-build-an-agent) into .claude/skills/nvwb in your project. Claude Code loads it when a task matches its description.
Run `npx skills add brevdev/workshop-build-an-agent --skill nvwb -a codex`. Or copy the skill folder (.agents/skills/nvwb in brevdev/workshop-build-an-agent) into .agents/skills/nvwb 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 brevdev/workshop-build-an-agent --skill nvwb -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, .gemini/skills/nvwb, .github/skills/nvwb and .opencode/skills/nvwb in your project.
Going by SKILL.md and its folder, Nvwb needs the command-line tools its instructions call (ssh). Our summary lists: Docker.
SKILL.md contains no URLs. Its commands use ssh, which can reach the network depending on how they are called. 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.
Nvwb 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.
About 1.1k tokens (SKILL.md is roughly 4.5k 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 12k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Nvwb: Backend Gap Report (AMD-AGI/Primus, 130 stars), Respond To Issue (NVIDIA/Megatron-LM, 18k stars), Jetson Promote Image (NVIDIA/skills, 3.5k stars) and Finishing a Development Branch (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
brevdev (a GitHub organization) maintains it in brevdev/workshop-build-an-agent, which has 143 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 6, 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.