[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ED5B0X7ZPY4PM96ASFM1KV":3,"skill-same:01M7ED5B0X7ZPY4PM96ASFM1KV":88},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7ED5B0X7ZPY4PM96ASFM1KV","nemoclaw-user-get-started",null,"Installs NemoClaw, launches a sandbox, and runs the first agent prompt. Use when onboarding, installing, or launching a NemoClaw sandbox for the first time. Trigger keywords - nemoclaw quickstart, install nemoclaw openclaw sandbox, nemohermes quickstart, hermes agent nemoclaw, run hermes openshell sandbox, nemoclaw prerequisites, nemoclaw supported platforms, nemoclaw hardware software, nemoclaw windows wsl2 setup, nemoclaw install windows docker desktop.","kael-odin\u002Fcodex-plugins-zh","kael-odin","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F166499071?v=4","01M7EBHJT87XN88WT3PEQ8ZGZK","Kael Odin","01M7EBHJVC91GD7PGJN3ZB14SG",37,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnvidia\u002Fskills\u002Fnemoclaw-user-get-started\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"nemoclaw-user-get-started\"\ndescription: \"Installs NemoClaw, launches a sandbox, and runs the first agent prompt. Use when onboarding, installing, or launching a NemoClaw sandbox for the first time. Trigger keywords - nemoclaw quickstart, install nemoclaw openclaw sandbox, nemohermes quickstart, hermes agent nemoclaw, run hermes openshell sandbox, nemoclaw prerequisites, nemoclaw supported platforms, nemoclaw hardware software, nemoclaw windows wsl2 setup, nemoclaw install windows docker desktop.\"\nlicense: \"Apache-2.0\"\n---\n# NemoClaw Quickstart with OpenClaw\n\nFollow these steps to get started with NemoClaw and your first sandboxed OpenClaw agent.\n\n**Note:**\n\nMake sure you have completed reviewing the [Prerequisites](references\u002Fprerequisites.md) before following this guide.\n\n## Install NemoClaw and Onboard OpenClaw Agent\n\nDownload and run the installer script.\nThe script installs Node.js if it is not already present, then runs the guided onboard wizard to create a sandbox, configure inference, and apply security policies.\n\n**Note:**\n\nNemoClaw creates a fresh OpenClaw instance inside the sandbox during the onboarding process.\n\n```bash\ncurl -fsSL https:\u002F\u002Fwww.nvidia.com\u002Fnemoclaw.sh | bash\n```\n\nThe piped installer prompts through your terminal. In headless scripts or CI,\npass explicit acceptance to the `bash` side of the pipe:\n\n```console\n$ curl -fsSL https:\u002F\u002Fwww.nvidia.com\u002Fnemoclaw.sh | NEMOCLAW_NON_INTERACTIVE=1 NEMOCLAW_ACCEPT_THIRD_PARTY_SOFTWARE=1 bash\n```\n\nIf you use nvm or fnm to manage Node.js, the installer might not update your current shell's PATH.\nIf `nemoclaw` is not found after install, run `source ~\u002F.bashrc` (or `source ~\u002F.zshrc` for zsh) or open a new terminal.\n\nOn Linux, the installer checks Docker before it installs NemoClaw.\nIf Docker is missing, the installer downloads the official Docker convenience script, asks for `sudo`, installs Docker, and starts the Docker service when systemd is available.\nIf Docker is installed but your current shell cannot use the Docker socket yet, the installer adds your user to the `docker` group when needed and exits with a recovery command.\n\nOn macOS, the installer uses the Docker-driver OpenShell gateway path with Docker Desktop or Colima.\n\n```console\n$ newgrp docker\n$ curl -fsSL https:\u002F\u002Fwww.nvidia.com\u002Fnemoclaw.sh | bash\n```\n\nOn DGX Spark, DGX Station, and Windows WSL, an interactive installer offers express install after you accept the third-party software notice.\nExpress install switches onboarding to non-interactive mode, allows `sudo` password prompts for required host changes, and selects the managed local inference path for that platform.\nUnless `NEMOCLAW_POLICY_TIER` is set, it applies sandbox policy in `suggested` mode with the `balanced` tier by default, using the base sandbox policy plus supported package, model, web-search, and local-inference presets.\nOn WSL, express install selects the Windows-host Ollama setup path.\nSet `NEMOCLAW_NO_EXPRESS=1` to skip the express prompt, or set `NEMOCLAW_PROVIDER` before launching the installer when you want to choose a provider yourself.\n\nThe installer auto-launches `nemoclaw onboard` when it can locate the freshly-installed binary.\nIf it cannot locate the binary, or if blocking host preflight checks fail, it does not launch the wizard automatically.\nIn that case, the installer prints the relevant diagnostics and a `To finish setup, run:` block with the explicit `nemoclaw onboard` command.\n\n**Note:**\n\nThe onboard flow builds the sandbox image with `NEMOCLAW_DISABLE_DEVICE_AUTH=1` so the dashboard is immediately usable during setup.\nThis is a build-time setting baked into the sandbox image, not a runtime knob.\nIf you export `NEMOCLAW_DISABLE_DEVICE_AUTH` after onboarding finishes, it has no effect on an existing sandbox.\n\n### Review the Configuration Before the Sandbox Build\n\nAfter you enter the sandbox name, the wizard prints a review summary and asks for final confirmation before registering the provider, prompting for optional integrations, and building the sandbox image.\nFor example, if you picked an OpenAI-compatible endpoint, the summary looks like the following:\n\n```text\n  ──────────────────────────────────────────────────\n  Review configuration\n  ──────────────────────────────────────────────────\n  Provider:      compatible-endpoint\n  Model:         openai\u002Fopenai\u002Fgpt-5.5\n  API key:       COMPATIBLE_API_KEY (staged for OpenShell gateway registration)\n  Web search:    disabled\n  Messaging:     none\n  Sandbox name:  my-gpt-claw\n  Note:          Sandbox build typically takes 5–15 minutes on this host.\n  ──────────────────────────────────────────────────\n  Web search and messaging channels will be prompted next.\n  Apply this configuration? [Y\u002Fn]:\n```\n\nThe default is `Y`, so you can press Enter once to continue. Answer `n` to abort cleanly, fix the entries, and re-run `nemoclaw onboard`.\n\nNon-interactive runs (`NEMOCLAW_NON_INTERACTIVE=1`) print the summary for log clarity but skip the prompt.\n\n### Configure Web Search and Messaging\n\nAfter you confirm the summary, NemoClaw registers the selected provider with the OpenShell gateway and sets the `inference.local` route.\nThe wizard then asks whether to enable Brave Web Search.\nIf you enable it, enter a Brave Search API key when prompted.\n\nThe wizard also offers messaging channels such as Telegram, Discord, Slack, WeChat, and WhatsApp.\nPress a channel number to toggle it, then press Enter to continue.\nIf you select a channel, NemoClaw validates the token format before it bakes the channel configuration into the sandbox.\nFor example, Slack bot tokens must start with `xoxb-`.\nWeChat and WhatsApp are experimental.\nReview Messaging Channels (use the `nemoclaw-user-manage-sandboxes` skill) before enabling them.\n\n### Choose Network Policy Presets\n\nAfter the sandbox image builds and OpenClaw starts inside the sandbox, NemoClaw asks which network policy tier to apply.\nThe default **Balanced** tier includes common development presets such as npm, PyPI, Hugging Face, Homebrew, and Brave Search when the selected agent supports web search.\nUse the arrow keys or `j` and `k` to move, Space to select, and Enter to confirm.\n\nThe preset selector lets you include more destinations, such as GitHub, Jira, Slack, Telegram, or local inference.\nPress `r` to toggle a selected preset between read-only and read-write when the preset supports both modes.\n\nWhen the install completes, a summary confirms the running environment.\nBefore printing the summary, NemoClaw verifies that the sandbox gateway and dashboard port forward are reachable.\nInference route and messaging bridge checks are reported as warnings when they need more time or additional configuration.\nThe `Model` and provider line reflects the inference option you picked during onboarding.\nThe example below shows the result if you picked an OpenAI-compatible endpoint during onboarding.\n\n```text\n──────────────────────────────────────────────────\nNemoClaw is ready\n\nSandbox:  my-gpt-claw\nModel:    openai\u002Fopenai\u002Fgpt-5.5 (Other OpenAI-compatible endpoint)\n\nStart chatting\n\n  Browser:\n    http:\u002F\u002F127.0.0.1:18789\u002F\n\n  Terminal:\n    nemoclaw my-gpt-claw connect\n    then run: openclaw tui\n\nAuthenticated dashboard URL, if needed:\n  nemoclaw my-gpt-claw dashboard-url --quiet\n\nManage later\n\n  Status:      nemoclaw my-gpt-claw status\n  Logs:        nemoclaw my-gpt-claw logs --follow\n  Model:       nemoclaw inference set --model \u003Cmodel> --provider \u003Cprovider> --sandbox my-gpt-claw\n  Policies:    nemoclaw my-gpt-claw policy-add\n  Credentials: nemoclaw credentials reset \u003CKEY> && nemoclaw onboard\n──────────────────────────────────────────────────\n\n[INFO]  === Installation complete ===\n```\n\nIf you picked a different option, the `Model` line shows that provider's model and label instead. For example, you might see `gpt-5.4 (OpenAI)`, `claude-sonnet-4-6 (Anthropic)`, `gemini-2.5-flash (Google Gemini)`, `llama3.1:8b (Local Ollama)`, `nvidia-routed (Model Router)`, or `\u003Cyour-model> (Other OpenAI-compatible endpoint)`.\n\nLoad [references\u002Fquickstart-details.md](references\u002Fquickstart-details.md) for detailed steps on Respond to the Onboard Wizard.\n\n## Run Your First Agent Prompt\n\nYou can chat with the agent from the terminal or the browser.\n\n### Open the OpenClaw UI in a Browser to Chat with the Agent\n\nThe onboard wizard starts a background port forward to the sandbox dashboard, then prints the dashboard URL in the install summary.\nThe default host port is `18789`.\nIf that port is already taken, NemoClaw uses the next free dashboard port, such as `18790`, and prints that port in the final URL.\nIf the chosen port becomes occupied after the sandbox build starts, onboarding rolls back the newly-created sandbox and asks you to retry instead of printing an unreachable dashboard URL.\nThe install transcript does not print the gateway token.\nIf the browser requires authentication, use the `dashboard-url --quiet` command to print a complete URL explicitly.\n\n```text\nnemoclaw my-gpt-claw dashboard-url --quiet\n```\n\nOpen the dashboard URL in your browser.\nIf the browser asks for authentication, run `nemoclaw my-gpt-claw dashboard-url --quiet` and open the returned URL.\nTreat the authenticated URL like a password.\n\n### Chat with the Agent from the Terminal\n\nConnect to the sandbox and use the OpenClaw CLI.\n\n```bash\nnemoclaw my-assistant connect\n# inside the sandbox:\nopenclaw tui\n```\n\n## References\n\n- **Load [references\u002Fquickstart-hermes.md](references\u002Fquickstart-hermes.md)** when users ask for Hermes setup, NemoHermes onboarding, or running Hermes inside OpenShell. Installs NemoClaw, selects the Hermes agent, and launches a sandboxed Hermes API endpoint.\n- **Load [references\u002Fprerequisites.md](references\u002Fprerequisites.md)** when verifying prerequisites before installation. Lists the hardware, software, and container runtime requirements for running NemoClaw.\n- **Load [references\u002Fwindows-preparation.md](references\u002Fwindows-preparation.md)** when preparing a Windows machine for NemoClaw, enabling WSL 2, configuring Docker Desktop for Windows, or troubleshooting a Windows-specific install error. Covers Windows-only preparation steps required before the Quickstart.\n- **Load [references\u002Fquickstart-details.md](references\u002Fquickstart-details.md)** when you need detailed steps for Respond to the Onboard Wizard.\n\n## Related Skills\n\n- `nemoclaw-user-overview` — NemoClaw Overview (use the `nemoclaw-user-overview` skill) to learn what NemoClaw is and its capabilities\n","# NemoClaw Quickstart with OpenClaw\n\nFollow these steps to get started with NemoClaw and your first sandboxed OpenClaw agent.\n\n**Note:**\n\nMake sure you have completed reviewing the [Prerequisites](references\u002Fprerequisites.md) before following this guide.\n\n## Install NemoClaw and Onboard OpenClaw Agent\n\nDownload and run the installer script.\nThe script installs Node.js if it is not already present, then runs the guided onboard wizard to create a sandbox, configure inference, and apply security policies.\n\n**Note:**\n\nNemoClaw creates a fresh OpenClaw instance inside the sandbox during the onboarding process.\n\n```bash\ncurl -fsSL https:\u002F\u002Fwww.nvidia.com\u002Fnemoclaw.sh | bash\n```\n\nThe piped installer prompts through your terminal. In headless scripts or CI,\npass explicit acceptance to the `bash` side of the pipe:\n\n```console\n$ curl -fsSL https:\u002F\u002Fwww.nvidia.com\u002Fnemoclaw.sh | NEMOCLAW_NON_INTERACTIVE=1 NEMOCLAW_ACCEPT_THIRD_PARTY_SOFTWARE=1 bash\n```\n\nIf you use nvm or fnm to manage Node.js, the installer might not update your current shell's PATH.\nIf `nemoclaw` is not found after install, run `source ~\u002F.bashrc` (or `source ~\u002F.zshrc` for zsh) or open a new terminal.\n\nOn Linux, the installer checks Docker before it installs NemoClaw.\nIf Docker is missing, the installer downloads the official Docker convenience script, asks for `sudo`, installs Docker, and starts the Docker service when systemd is available.\nIf Docker is installed but your current shell cannot use the Docker socket yet, the installer adds your user to the `docker` group when needed and exits with a recovery command.\n\nOn macOS, the installer uses the Docker-driver OpenShell gateway path with Docker Desktop or Colima.\n\n```console\n$ newgrp docker\n$ curl -fsSL https:\u002F\u002Fwww.nvidia.com\u002Fnemoclaw.sh | bash\n```\n\nOn DGX Spark, DGX Station, and Windows WSL, an interactive installer offers express install after you accept the third-party software notice.\nExpress install switches onboarding to non-interactive mode, allows `sudo` password prompts for required host changes, and selects the managed local inference path for that platform.\nUnless `NEMOCLAW_POLICY_TIER` is set, it applies sandbox policy in `suggested` mode with the `balanced` tier by default, using the base sandbox policy plus supported package, model, web-search, and local-inference presets.\nOn WSL, express install selects the Windows-host Ollama setup path.\nSet `NEMOCLAW_NO_EXPRESS=1` to skip the express prompt, or set `NEMOCLAW_PROVIDER` before launching the installer when you want to choose a provider yourself.\n\nThe installer auto-launches `nemoclaw onboard` when it can locate the freshly-installed binary.\nIf it cannot locate the binary, or if blocking host preflight checks fail, it does not launch the wizard automatically.\nIn that case, the installer prints the relevant diagnostics and a `To finish setup, run:` block with the explicit `nemoclaw onboard` command.\n\n**Note:**\n\nThe onboard flow builds the sandbox image with `NEMOCLAW_DISABLE_DEVICE_AUTH=1` so the dashboard is immediately usable during setup.\nThis is a build-time setting baked into the sandbox image, not a runtime knob.\nIf you export `NEMOCLAW_DISABLE_DEVICE_AUTH` after onboarding finishes, it has no effect on an existing sandbox.\n\n### Review the Configuration Before the Sandbox Build\n\nAfter you enter the sandbox name, the wizard prints a review summary and asks for final confirmation before registering the provider, prompting for optional integrations, and building the sandbox image.\nFor example, if you picked an OpenAI-compatible endpoint, the summary looks like the following:\n\n```text\n  ──────────────────────────────────────────────────\n  Review configuration\n  ──────────────────────────────────────────────────\n  Provider:      compatible-endpoint\n  Model:         openai\u002Fopenai\u002Fgpt-5.5\n  API key:       COMPATIBLE_API_KEY (staged for OpenShell gateway registration)\n  Web search:    disabled\n  Messaging:     none\n  Sandbox name:  my-gpt-claw\n  Note:          Sandbox build typically takes 5–15 minutes on this host.\n  ──────────────────────────────────────────────────\n  Web search and messaging channels will be prompted next.\n  Apply this configuration? [Y\u002Fn]:\n```\n\nThe default is `Y`, so you can press Enter once to continue. Answer `n` to abort cleanly, fix the entries, and re-run `nemoclaw onboard`.\n\nNon-interactive runs (`NEMOCLAW_NON_INTERACTIVE=1`) print the summary for log clarity but skip the prompt.\n\n### Configure Web Search and Messaging\n\nAfter you confirm the summary, NemoClaw registers the selected provider with the OpenShell gateway and sets the `inference.local` route.\nThe wizard then asks whether to enable Brave Web Search.\nIf you enable it, enter a Brave Search API key when prompted.\n\nThe wizard also offers messaging channels such as Telegram, Discord, Slack, WeChat, and WhatsApp.\nPress a channel number to toggle it, then press Enter to continue.\nIf you select a channel, NemoClaw validates the token format before it bakes the channel configuration into the sandbox.\nFor example, Slack bot tokens must start with `xoxb-`.\nWeChat and WhatsApp are experimental.\nReview Messaging Channels (use the `nemoclaw-user-manage-sandboxes` skill) before enabling them.\n\n### Choose Network Policy Presets\n\nAfter the sandbox image builds and OpenClaw starts inside the sandbox, NemoClaw asks which network policy tier to apply.\nThe default **Balanced** tier includes common development presets such as npm, PyPI, Hugging Face, Homebrew, and Brave Search when the selected agent supports web search.\nUse the arrow keys or `j` and `k` to move, Space to select, and Enter to confirm.\n\nThe preset selector lets you include more destinations, such as GitHub, Jira, Slack, Telegram, or local inference.\nPress `r` to toggle a selected preset between read-only and read-write when the preset supports both modes.\n\nWhen the install completes, a summary confirms the running environment.\nBefore printing the summary, NemoClaw verifies that the sandbox gateway and dashboard port forward are reachable.\nInference route and messaging bridge checks are reported as warnings when they need more time or additional configuration.\nThe `Model` and provider line reflects the inference option you picked during onboarding.\nThe example below shows the result if you picked an OpenAI-compatible endpoint during onboarding.\n\n```text\n──────────────────────────────────────────────────\nNemoClaw is ready\n\nSandbox:  my-gpt-claw\nModel:    openai\u002Fopenai\u002Fgpt-5.5 (Other OpenAI-compatible endpoint)\n\nStart chatting\n\n  Browser:\n    http:\u002F\u002F127.0.0.1:18789\u002F\n\n  Terminal:\n    nemoclaw my-gpt-claw connect\n    then run: openclaw tui\n\nAuthenticated dashboard URL, if needed:\n  nemoclaw my-gpt-claw dashboard-url --quiet\n\nManage later\n\n  Status:      nemoclaw my-gpt-claw status\n  Logs:        nemoclaw my-gpt-claw logs --follow\n  Model:       nemoclaw inference set --model \u003Cmodel> --provider \u003Cprovider> --sandbox my-gpt-claw\n  Policies:    nemoclaw my-gpt-claw policy-add\n  Credentials: nemoclaw credentials reset \u003CKEY> && nemoclaw onboard\n──────────────────────────────────────────────────\n\n[INFO]  === Installation complete ===\n```\n\nIf you picked a different option, the `Model` line shows that provider's model and label instead. For example, you might see `gpt-5.4 (OpenAI)`, `claude-sonnet-4-6 (Anthropic)`, `gemini-2.5-flash (Google Gemini)`, `llama3.1:8b (Local Ollama)`, `nvidia-routed (Model Router)`, or `\u003Cyour-model> (Other OpenAI-compatible endpoint)`.\n\nLoad [references\u002Fquickstart-details.md](references\u002Fquickstart-details.md) for detailed steps on Respond to the Onboard Wizard.\n\n## Run Your First Agent Prompt\n\nYou can chat with the agent from the terminal or the browser.\n\n### Open the OpenClaw UI in a Browser to Chat with the Agent\n\nThe onboard wizard starts a background port forward to the sandbox dashboard, then prints the dashboard URL in the install summary.\nThe default host port is `18789`.\nIf that port is already taken, NemoClaw uses the next free dashboard port, such as `18790`, and prints that port in the final URL.\nIf the chosen port becomes occupied after the sandbox build starts, onboarding rolls back the newly-created sandbox and asks you to retry instead of printing an unreachable dashboard URL.\nThe install transcript does not print the gateway token.\nIf the browser requires authentication, use the `dashboard-url --quiet` command to print a complete URL explicitly.\n\n```text\nnemoclaw my-gpt-claw dashboard-url --quiet\n```\n\nOpen the dashboard URL in your browser.\nIf the browser asks for authentication, run `nemoclaw my-gpt-claw dashboard-url --quiet` and open the returned URL.\nTreat the authenticated URL like a password.\n\n### Chat with the Agent from the Terminal\n\nConnect to the sandbox and use the OpenClaw CLI.\n\n```bash\nnemoclaw my-assistant connect\n# inside the sandbox:\nopenclaw tui\n```\n\n## References\n\n- **Load [references\u002Fquickstart-hermes.md](references\u002Fquickstart-hermes.md)** when users ask for Hermes setup, NemoHermes onboarding, or running Hermes inside OpenShell. Installs NemoClaw, selects the Hermes agent, and launches a sandboxed Hermes API endpoint.\n- **Load [references\u002Fprerequisites.md](references\u002Fprerequisites.md)** when verifying prerequisites before installation. Lists the hardware, software, and container runtime requirements for running NemoClaw.\n- **Load [references\u002Fwindows-preparation.md](references\u002Fwindows-preparation.md)** when preparing a Windows machine for NemoClaw, enabling WSL 2, configuring Docker Desktop for Windows, or troubleshooting a Windows-specific install error. Covers Windows-only preparation steps required before the Quickstart.\n- **Load [references\u002Fquickstart-details.md](references\u002Fquickstart-details.md)** when you need detailed steps for Respond to the Onboard Wizard.\n\n## Related Skills\n\n- `nemoclaw-user-overview` — NemoClaw Overview (use the `nemoclaw-user-overview` skill) to learn what NemoClaw is and its capabilities\n",{"name":5,"license":15,"description":7},"main","e3091d1b371a9dcd9455d333175f948b286fdfcf","plugins\u002Fnvidia\u002Fskills\u002Fnemoclaw-user-get-started",1,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh","https:\u002F\u002Fkael-odin.github.io\u002Fcodex-plugins-zh\u002F","https:\u002F\u002Fgithub.com\u002Fkael-odin","https:\u002F\u002Fkael-odin.github.io\u002Fodin-valhalla\u002F","Full-stack development • Open-source • System engineering\r\nTurning ideas into repositories.","2026-11-08 17:05:36",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add kael-odin\u002Fcodex-plugins-zh --skill nemoclaw-user-get-started",{"tool":40,"command":41},"bunx","bunx skills add kael-odin\u002Fcodex-plugins-zh --skill nemoclaw-user-get-started",{"tool":43,"command":44},"pnpm","pnpm dlx skills add kael-odin\u002Fcodex-plugins-zh --skill nemoclaw-user-get-started","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnvidia\u002Fskills\u002Fnemoclaw-user-get-started\u002FSKILL.md",true,[48,54,58,62,66,70,74,78,82],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",538,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnvidia\u002Fskills\u002Fnemoclaw-user-get-started\u002Fagents\u002Fopenai.yaml",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"BENCHMARK.md",2887,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnvidia\u002Fskills\u002Fnemoclaw-user-get-started\u002FBENCHMARK.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"evals\u002Fevals.json",6855,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnvidia\u002Fskills\u002Fnemoclaw-user-get-started\u002Fevals\u002Fevals.json",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fprerequisites.md",4515,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnvidia\u002Fskills\u002Fnemoclaw-user-get-started\u002Freferences\u002Fprerequisites.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fquickstart-details.md",10015,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnvidia\u002Fskills\u002Fnemoclaw-user-get-started\u002Freferences\u002Fquickstart-details.md",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fquickstart-hermes.md",6748,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnvidia\u002Fskills\u002Fnemoclaw-user-get-started\u002Freferences\u002Fquickstart-hermes.md",{"path":75,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fwindows-preparation.md",6342,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnvidia\u002Fskills\u002Fnemoclaw-user-get-started\u002Freferences\u002Fwindows-preparation.md",{"path":79,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":80,"sourceHtmlUrl":81},"skill-card.md",2492,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnvidia\u002Fskills\u002Fnemoclaw-user-get-started\u002Fskill-card.md",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"skill.oms.sig","OTHER","其他",5581,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnvidia\u002Fskills\u002Fnemoclaw-user-get-started\u002Fskill.oms.sig",[89,97,105,113,120,127],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7EDVCKB89EF755PQMKV1BZA","android-emulator-qa","Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7EDPX7WHN6HQZ0QKWB0BGVZ","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","MIT","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fsupabase\u002Fskills\u002Fsupabase-postgres-best-practices\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7EDHHD98T8ZH09F40Q973G3","sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fsentry\u002Fskills\u002Fsentry\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fsentry\u002Fskills\u002Fsentry\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M7EDH3SGVMS1AFS6Q40B5J48","render-workflows","搭建、开发、测试和部署 Render Workflows。涵盖首次脚手架搭建（通过 CLI 或手动方式）、SDK 安装（Python 或 TypeScript）、任务模式（重试、子任务、扇出）、本地开发、控制台部署和故障排查。适用于用户首次搭建 Render Workflows、构建工作流服务、添加或修改工作流任务、本地测试工作流或部署到 Render 的场景。","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-workflows\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":19},"01M7EDH0CYEKQ4VVARHZAQ43S8","render-web-services","配置 Render web service——端口绑定、TLS、健康检查、自定义域名、自动部署、PR 预览、持久化磁盘及部署生命周期。当用户需要搭建 web service、修复健康检查失败、添加自定义域名、配置零停机部署，或排查端口绑定问题时使用。","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-web-services\u002FSKILL.md",[],[],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":19},"01M7EDGVDYFBG1CKSNMQ2DD336","render-static-sites","在 Render 全球 CDN 上部署并配置静态站点——构建命令、发布路径、SPA 路由、重定向、自定义 header 及 PR 预览。当用户需要部署静态站点、搭建 React\u002FVue\u002FHugo\u002FGatsby 前端、配置 SPA 回退路由、添加重定向规则、自定义响应 header，或在静态站点与 web service 之间为前端做选择时使用。触发词:static site、CDN、SPA、single-page app、React deploy、Vue deploy、Hugo、Gatsby、Docusaurus、Jekyll、staticPublishPath。","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-static-sites\u002FSKILL.md",[],[]]