mcpField
N
nemoclaw-user-guide

nemoclaw-user-guide

github.com/nvidiaAgent workflows3.8k1.2k installsUpdated today
Repository

About nemoclaw-user-guide

nemoclaw-user-guide is an Agent skill that guides AI assistants through current NemoClaw documentation for setup, troubleshooting, and operations. It prioritizes the docs MCP server and Markdown sources, and distinguishes OpenClaw, Hermes, and Deep Agents instructions.

Key features

  1. 01Canonical docs retrieval workflow
  2. 02Read-only documentation search via MCP
  3. 03Variant-specific setup guidance
  4. 04Task-based documentation routing
  5. 05Credential and safety guidance

Use cases

  1. 01Finding setup steps for an agent variant
  2. 02Troubleshooting inference or network policies
  3. 03Looking up sandbox management commands

MCP support

It directs MCP-capable assistants to configure the NemoClaw documentation server at `https://docs.nvidia.com/nemoclaw/_mcp/server` and search with its read-only `searchDocs` tool.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nvidia/skills --skill nemoclaw-user-guide

After installing, type/nemoclaw-user-guidein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

BENCHMARK.md
skill-card.md
skill.oms.sig
evals/
evals.json

Details

From the project README

NemoClaw Docs for AI Agents

Use the canonical NemoClaw documentation as your source of truth. Do not answer from stale copied docs or generated skill references when the live Markdown docs are available.

Retrieval Order

  1. If the assistant supports MCP, configure the NemoClaw docs MCP server at https://docs.nvidia.com/nemoclaw/_mcp/server.
  2. Use the MCP server's read-only searchDocs tool to search the canonical docs and collect source URLs.
  3. If MCP is not available, fetch the AI documentation index first: https://docs.nvidia.com/nemoclaw/llms.txt.
  4. Fetch the specific .md page listed in the index or returned by docs search for the user's task.
  5. If you only find an HTML documentation URL, replace the .html suffix with .md, or append .md to the route when the URL has no suffix.
  6. Prefer the user's selected agent variant. Do not mix variant-specific instructions unless you explain why.

Configure the MCP Server

For Claude Code, run:

claude mcp add --transport http fern-docs https://docs.nvidia.com/nemoclaw/_mcp/server

For Cursor, add https://docs.nvidia.com/nemoclaw/_mcp/server to the MCP server configuration. For other MCP clients, configure a streamable HTTP MCP server at that URL.

Starting Pages

Use these pages first for common onboarding flows:

  • OpenClaw home: https://docs.nvidia.com/nemoclaw/latest/user-guide/openclaw/home.md.
  • OpenClaw prerequisites: https://docs.nvidia.com/nemoclaw/latest/user-guide/openclaw/get-started/prerequisites.md.
  • OpenClaw quickstart: https://docs.nvidia.com/nemoclaw/latest/user-guide/openclaw/get-started/quickstart.md.
  • Hermes home: https://docs.nvidia.com/nemoclaw/latest/user-guide/hermes/home.md.
  • Hermes prerequisites: https://docs.nvidia.com/nemoclaw/latest/user-guide/hermes/get-started/prerequisites.md.
  • Hermes quickstart: https://docs.nvidia.com/nemoclaw/latest/user-guide/hermes/get-started/quickstart.md.
  • Deep Agents home: https://docs.nvidia.com/nemoclaw/latest/user-guide/deepagents/home.md.
  • Deep Agents prerequisites: https://docs.nvidia.com/nemoclaw/latest/user-guide/deepagents/get-started/prerequisites.md.
  • Deep Agents quickstart: https://docs.nvidia.com/nemoclaw/latest/user-guide/deepagents/get-started/quickstart.md.

How to Help the User

  • Ask which agent variant they want to use before giving setup instructions: OpenClaw, Hermes, or Deep Agents.
  • Ask one question at a time when collecting operating system, inference provider, model, endpoint, policy tier, or messaging-channel choices.
  • Run commands for non-technical users when your environment allows it, after explaining what the command does and getting permission.
  • Summarize important command output instead of asking the user to paste terminal output into chat.
  • Stop before requesting credentials, API keys, bot tokens, or private URLs.
  • Never ask the user to paste secrets into chat.
  • Use redacted placeholders such as <PASTE_YOUR_API_KEY_HERE> in examples.

Common Task Routing

  • Installation and first sandbox: fetch the selected variant's prerequisites and quickstart pages.
  • Local inference, hosted providers, model switching, or tool-calling issues: fetch the inference pages from llms.txt.
  • Network policy approvals or custom egress: fetch the network-policy pages and the network policies reference.
  • Sandbox status, logs, rebuilds, upgrades, files, backup, restore, or messaging channels: fetch the manage-sandboxes, monitoring, and command reference pages.
  • Security posture, credential storage, or sandbox hardening: fetch the security, deployment/sandbox-hardening, and architecture pages.
  • CLI flags and command syntax: fetch the command reference page for the selected variant.
  • Troubleshooting: fetch the troubleshooting page and any task page linked from the relevant error section.

Response Requirements

  • Cite the Markdown documentation pages you used. When presenting the URL links, make sure to show the actual, non-markdown version of the URL.
  • Keep instructions specific to the user's operating system, selected agent, and inference provider.
  • Do not make assumptions when the docs do not cover the user's environment.
  • Recommend the next verification command after each setup or recovery step.

Comments

Markdown supported