nemoclaw-user-guide

作成者: nvidia

人間ユーザーのAIエージェントを、NemoClawドキュメントMCPサーバーと正規のFernドキュメント(Markdown形式)へ誘導します。ユーザーがインストール方法や設定方法などを尋ねた際に使用します。

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

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.

nvidiaのその他のスキル

compileiq-debug
nvidia
何かがおかしいときに使用:Search()がハングする、すべての評価がINVALID_SCOREを返す、スコアが改善しない、すべての設定が同じ数値を返す、ptxasエラー…
create-github-pr
nvidia
gh CLIを使用してGitHubのプルリクエストを作成します。ユーザーが新しいPRを作成したい、コードをレビューに提出したい、またはプルリクエストを開きたい場合に使用します。トリガーキーワード -…
nemoclaw-maintainer-cross-issue-sweep
nvidia
他のオープンなIssueをスキャンし、特定のPRが修正する可能性があるものや、誤って壊す可能性があるものを見つけます。隣接修正の機会や矛盾リスクをfile:line…と共に出力します。
fhir-basics
nvidia
エージェントにFHIR R4 APIの動作方法、利用可能なリソース、検索パラメータを使ったクエリ方法、およびすべてのレスポンス形式を正しく解析する方法を教えます…
compileiq-validate-result
nvidia
検索が完了した後、かつスピードアップの申請やACFの発送の前に使用します。dump_results CSVを読み込み、トップK候補(単一目的)を抽出します…
changelog-audit
nvidia
リリース前にWarp CHANGELOG.mdを監査:失われたエントリを復元、ユーザー影響で並べ替え、エントリの文言を洗練、行折り返し、および(リリースブランチモードで)比較をバンプ…
maintain-dynamic-plugins
nvidia
NeMo Relayの動的プラグインローダー、マニフェスト、RustネイティブSDK、gRPCワーカープロトコル、PythonワーカーSDK、ドキュメント、テスト、およびリリースワークフローのカバレッジを維持する
dgx-diagnose
nvidia
一般的なDGX Station GB300の問題(CUDAクラッシュ、誤ったGPUターゲット、vLLM/SGLangコンテナのバグ、MIG状態の問題、NVLink/Fabric Managerエラーなど)を診断します。