docs: fix stale links and skill listing

docs/about/how-it-works.mdx

@@ -132,13 +132,13 @@ NemoClaw's runtime context tells supported agents to try allowed network and fil
 - Refer to the [Architecture](../reference/architecture) for the full technical structure, including file layouts and the blueprint lifecycle.
 - Refer to [Inference Options](../inference/inference-options) for detailed provider configuration.
 - For details on the baseline rules, refer to [Network Policies](../reference/network-policies).
-- For container-level hardening, refer to [Sandbox Hardening](../manage-sandboxes/sandbox-hardening).
+- For container-level hardening, refer to [Sandbox Hardening](../deployment/sandbox-hardening).
 
 </AgentOnly>
 <AgentOnly variant="hermes">
 
 - Read [Ecosystem](ecosystem) for stack-level relationships and NemoClaw versus OpenShell-only paths.
-- Follow [Quickstart with Hermes](../get-started/quickstart) to launch your first sandbox.
+- Follow [Quickstart with Hermes](../get-started/quickstart-hermes) to launch your first sandbox.
 - Refer to the [Architecture](../reference/architecture) for the full technical structure, including file layouts and the blueprint lifecycle.
 - Refer to [Inference Options](../inference/inference-options) for detailed provider configuration.
 - For details on the baseline rules, refer to [Network Policies](../reference/network-policies).

docs/about/release-notes.mdx

@@ -129,9 +129,9 @@ NemoClaw v0.0.55 improves local Ollama onboarding reliability, plugin secret-sca
 NemoClaw v0.0.54 updates messaging activation, Windows WSL onboarding, NemoHermes dashboard access, and sandbox repair paths:
 
 - Generated OpenClaw config now marks Telegram, Discord, Slack, and WhatsApp as enabled at the channel level. Selected messaging plugins are pinned during the image build, and `channels add` verifies Telegram, Discord, and Slack bridge startup after the rebuild instead of leaving silent channel failures for later debugging. For more information, refer to [Messaging Channels](../manage-sandboxes/messaging-channels).
-- The Windows bootstrap flow waits for Ubuntu account creation before touching Docker settings, enables Docker Desktop WSL integration for the target distro, avoids changing the global WSL default distro, and adds WSL-specific Docker reachability hints during onboarding. For more information, refer to [Prepare Windows for NemoClaw](../get-started/prerequisites/windows-preparation).
+- The Windows bootstrap flow waits for Ubuntu account creation before touching Docker settings, enables Docker Desktop WSL integration for the target distro, avoids changing the global WSL default distro, and adds WSL-specific Docker reachability hints during onboarding. For more information, refer to [Prepare Windows for NemoClaw](../get-started/windows-preparation).
 - Windows-host Ollama setup inside WSL now requires the Docker Desktop WSL integration path. NemoClaw still shows Windows-host Ollama options when it detects them, but labels the Docker Desktop requirement and blocks unsupported native Docker-in-WSL selections before it tries to start or install Ollama. For more information, refer to [Use a Local Inference Server](../inference/use-local-inference).
-- NemoHermes can expose the optional native Hermes web dashboard separately from the OpenAI-compatible API. Set `NEMOCLAW_HERMES_DASHBOARD=1` before onboarding to start and forward the dashboard on port `9119`, with `NEMOCLAW_HERMES_DASHBOARD_PORT` and `NEMOCLAW_HERMES_DASHBOARD_TUI` available for port and TUI tab control. For more information, refer to [NemoClaw Quickstart with Hermes](../../hermes/get-started/quickstart).
+- NemoHermes can expose the optional native Hermes web dashboard separately from the OpenAI-compatible API. Set `NEMOCLAW_HERMES_DASHBOARD=1` before onboarding to start and forward the dashboard on port `9119`, with `NEMOCLAW_HERMES_DASHBOARD_PORT` and `NEMOCLAW_HERMES_DASHBOARD_TUI` available for port and TUI tab control. For more information, refer to [NemoClaw Quickstart with Hermes](../get-started/quickstart-hermes).
 - Onboarding diagnostics include more copy-paste-ready recovery hints. Invalid sandbox names now include a `Try: <suggested-slug>` line when NemoClaw can derive a valid name, and non-interactive NVIDIA Endpoints setup prints the exact `export NVIDIA_INFERENCE_API_KEY=nvapi-...` shape when the key is missing. For more information, refer to [NemoClaw CLI Commands Reference](../reference/commands).
 - Homebrew stays on the Linuxbrew prefix while exposing installed formula commands in sandbox shell sessions, the `/nemoclaw` slash command activates at OpenClaw startup again, Hermes rebuilds tolerate older release tarballs that lack optional UI package lockfiles, and device scope-upgrade approvals recover without being pinned to the old gateway-scoped request. For more information, refer to [Common NemoClaw Integration Policy Examples](../network-policy/integration-policy-examples).
 - The host-gateway allowance for OpenClaw `web_fetch` is confined to the trusted proxy path, while strict and direct paths continue to block host-gateway names. Hermes Provider onboarding skips the host-side smoke probe only for OAuth-backed setup and keeps direct validation for Nous API key setup. For more information, refer to [NemoClaw Inference Options](../inference/inference-options).

docs/inference/set-up-sub-agent.mdx

@@ -51,6 +51,10 @@ The primary orchestration model remains responsible for conversation, planning,
 
 ## Update the Sandbox Config
 
