debug

Diagnose NanoClaw container issues by inspecting logs, environments, and mounts.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/clsandoval/monorepo --skill debug-clsandoval
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/clsandoval/monorepo/tree/main/automations/nanoclaw/.claude/skills/debug
Command: npx skills add https://github.com/clsandoval/monorepo --skill debug-clsandoval

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers quickly identify and fix issues in the NanoClaw container environment, from authentication to session resumption and log analysis.

Core Features & Use Cases

  • Diagnose container run failures and misconfigurations affecting logs, env, mounts, and permissions.
  • Provide step-by-step debugging workflows for common container issues and authentication problems.
  • Use case: A developer sees "Claude Code process exited with code 1" and follows this guide to isolate the root cause.

Quick Start

Follow the diagnostic steps to reproduce and resolve a container failure in your local environment.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I debug a NanoClaw container crash when the Claude Code process exits with code 1?

Debug a NanoClaw container crash by following a repeatable diagnostic workflow that inspects container logs, environment variables, and mount paths to isolate the root cause of the process exit. It enumerates log locations and common remedies.

Why does my NanoClaw container fail session resumption in local development?

Session resumption failures in NanoClaw often stem from misconfigured mounts or environment variable handling. The diagnostic workflow inspects mount paths and authentication setups to identify and resolve the configuration mismatch.

How do I troubleshoot authentication problems in a NanoClaw container environment?

Troubleshoot NanoClaw authentication problems by inspecting environment variables and logs to verify credential handling. The workflow provides step-by-step checks for common authentication misconfigurations in local or CI environments.

What is the best way to inspect NanoClaw container logs and environment variables?

The best way to inspect NanoClaw container logs and environment variables is using the provided diagnostic workflow, which enumerates specific log locations and environment variable handling rules to quickly identify misconfigurations.

Can I use this debugging workflow for NanoClaw misconfigured mounts in CI environments?

Yes, you can use this workflow to debug NanoClaw misconfigured mounts in CI environments. The diagnostic steps apply to both local development and CI pipelines to inspect mount paths and resolve permission issues.

What should I check first when a NanoClaw container run fails?

When a NanoClaw container run fails, first check the container logs, environment variables, and mount paths. The diagnostic workflow guides you through these inspection steps to reproduce and resolve the failure.