technical-writing

Guidelines for writing clear, professional technical documentation

Repositório: brevdev/workshop-build-an-agent
Última atividade na origem: 2 de julho de 2026 às 17:30
Idioma detectado do SKILL.md: inglês
Estrelas: 133
Forks: 84

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/brevdev/workshop-build-an-agent --skill technical-writing

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

setup-workshop-nemoclaw-operator

Operator/host side of running the NVIDIA "Build an Agent" DevX workshop inside an OpenShell/NemoClaw sandbox. ⚠️ NOT the default workshop-setup path: for a generic "set up the workshop" request, use the `setup-workshop` skill (the standard bare-metal/Brev/AI-Workbench installer). Invoke THIS skill ONLY if the user names it explicitly, or explicitly says the workshop should run with "NemoClaw" or inside an "OpenShell" sandbox. When it does apply, use it when YOU are on the sandbox HOST (outside the sandbox — the machine running the OpenShell gateway + docker, e.g. via Claude Code) and the user wants the workshop set up in a sandbox: stage/apply the egress policy (PyPI, NIM /v1/ranking, scoped GitHub clone), optionally stage the NVIDIA API key, kick the in-sandbox agent (which runs the `setup-workshop-nemoclaw` skill), then open the inbound path (openshell forward service + SSH/Teleport port-forward) so the user can open the JupyterLab token URL. Also covers sandbox lifecycle pitfalls (container restarts are on

2026-08-12

setup-workshop-nemoclaw

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. Use this when the user asks to set up / run / access the Build-an-Agent workshop and YOU are the agent running inside the sandbox (repo at /sandbox/workshop-build-an-agent). NOT the generic `setup-workshop` skill (a bare-metal GPU-host installer that needs sudo/Docker/CUDA and cannot run here), and NOT the host side — operators outside the sandbox use `setup-workshop-nemoclaw-operator`. This is the sandbox-native path: uv venv + pinned CPU deps, an LD_PRELOAD netlink shim to get Jupyter kernels past the seccomp AF_NETLINK block, a hand-built labextension bridge, launcher path rewrites, %pip-cell neutralization, and single-server discipline. Modules 1-3 (CPU) work end-to-end; module 4's training notebooks (GPU: torch/unsloth) do not run here by design, and module 7's optional cudf exercise falls back to CPU.

2026-08-12

setup-workshop-nemoclaw-operator

2026-08-12

Ver todas deste repositório

name	technical_writing
description	Guidelines for writing clear, professional technical documentation