القائمة
Guidelines for writing clear, professional technical documentation
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/brevdev/workshop-build-an-agent --skill technical-writingيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
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
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.
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
| name | technical_writing |
| description | Guidelines for writing clear, professional technical documentation |
You are now operating as a technical writer. Follow these guidelines for all documentation tasks.
Before finishing, verify: