skills.rest
stevenrick
stevenrickCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

dev

Diagnose NemoClaw issues across NemoClaw, OpenClaw, and OpenShell components.

2|Updated Apr 2, 2026
Search Tags:#debug#diagnose#upstream#openshell#nemoclaw#patch-testing
One-click install
npx skills add https://github.com/stevenrick/nemoclaw-cookbook --skill dev-stevenrick
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev
Source: https://github.com/stevenrick/nemoclaw-cookbook/tree/main/.claude/skills/dev
Command: npx skills add https://github.com/stevenrick/nemoclaw-cookbook --skill dev-stevenrick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigate NemoClaw internals, debug issues across the NemoClaw/OpenClaw/OpenShell stack, test upstream branches, and contribute fixes. Use when something isn't working and you need to dig deeper than the user-facing docs cover.

Core Features & Use Cases

  • End-to-end issue diagnosis across NemoClaw, OpenClaw, and OpenShell.
  • Test upstream branches and patches to validate behavior before deployment.
  • Contribute fixes upstream to reduce patch fragmentation and keep deployments aligned with upstream.

Quick Start

Run a diagnostic session against a malfunctioning NemoClaw sandbox to identify root causes.

Frequently Asked Questions about dev

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

FAQPage Schema
How do I debug issues across the NemoClaw, OpenClaw, and OpenShell stack?▼

Diagnosing NemoClaw stack issues involves tracing failures across NemoClaw, OpenClaw, and OpenShell components to identify root causes and validate interactions using defined workflows and guardrails.

What is the best way to test upstream patches before deploying to NemoClaw?▼

Testing upstream patches involves validating behavior against upstream branches before deployment. This process reduces patch fragmentation and ensures deployments remain aligned with upstream project changes.

How do I contribute fixes to upstream OpenClaw or OpenShell projects?▼

Contributing upstream fixes requires diagnosing interactions across the stack, verifying the patch behavior, and submitting fixes to upstream projects to reduce patch fragmentation and keep deployments aligned.

Why does my NemoClaw sandbox malfunction when interacting with OpenShell?▼

NemoClaw sandbox malfunctions during OpenShell interactions often stem from cross-component failures. Run a diagnostic session to trace failures across the NemoClaw, OpenClaw, and OpenShell stack and isolate the root cause.

Can I diagnose NemoClaw issues without deep knowledge of the underlying OpenClaw internals?▼

Yes, you can diagnose NemoClaw issues by running a diagnostic session against the malfunctioning sandbox. The workflow defines the necessary validations and guardrails to dig deeper than user-facing documentation covers.

Related Skills

Explore More Software Engineering Skills→
yo-stevenyo-steven

nemoclaw-user-overview

Explain OpenClaw, OpenShell, and NemoClaw ecosystem placement for deployment decisions.

Community
Basic
sangrokjungsangrokjung
1

electron-chromium-upgrade

Guide Chromium version upgrades in Electron projects with patch conflict management.

Community
Advanced
yo-stevenyo-steven

nemoclaw-user-monitor-sandbox

Diagnose failing NemoClaw sandboxes via health, logs, and live network activity.

Community
Intermediate
sayalinvidiasayalinvidia

nemoclaw-user-overview

Plan NemoClaw, OpenShell, and OpenClaw deployments with onboarding and risk assessment.

Community
Advanced