skills.rest
yo-steven
yo-stevenCOMMUNITY
Explore all skills by this author →
GitHub

nemoclaw-user-reference

Explains NemoClaw's host CLI, TypeScript sandbox plugin, blueprint architecture, network policies, and troubleshooting workflows for OpenClaw sandbox operations.

Updated May 23, 2026
Search Tags:#troubleshooting#network policy#command reference#nemoclaw architecture#openshell cli#sandbox egress#operator approval flow
One-click install
npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill nemoclaw-user-reference-yo-steven
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nemoclaw-user-reference
Source: https://github.com/yo-steven/skills-exploration-20260522/tree/main/skills/NemoClaw/nemoclaw-user-reference
Command: npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill nemoclaw-user-reference-yo-steven

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

NemoClaw users need a single, reliable reference for how the NemoClaw plugin and blueprint architecture work together with OpenShell to orchestrate an OpenClaw sandbox, including which CLI to use and what to do when sandbox networking is blocked.

Core Features & Use Cases

  • NemoClaw architecture understanding: Explains how the host CLI, the TypeScript plugin running inside the sandbox, and the versioned YAML blueprint coordinate to provision, secure, and run the OpenClaw sandbox.
  • Plugin and blueprint design guidance: Covers the blueprint lifecycle (resolve, verify digest, plan, apply, status) and how policies and inference profiles are defined and enforced.
  • CLI selection and operational command reference: Provides guidance on when to use nemoclaw versus openshell, plus a detailed reference for NemoClaw and /nemoclaw slash commands and their subcommands.
  • Network policy and operator approval flow: Documents deny-by-default policy behavior, baseline policy endpoints and filesystem rules, and the runtime sequence for operator approval of blocked requests.
  • Troubleshooting pathways: Offers targeted fixes for installation, onboarding, and runtime issues, including common failure modes like DNS/corporate firewall problems and gateway/sandbox connectivity issues.

Quick Start

Ask the AI to explain the NemoClaw plugin and blueprint architecture and how it orchestrates OpenClaw sandboxes using the correct CLI commands for troubleshooting.

Frequently Asked Questions about nemoclaw-user-reference

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does the NemoClaw plugin and blueprint architecture orchestrate an OpenClaw sandbox?▼

The NemoClaw plugin and blueprint architecture orchestrates an OpenClaw sandbox by coordinating a host CLI, an in-sandbox TypeScript plugin, and a versioned YAML blueprint to provision, secure, and run the environment.

When should I use the nemoclaw CLI versus openshell for sandbox operations?▼

Use the nemoclaw CLI versus openshell based on your operational target: nemoclaw manages blueprint-driven provisioning and slash commands, while openshell handles direct host-level interactions for sandbox operations.

How do I troubleshoot blocked sandbox egress and DNS connectivity issues in NemoClaw?▼

Troubleshoot blocked sandbox egress and DNS connectivity in NemoClaw by checking the deny-by-default network policy, verifying baseline endpoints, and diagnosing corporate firewall or gateway interruptions.

What is the operator approval flow for blocked network requests in a deny-by-default sandbox?▼

The operator approval flow for blocked network requests in a deny-by-default sandbox triggers at runtime, requiring explicit operator authorization before any egress outside baseline policy endpoints is permitted.

How do I look up nemoclaw subcommands and flags for OpenShell CLI workflows?▼

Look up nemoclaw subcommands and flags for OpenShell CLI workflows by querying the command-level reference, which details slash commands, operational flags, and blueprint lifecycle stages like resolve, plan, and apply.

Why does my NemoClaw onboarding fail during blueprint verify digest and provisioning?▼

NemoClaw onboarding fails during blueprint verify digest and provisioning due to versioned YAML mismatches, plugin execution errors, or blocked filesystem rules preventing proper OpenClaw sandbox initialization.

Related Skills

Explore More Education & Research Skills→
rblake2320rblake2320

nemoclaw-user-reference

Map NemoClaw plugin, blueprint, and OpenShell interactions to host, gateway, sandbox, and provider components.

Community
Advanced
cyoteecyotee

Comet Architecture

Explain Compound V3 Comet architecture with component roles and contract mappings.

Community
Basic
NVIDIA-NeMoNVIDIA-NeMo
58

deploy-sandbox

Deploy NAT agents as isolated OpenShell sandboxes with Landlock filesystem protection.

Official
Advanced
NeKon69NeKon69
1

Octo.nvim API Reference

Reference Octo.nvim Lua functions and commands for GitHub interactions.

Community
Basic