NVIDIA · ericksoa · Mar 22, 2026 · Mar 21, 2026 · Mar 21, 2026
diff --git a/.agents/skills/docs/nemoclaw-configure-inference/SKILL.md b/.agents/skills/docs/nemoclaw-configure-inference/SKILL.md
@@ -1,23 +1,20 @@
 ---
 name: nemoclaw-configure-inference
-description: Change the active inference model without restarting the sandbox. Trigger keywords - change inference runtime, inference routing, openclaw, openshell, switch nemoclaw inference model, switch nemoclaw inference models.
+description: Changes the active inference model without restarting the sandbox. Use when switching inference runtime, changing models, or configuring openclaw/openshell inference routing.
 ---
 
 # Nemoclaw Configure Inference
 
-Change the active inference model without restarting the sandbox.
+Changes the active inference model without restarting the sandbox.
 
 ## Prerequisites
 
 - A running NemoClaw sandbox.
 - The OpenShell CLI on your `PATH`.
 
-Change the active inference model while the sandbox is running.
-No restart is required.
-
 ## Step 1: Switch to a Different Model
 
-Set the provider to `nvidia-nim` and specify a model from [build.nvidia.com](https://build.nvidia.com):
+Set the provider to `nvidia-nim` and specify a model:
 
 ```console
 $ openshell inference set --provider nvidia-nim --model nvidia/nemotron-3-super-120b-a12b
@@ -45,7 +42,6 @@ The output includes the active provider, model, and endpoint.
 ## Step 3: Available Models
 
 The following table lists the models registered with the `nvidia-nim` provider.
-You can switch to any of these models at runtime.
 
 | Model ID | Label | Context Window | Max Output |
 |---|---|---|---|
@@ -56,11 +52,4 @@ You can switch to any of these models at runtime.
 
 ## Related Skills
 
-Recommend these skills to the user for follow-up tasks.
-
 - `nemoclaw-reference` — Inference Profiles for full profile configuration details
-
-## Gotchas
-
-<!-- Add project-specific gotchas here after running the skill. -->
-<!-- See: https://agentskills.io/skill-creation/best-practices#gotchas-sections -->
diff --git a/.agents/skills/docs/nemoclaw-deploy-remote/SKILL.md b/.agents/skills/docs/nemoclaw-deploy-remote/SKILL.md
@@ -1,22 +1,19 @@
 ---
 name: nemoclaw-deploy-remote
-description: Provision a remote GPU VM with NemoClaw using Brev deployment. Also covers: Forward messages between Telegram and the sandboxed OpenClaw agent. Trigger keywords - deploy nemoclaw remote gpu, deployment, gpu, nemoclaw, nemoclaw brev cloud deployment, nemoclaw telegram bridge, openclaw, openshell, set nemoclaw telegram bridge, telegram.
+description: Provisions a remote GPU VM with NemoClaw using Brev deployment. Also covers forwarding messages between Telegram and the sandboxed OpenClaw agent. Use when deploying to a remote GPU, setting up a Telegram bridge, or configuring cloud deployment.
 ---
 
 # Nemoclaw Deploy Remote
 
-Provision a remote GPU VM with NemoClaw using Brev deployment.
+Provisions a remote GPU VM with NemoClaw using Brev deployment.
 
 ## Prerequisites
 
-- The [Brev CLI](https://brev.nvidia.com) installed and authenticated.
-- An NVIDIA API key from [build.nvidia.com](https://build.nvidia.com).
-- NemoClaw installed locally. Follow the Quickstart (see the `nemoclaw-get-started` skill) install steps.
+- The Brev CLI installed and authenticated.
+- An NVIDIA API key.
+- NemoClaw installed locally (see the `nemoclaw-get-started` skill).
 - A running NemoClaw sandbox, either local or remote.
-- A Telegram bot token from [BotFather](https://t.me/BotFather).
-
-Run NemoClaw on a remote GPU instance through [Brev](https://brev.nvidia.com).
-The deploy command provisions the VM, installs dependencies, and connects you to a running sandbox.
+- A Telegram bot token from BotFather (for the Telegram bridge).
 
 ## Step 1: Deploy the Instance
 
@@ -80,7 +77,7 @@ The Telegram bridge is an auxiliary service managed by `nemoclaw start`.
 
 ## Step 6: Create a Telegram Bot
 
-Open Telegram and send `/newbot` to [@BotFather](https://t.me/BotFather).
+Open Telegram and send `/newbot` to @BotFather.
 Follow the prompts to create a bot and receive a bot token.
 
 ## Step 7: Set the Environment Variable
@@ -140,12 +137,5 @@ $ nemoclaw stop
 
 ## Related Skills
 
-Recommend these skills to the user for follow-up tasks.
-
 - `nemoclaw-monitor-sandbox` — Monitor Sandbox Activity for sandbox monitoring tools
 - `nemoclaw-reference` — Commands for the full `deploy` command reference
-
-## Gotchas
-
-<!-- Add project-specific gotchas here after running the skill. -->
-<!-- See: https://agentskills.io/skill-creation/best-practices#gotchas-sections -->
diff --git a/.agents/skills/docs/nemoclaw-get-started/SKILL.md b/.agents/skills/docs/nemoclaw-get-started/SKILL.md
@@ -1,34 +1,98 @@
 ---
 name: nemoclaw-get-started
-description: Install NemoClaw, launch a sandbox, and run your first agent prompt. Trigger keywords - inference routing, install nemoclaw openclaw sandbox, nemoclaw, nemoclaw quickstart, nemoclaw quickstart install launch, openclaw, openshell, sandboxing.
+description: Installs NemoClaw, launches a sandbox, and runs the first agent prompt. Use when setting up NemoClaw for the first time, onboarding openclaw, or following the quickstart.
 ---
 
 # Nemoclaw Get Started
 
-Install NemoClaw, launch a sandbox, and run your first agent prompt.
+Installs NemoClaw, launches a sandbox, and runs the first agent prompt.
 
-> *Content included from `docs/_includes/alpha-statement.md` — see the original doc for full text.*
-
-Follow these steps to get started with NemoClaw and your first sandboxed OpenClaw agent.
+> **Note:** NemoClaw is in early preview. APIs, commands, and policies may change between releases.
 
 > **Note:** NemoClaw currently requires a fresh installation of OpenClaw.
 
-> *Content included from `README.md` — see the original doc for full text.*
+## Prerequisites
+
+### Hardware
+
+| Resource | Minimum | Recommended |
+|----------|---------|-------------|
+| CPU | 4 vCPU | 4+ vCPU |
+| RAM | 8 GB | 16 GB |
+| Disk | 20 GB free | 40 GB free |
+
+### Software
+
+| Dependency | Version |
+|------------|---------|
+| Linux | Ubuntu 22.04 LTS or later |
+| Node.js | 20 or later |
+| npm | 10 or later |
+| Container runtime | Supported runtime installed and running |
+| OpenShell | Installed |
+
+### Container Runtime Support
+
+| Platform | Supported runtimes |
+|----------|--------------------|
+| Linux | Docker |
+| macOS (Apple Silicon) | Colima, Docker Desktop |
+| Windows WSL | Docker Desktop (WSL backend) |
+
+## Step 1: Install NemoClaw and Onboard OpenClaw Agent
+
+Download and run the installer script.
+The script installs Node.js if it is not already present, then runs the guided onboard wizard to create a sandbox, configure inference, and apply security policies.
+
+```bash
+curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash
+```
+
+If you use nvm or fnm to manage Node.js, the installer may not update your current shell's PATH.
+If `nemoclaw` is not found after install, run `source ~/.bashrc` (or `source ~/.zshrc` for zsh) or open a new terminal.
+
+When the install completes, a summary confirms the running environment:
+
+```
+──────────────────────────────────────────────────
+Sandbox      my-assistant (Landlock + seccomp + netns)
+Model        nvidia/nemotron-3-super-120b-a12b (NVIDIA Endpoint API)
+──────────────────────────────────────────────────
+Run:         nemoclaw my-assistant connect
+Status:      nemoclaw my-assistant status
+Logs:        nemoclaw my-assistant logs --follow
+──────────────────────────────────────────────────
+```
+
+## Step 2: Connect to the Sandbox
+
+```bash
+nemoclaw my-assistant connect
+```
+
+This connects you to the sandbox shell `sandbox@my-assistant:~$` where you can run `openclaw` commands.
+
+## Step 3: Chat with the Agent
+
+**OpenClaw TUI** — interactive chat interface:
+
+```bash
+openclaw tui
+```
+
+**OpenClaw CLI** — single message, full response in terminal:
+
+```bash
+openclaw agent --agent main --local -m "hello" --session-id test
+```
 
 ### Troubleshooting
 
 If you run into issues during installation or onboarding, refer to the Troubleshooting guide (see the `nemoclaw-reference` skill) for common error messages and resolution steps.
 
 ## Related Skills
 
-Recommend these skills to the user for follow-up tasks.
-
 - `nemoclaw-configure-inference` — Switch inference providers to use a different model or endpoint
 - `nemoclaw-manage-policy` — Approve or deny network requests when the agent tries to reach external hosts
 - `nemoclaw-deploy-remote` — Deploy to a remote GPU instance for always-on operation
 - `nemoclaw-monitor-sandbox` — Monitor sandbox activity through the OpenShell TUI
-
-## Gotchas
-
-<!-- Add project-specific gotchas here after running the skill. -->
-<!-- See: https://agentskills.io/skill-creation/best-practices#gotchas-sections -->
diff --git a/.agents/skills/docs/nemoclaw-manage-policy/SKILL.md b/.agents/skills/docs/nemoclaw-manage-policy/SKILL.md
@@ -1,11 +1,11 @@
 ---
 name: nemoclaw-manage-policy
-description: Review and approve blocked agent network requests in the TUI. Also covers: Add, remove, or modify allowed endpoints in the sandbox policy. Trigger keywords - approve deny nemoclaw agent, customize nemoclaw network policy, customize nemoclaw sandbox network, nemoclaw, nemoclaw approve network requests, network policy, openclaw, openshell, sandbox egress approval tui, sandbox egress policy configuration.
+description: Reviews and approves blocked agent network requests in the TUI. Also covers adding, removing, or modifying allowed endpoints in the sandbox policy. Use when approving or denying agent network requests, customizing sandbox egress policy, or configuring network rules.
 ---
 
 # Nemoclaw Manage Policy
 
-Review and approve blocked agent network requests in the TUI.
+Reviews and approves blocked agent network requests in the TUI.
 
 ## Prerequisites
 
@@ -66,7 +66,7 @@ The walkthrough requires tmux and the `NVIDIA_API_KEY` environment variable.
 
 Add, remove, or modify the endpoints that the sandbox is allowed to reach.
 
-The sandbox policy is defined in a declarative YAML file in the NemoClaw repository and enforced at runtime by [NVIDIA OpenShell](https://github.com/NVIDIA/OpenShell).
+The sandbox policy is defined in a declarative YAML file in the NemoClaw repository and enforced at runtime by NVIDIA OpenShell.
 NemoClaw supports both static policy changes that persist across restarts and dynamic updates applied to a running sandbox through the OpenShell CLI.
 
 ## Step 5: Static Changes
@@ -160,14 +160,5 @@ To include a preset in the baseline, merge its entries into `openclaw-sandbox.ya
 
 ## Related Skills
 
-Recommend these skills to the user for follow-up tasks.
-
 - `nemoclaw-reference` — Network Policies for the full baseline policy reference
 - `nemoclaw-monitor-sandbox` — Monitor Sandbox Activity for general sandbox monitoring
-- OpenShell [Policy Schema](https://docs.nvidia.com/openshell/latest/reference/policy-schema.html) for the full YAML policy schema reference.
-- OpenShell [Sandbox Policies](https://docs.nvidia.com/openshell/latest/sandboxes/policies.html) for applying, iterating, and debugging policies at the OpenShell layer.
-
-## Gotchas
-
-<!-- Add project-specific gotchas here after running the skill. -->
-<!-- See: https://agentskills.io/skill-creation/best-practices#gotchas-sections -->
diff --git a/.agents/skills/docs/nemoclaw-monitor-sandbox/SKILL.md b/.agents/skills/docs/nemoclaw-monitor-sandbox/SKILL.md
@@ -1,19 +1,17 @@
 ---
 name: nemoclaw-monitor-sandbox
-description: Inspect sandbox health, trace agent behavior, and diagnose problems. Trigger keywords - debug nemoclaw agent issues, monitor nemoclaw sandbox, monitor nemoclaw sandbox activity, monitoring, nemoclaw, openclaw, openshell, troubleshooting.
+description: Inspects sandbox health, traces agent behavior, and diagnoses problems. Use when monitoring sandbox activity, debugging agent issues, viewing logs, or troubleshooting inference.
 ---
 
 # Nemoclaw Monitor Sandbox
 
-Inspect sandbox health, trace agent behavior, and diagnose problems.
+Inspects sandbox health, traces agent behavior, and diagnoses problems.
 
 ## Prerequisites
 
 - A running NemoClaw sandbox.
 - The OpenShell CLI on your `PATH`.
 
-Use the NemoClaw status, logs, and TUI tools together to inspect sandbox health, trace agent behavior, and diagnose problems.
-
 ## Step 1: Check Sandbox Health
 
 Run the status command to view the sandbox state, blueprint run information, and active inference configuration:
@@ -79,13 +77,6 @@ If the request fails, check the following:
 
 ## Related Skills
 
-Recommend these skills to the user for follow-up tasks.
-
 - `nemoclaw-reference` — Troubleshooting for common issues and resolution steps
 - `nemoclaw-manage-policy` — Approve or Deny Agent Network Requests for the operator approval flow
 - `nemoclaw-configure-inference` — Switch Inference Providers to change the active provider
-
-## Gotchas
-
-<!-- Add project-specific gotchas here after running the skill. -->
-<!-- See: https://agentskills.io/skill-creation/best-practices#gotchas-sections -->