debug

Diagnose container agent issues by correlating logs, environment settings, and mount configurations.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/cosmin/microclaw --skill debug-cosmin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/cosmin/microclaw/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/cosmin/microclaw --skill debug-cosmin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug container agent issues. Use when things aren't working, container fails, authentication problems, or to understand how the container system works. It covers logs, environment variables, mounts, and common issues.

Core Features & Use Cases

  • Diagnose container-runner problems by inspecting logs, env, and mounts.
  • Guide remediation for authentication and permission-related failures.
  • Quick-reference diagnostics for common container issues in MicroClaw workflows.

Quick Start

Run the debug skill to inspect container logs, verify session mounts, and review common issues for quick remediation.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I troubleshoot a container agent that keeps failing on startup?

Diagnose container authentication failures by verifying session data and reviewing environment variables for misconfigured credentials. The skill correlates these settings with container logs to pinpoint the root cause of access denial or permission errors.

Why does my container agent experience permission errors related to mounts?

Container mount permission errors often stem from incorrect session mount configurations. Verify that mount points are properly mapped and accessible within the MicroClaw runtime to resolve access restrictions and reproduce failure scenarios.

What's the best way to diagnose environment variable issues in a container runtime?

Diagnose environment variable issues by collecting the container's current environment settings and correlating them with observed failures. This approach isolates misconfigurations affecting authentication, permissions, and overall container agent stability.

Can I use this approach to fix issues across any container workflow?

Yes, this diagnostic approach applies across common container failure scenarios within MicroClaw workflows. It requires access to container logs, environment variables, mount points, and session data to verify configurations and guide remediation effectively.

What should I do when container logs don't reveal the cause of an agent crash?

When container logs are insufficient, cross-reference environment variables and mount configurations to reproduce the failure. Correlating session data with these settings often exposes hidden authentication or permission issues not visible in standard log output.