New to Claude Skills? Learn how to install them →

nvidia on GitHub

NemoClaw Documentation Access

OfficialFree

Streamline your access to NemoClaw documentation with AI agents.

by nvidia2.8k stars on nvidia/skills
Updated Aug 7, 2026
Get this skill

Free · Opens the source repo

What NemoClaw Documentation Access does

The NemoClaw Documentation Access skill facilitates seamless interaction between AI coding agents and the official NemoClaw documentation. By guiding users to the most relevant Markdown resources, this skill ensures that users receive accurate and up-to-date information directly from the source, rather than relying on potentially outdated or incorrect information. This is particularly useful for developers and designers working with NemoClaw who need quick access to installation, configuration, and operational guidance.

This skill operates by connecting to the NemoClaw docs MCP server, allowing agents to search and retrieve specific documentation pages based on user queries. If the MCP server is not available, the skill can fall back on an index file to access the necessary documentation. The structured retrieval process means that users can receive tailored responses based on their specific agent variant—OpenClaw, Hermes, or Deep Agents—ensuring that the guidance is relevant and precise.

The skill is designed for both technical and non-technical users, providing step-by-step instructions for setup and troubleshooting. It emphasizes clarity by summarizing command outputs and avoiding requests for sensitive information, making it a safe choice for users who may be less familiar with command-line operations. This focus on user-friendliness, combined with the ability to fetch detailed documentation, makes it an essential tool for anyone looking to leverage NemoClaw effectively.

In summary, the NemoClaw Documentation Access skill is ideal for developers and designers who require quick, reliable access to the NemoClaw documentation while working with AI agents. By streamlining the process of finding and using documentation, this skill enhances productivity and reduces the time spent searching for information.

When to use it

Use this skill when you need to install, configure, or troubleshoot NemoClaw with an AI coding assistant.

When not to use it

This skill may not be suitable if you are looking for general programming help unrelated to NemoClaw or its specific variants.

What you can build with it

Quick Installation Guidance

A user needs to install NemoClaw and seeks step-by-step instructions tailored to their operating system and agent variant.

Troubleshooting Configuration Issues

When encountering issues during setup, a user can ask for specific troubleshooting documentation to resolve their problems.

Accessing Latest Documentation

A developer wants to ensure they are using the most current NemoClaw guidelines and can quickly retrieve the latest Markdown documentation.

How to install NemoClaw Documentation Access

View source

1. Install with the skills CLI

npx skills add nvidia/skills/nemoclaw-user-guide --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by nvidia

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.

Frequently asked questions about NemoClaw Documentation Access

Similar skills