debug

Diagnoses and debugs NanoClaw container runtime issues including logs, environment variables, and mounts.

1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/breakcafe/picoclaw --skill debug-breakcafe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/breakcafe/picoclaw/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/breakcafe/picoclaw --skill debug-breakcafe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnosing and debugging the NanoClaw container-based Claude agent runtime to resolve failures, authentication problems, logs, environment setups, and common issues.

Core Features & Use Cases

  • Architecture overview to understand container-runner relationships and data flow.
  • Locating and inspecting logs across host and container to pinpoint failures.
  • Validating environment variables and mount configurations to ensure correct runtime behavior.
  • Troubleshooting common issues such as authentication errors, permissions, and MCP server startup.
  • Practical workflows for reproducible debugging sessions and issue resolution.

Quick Start

Run the diagnostic script to verify the container setup and identify common issues.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I debug container issues in a NanoClaw runtime?

To debug container issues in a NanoClaw runtime, you can run a diagnostic script that validates environment variables, inspects host and container logs, and checks mount configurations to pinpoint failures quickly.

Where do I find container logs to troubleshoot authentication errors?

You can troubleshoot authentication errors by locating and inspecting logs across both host and container contexts, which helps identify permission issues and startup failures within your containerized environment.

How do I validate environment variables and mount configurations for container debugging?

Validating environment variables and mount configurations involves checking your runtime setup to ensure correct behavior, preventing common issues related to permissions and MCP server startup during container debugging sessions.

What is the best way to diagnose MCP server startup failures in a containerized agent deployment?

The best way to diagnose MCP server startup failures is following a structured diagnostic workflow that inspects container logs, validates environment setups, and verifies mount sessions across host and container contexts.

Why is my container debugging workflow not resolving runtime failures?

Your container debugging workflow may not resolve runtime failures if environment variables are misconfigured or mount setups are incorrect, requiring a structured diagnostic approach to verify architecture and data flow.

Can I use a structured diagnostic workflow for reproducible container debugging sessions?

Yes, you can use structured diagnostic workflows for reproducible container debugging sessions, which provide safety checks and systematic guidance for troubleshooting issues across host and container environments.