composio-community/nemoclaw-composio / .agents/skills/nemoclaw-user-get-started
nemoclaw-user-get-started
FlaggedLists the hardware, software, and container runtime requirements for running NemoClaw. Use when verifying prerequisites before installation. Trigger keywords - nemoclaw prerequisites, nemoclaw supported platforms, nemoclaw hardware software, nemoclaw quickstart, install nemoclaw openclaw sandbox, nemoclaw windows wsl2 setup, nemoclaw install windows docker desktop.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 19.6 KB |
| references/prerequisites.md | markdown | 3.3 KB |
| references/windows-preparation.md | markdown | 3.2 KB |
references/windows-preparation.md
View on GitHub<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
<!-- SPDX-License-Identifier: Apache-2.0 -->
# Prepare Windows for NemoClaw
You can run NemoClaw inside Windows Subsystem for Linux (WSL 2) on Windows.
Complete these steps before following the Quickstart (use the `nemoclaw-user-get-started` skill).
Linux and macOS users do not need this page and can go directly to the Quickstart.
> **Note:** This guide has been tested on x86-64.
## Prerequisites
Verify the following before you begin:
- Windows 10 (build 19041 or later) or Windows 11.
- Hardware requirements are the same as the Quickstart (use the `nemoclaw-user-get-started` skill).
## Enable WSL 2
Open an elevated PowerShell (Run as Administrator):
```console
$ wsl --install --no-distribution
```
This enables both the Windows Subsystem for Linux and Virtual Machine Platform features.
Reboot if prompted.
## Install and Register Ubuntu
After reboot, open an elevated PowerShell again:
```console
$ wsl --install -d Ubuntu
```
Let the distribution launch and complete first-run setup (pick a Unix username and password), then type `exit` to return to PowerShell.
> **Warning:** Do not use the `--no-launch` flag.
> The `--no-launch` flag downloads the package but does not register the distribution with WSL.
> Commands like `wsl -d Ubuntu` fail with "There is no distribution with the supplied name" until the distribution has been launched at least once.
Verify the distribution is registered and running WSL 2:
```console
$ wsl -l -v
```
Expected output:
```text
NAME STATE VERSION
* Ubuntu Running 2
```
## Install Docker Desktop
Install [Docker Desktop](https://www.docker.com/products/docker-desktop/) with the WSL 2 backend (the default on Windows 11).
After installation, open Docker Desktop Settings and confirm that WSL integration is enabled for your Ubuntu distribution (Settings > Resources > WSL integration).
Verify from inside WSL:
```console
$ wsl
$ docker info
```
`docker info` prints server information.
If you see "Cannot connect to the Docker daemon", confirm that Docker Desktop is running and that WSL integration is enabled.
## Set Up Local Inference with Ollama (Optional)
If you plan to select Ollama as your inference provider during onboarding, install it inside WSL before running the NemoClaw installer:
```console
$ curl -fsSL https://ollama.com/install.sh | sh
```
If Ollama is also running on the Windows side, quit it before running `nemoclaw onboard` (system tray > right-click > Quit).
The Windows and WSL instances bind to the same port and conflict.
The onboarding process starts Ollama in WSL if it is not already running.
You can also start it yourself beforehand with `ollama serve`.
## Next Step
Your Windows environment is ready.
Open a WSL terminal (type `wsl` in PowerShell, or open Ubuntu from Windows Terminal) and continue with the Quickstart (use the `nemoclaw-user-get-started` skill) to install NemoClaw and launch your first sandbox.
All NemoClaw commands run inside WSL, not in PowerShell.
## Troubleshooting
For Windows-specific troubleshooting, refer to the Windows Subsystem for Linux section (use the `nemoclaw-user-reference` skill) in the Troubleshooting guide.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |