AGENT SKILL

nemoclaw-user-guide

Guides human users' AI agents to the NemoClaw docs MCP server and canonical Fern documentation in Markdown form. Use when users ask how to install, configure, operate, troubleshoot, secure, or learn NemoClaw with an AI coding assistant. Trigger keywords - nemoclaw docs, use nemoclaw with ai agent, nemoclaw mcp docs, nemoclaw install help, nemoclaw quickstart, nemoclaw markdown docs, llms.txt, agent skills.

License 许可
Apache-2.0
最近更新
2026-10-08
Stars
★ 0
Forks
0

01 前言 Front Matter

name
nemoclaw-user-guide
license
Apache-2.0
description
Guides human users' AI agents to the NemoClaw docs MCP server and canonical Fern documentation in Markdown form. Use when users ask how to install, configure, operate, troubleshoot, secure, or learn NemoClaw with an AI coding assistant. Trigger keywords - nemoclaw docs, use nemoclaw with ai agent, nemoclaw mcp docs, nemoclaw install help, nemoclaw quickstart, nemoclaw markdown docs, llms.txt, agent skills.

02 资源文件 4

03 SKILL.md 正文

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, either OpenClaw or Hermes, and 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.

How to Help the User

  • Ask which agent variant they want to use before giving setup instructions: OpenClaw or Hermes.
  • 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.
  • Keep instructions specific to the user's operating system, selected agent, and inference provider.
  • Explain assumptions when the docs do not cover the exact environment.
  • Recommend the next verification command after each setup or recovery step.

04 同仓库更多 Skills

Solizardking
Solizardking/train2earn

testing

For testing with Light Protocol programs and clients on localnet, devnet, and mainnet validation.

★ 0
Solizardking
Solizardking/train2earn

qedgen

Formally verify programs by writing Lean 4 proofs. Trigger this skill whenever the user wants to formally verify code, generate Lean 4 proofs, prove properties about algorithms or smart contracts, verify invariants, convert program logic into formal specifications, or anything involving Lean 4 and formal verification. Also trigger when the user mentions "qedgen", "lean proof", "formal proof", "verify my code", "prove correctness", "formal verification", or wants mathematical guarantees about their implementation.

★ 0
Solizardking
Solizardking/train2earn

solana-dev

Use when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "deploy to devnet", or "explain Solana concepts" (rent, accounts, PDAs, CPIs, etc.). Also use for quick on-chain lookups via public RPC + curl — "what's the balance of <wallet>", "look up transaction <sig>", "token balance for <account>", "check this address on mainnet/devnet". End-to-end Solana development playbook covering wallet connection, Anchor/Pinocchio programs, Codama client generation, LiteSVM/Mollusk/Surfpool testing, security checklists, and JSON-RPC curl lookups against public clusters. Integrates with the Solana MCP server for live documentation search. Prefers framework-kit (@solana/client + @solana/react-hooks) for UI, wallet-standard-first connection (incl. ConnectorKit), @solana/kit for client/RPC code, and @solana/web3-compat for legacy boundaries.

★ 0
Solizardking
Solizardking/train2earn

solana-common-errors

Diagnose and fix common Solana development errors — GLIBC mismatches, Anchor version conflicts, cargo build-sbf / platform-tools failures, LiteSVM issues, edition2024 crate pins, RPC airdrops, and Anchor 0.29→0.32 migrations. Use when builds fail, Anchor CLI won't install, or CI breaks on Debian/Ubuntu.

★ 0
Solizardking
Solizardking/train2earn

skill-creator

Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.

★ 0
Solizardking
Solizardking/train2earn

phantom-wallet-mcp

Execute wallet operations through the Phantom MCP server. Use when the user wants to interact with their Phantom wallet directly — get addresses, transfer SOL or SPL tokens, buy/swap tokens, sign transactions, and sign messages across Solana, Ethereum, Bitcoin, and Sui. Requires the @phantom/mcp-server to be configured as an MCP server.

★ 0