+Before running these commands, install NemoClaw and onboard a sandbox such as `my-assistant`.
+The sandbox must be running on the host where you run Docker commands, and its agent container must be discoverable through the OpenShell sandbox label.
+If you have not created a sandbox yet, follow the [Quickstart with OpenClaw](../get-started/quickstart) first.
+
 Fetch the current OpenClaw config from the sandbox, patch it with your auxiliary provider and `agents.list` changes, then upload it back.
 On Docker-driver sandboxes, run these commands from the host that owns the sandbox containers.
 The container name includes a runtime suffix, so discover it from the OpenShell sandbox label:

docs/reference/commands-nemohermes.mdx

@@ -563,7 +563,7 @@ Expected output:
 
 ```text
 ...
-    Agent:    Hermes v2026.5.16
+    Agent:    Hermes vX.Y.Z
 ...
 ```
 

docs/reference/commands.mdx

@@ -664,7 +664,7 @@ Expected output:
 
 ```text
 ...
-    Agent:    OpenClaw v2026.5.27
+    Agent:    OpenClaw vX.Y.Z
 ...
 ```
 
@@ -690,7 +690,7 @@ Expected output:
 
 ```text
 ...
-    Agent:    Hermes v2026.5.16
+    Agent:    Hermes vX.Y.Z
 ...
 ```
 
@@ -1169,7 +1169,7 @@ Skill names must contain only alphanumeric characters, dots, hyphens, and unders
 
 <AgentOnly variant="openclaw">
 
-OpenClaw plugins are a different kind of extension. To install an OpenClaw plugin, see [Install OpenClaw Plugins](../manage-sandboxes/install-openclaw-plugins).
+OpenClaw plugins are a different kind of extension. To install an OpenClaw plugin, see [Install OpenClaw Plugins](../deployment/install-openclaw-plugins).
 For OpenClaw, the command uploads the skill to the OpenClaw state directory and mirrors it into `$HOME/.openclaw/skills/<name>` when the agent home directory differs from the state directory.
 That mirror makes skills listed by `openclaw skills list` available at session startup.
 If mirror creation fails, NemoClaw prints a warning so you can reinstall or inspect the home directory permissions.

docs/reference/troubleshooting.mdx

@@ -1424,7 +1424,7 @@ If you run other services on Spark that expect port 3000, bind them to a differe
 <a id="windows-wsl-2"></a>
 ## Windows Subsystem for Linux
 
-For environment setup steps, see [Windows Prerequisites](../get-started/prerequisites/windows-preparation).
+For environment setup steps, see [Windows Prerequisites](../get-started/windows-preparation).
 
 ### `wsl --install --no-distribution` returns Forbidden (403)
 
@@ -1500,7 +1500,7 @@ sudo systemctl stop ollama
 OLLAMA_CONTEXT_LENGTH=16384 ollama serve
 ```
 
-For additional troubleshooting, see the [Windows Setup](../get-started/prerequisites/windows-preparation) page.
+For additional troubleshooting, see the [Windows Setup](../get-started/windows-preparation) page.
 <AgentOnly variant="openclaw">
 For first-time OpenClaw setup, see the [Quickstart](../get-started/quickstart).
 </AgentOnly>
@@ -1602,7 +1602,7 @@ After the rebuild completes, return to the Skills page to confirm the skill is r
 ## Hermes
 
 The issues below are common problems you may encounter when running Hermes through `nemohermes`.
-For setup, refer to [Quickstart with Hermes](../../hermes/get-started/quickstart).
+For setup, refer to [Quickstart with Hermes](../get-started/quickstart-hermes).
 
 ### Port 8642 in a browser shows a blank page or `Cannot GET /`
 
@@ -1718,7 +1718,7 @@ Reset a specific provider's credentials with `nemohermes credentials reset <prov
 
 ### `Brave Search` policy preset has no effect under Hermes
 
-The Hermes wizard intentionally omits the Brave Search preset because Hermes does not use NemoClaw's OpenClaw web-search configuration (see [Quickstart with Hermes](../../hermes/get-started/quickstart) and [Network Policies](network-policies)).
+The Hermes wizard intentionally omits the Brave Search preset because Hermes does not use NemoClaw's OpenClaw web-search configuration (see [Quickstart with Hermes](../get-started/quickstart-hermes) and [Network Policies](network-policies)).
 If you add the `brave` preset to a Hermes sandbox after onboarding, the L7 egress allowlist opens for Brave's endpoints but the agent itself does not start consuming the credential.
 Configure Hermes web search from the agent's own configuration inside the sandbox.
 

docs/resources/agent-skills.mdx

@@ -59,6 +59,7 @@ The following user skills ship with NemoClaw.
 | `nemoclaw-user-configure-security` | Review the risk framework for every configurable security control, understand credential storage, and assess posture trade-offs. |
 | `nemoclaw-user-manage-sandboxes` | Manage day-two sandbox operations, including status, logs, diagnostics, rebuilds, upgrades, messaging channels, workspace files, backup, and restore. |
 | `nemoclaw-user-reference` | CLI command reference, plugin and blueprint architecture, baseline network policies, and troubleshooting guide. |
+| `nemoclaw-user-agent-skills` | How to clone, update, and use NemoClaw agent skills, including this page and the skills directory layout. |
 
 ## Example Questions and Triggered Skills
 
@@ -77,6 +78,7 @@ Examples of questions your assistant can answer with these skills:
 | "What security controls can I configure?" | `nemoclaw-user-configure-security` |
 | "Back up my agent workspace files." | `nemoclaw-user-manage-sandboxes` |
 | "What CLI commands are available?" | `nemoclaw-user-reference` |
+| "What NemoClaw skills are available for my coding assistant?" | `nemoclaw-user-agent-skills` |
 
 You can also reference a skill directly by name if you know which one you need.