Nemoclaw User Deploy Remote
Move NemoClaw off a laptop onto a remote GPU instance with clear deploy steps, Brev legacy caveats, and post-setup operations.
Overview
nemoclaw-user-deploy-remote is an agent skill most often used in Operate (also Ship) that walks through moving NemoClaw to remote GPU instances with deprecation-aware deploy and recovery guidance.
Install
npx skills add https://github.com/nvidia/skills --skill nemoclaw-user-deploy-remoteWhat is this skill?
- Guidance for deploying NemoClaw to remote GPU instances for persistent or GPU-backed sandboxes
- Explains legacy Brev compatibility flow—including what still works and what is deprecated
- Post-deploy focus: connection details, day-2 operation, and recovery after initial setup
- Frames decision criteria and verification so you do not rely on outdated deploy paths blindly
- NVIDIA NemoClaw-specific operational framing rather than generic cloud VM tutorials
Adoption & trust: 1 installs on skills.sh; 1.1k GitHub stars; trending (+100% hot-view momentum).
What problem does it solve?
You want NemoClaw off your laptop on a GPU instance but lack a trusted sequence for deploy, legacy Brev paths, and post-setup operations.
Who is it for?
Indie builders running NVIDIA NemoClaw who need GPU-backed remote sandboxes and explicit warnings about legacy Brev compatibility.
Skip if: Anyone not using NemoClaw, or teams wanting only local CPU assistants without remote infra ownership.
When should I use this skill?
Deploying NemoClaw to a remote GPU, understanding legacy Brev compatibility deprecation, or finding post-deploy connection and recovery details.
What do I get? / Deliverables
You can complete remote deployment with verified connectivity and know which flows are deprecated so day-2 operation and recovery are repeatable.
- Remote deployment runbook steps
- Verified connection and recovery checklist
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Remote GPU hosting is shelved under Operate/infra because the goal is sustained production-like sandboxes, not first-time product coding. The skill addresses instance provisioning, connection, and recovery—core infrastructure operations after you choose NemoClaw as your assistant runtime.
Where it fits
Cut over from local NemoClaw to a remote GPU before sharing the assistant with collaborators.
Re-establish SSH or service endpoints after an instance recycle.
Audit whether automation still calls deprecated Brev paths and migrate to supported deploy steps.
How it compares
NemoClaw-specific remote GPU deploy playbook—not a general Kubernetes or Terraform baseline skill.
Common Questions / FAQ
Who is nemoclaw-user-deploy-remote for?
Solo builders and small teams operating NemoClaw who need to host the sandboxed assistant on a remote GPU instead of a local dev machine.
When should I use nemoclaw-user-deploy-remote?
Use it during Ship/Launch when moving off local-only setups, and during Operate when reconnecting, recovering, or auditing whether your deploy still relies on deprecated Brev compatibility steps.
Is nemoclaw-user-deploy-remote safe to install?
Review the Security Audits panel on this Prism page; remote deploy skills often imply SSH, cloud APIs, and secrets—validate every command against your provider and org policy.
SKILL.md
READMESKILL.md - Nemoclaw User Deploy Remote
[ { "id": "docs-deployment-deploy-to-remote-gpu-001", "question": "I'm deploying NemoClaw to a remote GPU instance. Help me move the sandboxed assistant off my local machine so I can support persistent or GPU-backed operation.", "expected_skill": "nemoclaw-user-deploy-remote", "ground_truth": "A NemoClaw-specific answer that helps the user move the sandboxed assistant off my local machine and gives enough concrete guidance, decision criteria, verification steps, or risk framing to support persistent or GPU-backed operation." }, { "id": "docs-deployment-deploy-to-remote-gpu-002", "question": "I'm using the legacy Brev compatibility flow. Help me understand what the flow still does and where it is deprecated so I can avoid depending on an outdated path blindly.", "expected_skill": "nemoclaw-user-deploy-remote", "ground_truth": "A NemoClaw-specific answer that helps the user understand what the flow still does and where it is deprecated and gives enough concrete guidance, decision criteria, verification steps, or risk framing to avoid depending on an outdated path blindly." }, { "id": "docs-deployment-deploy-to-remote-gpu-003", "question": "I'm after remote deployment succeeds. Help me find the connection, operation, and recovery details so I can operate the sandbox after initial setup.", "expected_skill": "nemoclaw-user-deploy-remote", "ground_truth": "A NemoClaw-specific answer that helps the user find the connection, operation, and recovery details and gives enough concrete guidance, decision criteria, verification steps, or risk framing to operate the sandbox after initial setup." }, { "id": "docs-deployment-brev-web-ui-001", "question": "I'm launching NemoClaw from the Brev web UI. Help me avoid local CLI setup and local GPU requirements so I can start a hosted sandbox quickly.", "expected_skill": "nemoclaw-user-deploy-remote", "ground_truth": "A NemoClaw-specific answer that helps the user avoid local CLI setup and local GPU requirements and gives enough concrete guidance, decision criteria, verification steps, or risk framing to start a hosted sandbox quickly." }, { "id": "docs-deployment-brev-web-ui-002", "question": "I'm reviewing hosted launch choices. Help me understand each web UI option before creating the instance so I can choose settings that match my expected sandbox workflow.", "expected_skill": "nemoclaw-user-deploy-remote", "ground_truth": "A NemoClaw-specific answer that helps the user understand each web UI option before creating the instance and gives enough concrete guidance, decision criteria, verification steps, or risk framing to choose settings that match my expected sandbox workflow." }, { "id": "docs-deployment-brev-web-ui-003", "question": "I'm the hosted sandbox is created. Help me confirm where to connect and how to start using it so I can move from provisioning to actual agent work.", "expected_skill": "nemoclaw-user-deploy-remote", "ground_truth": "A NemoClaw-specific answer that helps the user confirm where to connect and how to start using it and gives enough concrete guidance, decision criteria, verification steps, or risk framing to move from provisioning to actual agent work." }, { "id": "docs-deployment-install-openclaw-plugins-001", "question": "I'm installing an OpenClaw plugin in a NemoClaw-managed sandbox. Help me add a new agent capability inside the sandbox so I can extend the assistant without weakening the host boundary.", "expected_skill": "nemoclaw-user-deploy-remote", "ground_truth": "A NemoClaw-specific answer that helps the user add a new agent capability inside the sandbox and gives enough concrete guidance, decision criteria, verification steps, or risk framing to extend the assistant without weakening the host boundary." }, { "id": "docs-deployment-install-openclaw-plugins-002", "question": "I'm deciding where to install a plug