debug

Diagnose containerized AI agent issues by analyzing logs and verifying configurations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps diagnose and resolve issues with the containerized agent execution system, including problems with logs, environment variables, mounts, and authentication.

Core Features & Use Cases

  • Log Analysis: Pinpoint errors by examining host and container logs.
  • Configuration Verification: Check environment variable passing and volume mounts.
  • Authentication Debugging: Resolve issues related to API keys and tokens.
  • Use Case: If your agent is failing to start or process messages, use this Skill to check container logs, verify that your API key is correctly configured and mounted, and ensure all necessary directories are accessible within the container.

Quick Start

Run the diagnostic script to check common NanoClaw container setup 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 agent authentication failures and permission errors?

Debug container agent authentication failures by analyzing container runtime logs to pinpoint errors and verifying environment variable propagation. You must check that API keys and tokens are correctly configured and properly mounted into the container.

Why does my containerized AI agent fail to start or process messages?

Your containerized AI agent may fail to start due to misconfigured volume mounts, inaccessible directories, or environment variables not passing correctly. Running a diagnostic script checks these common container setup issues to resolve startup failures.

What is the best way to verify environment variable propagation in a Docker container?

The best way to verify environment variable propagation in a Docker container is to run a diagnostic script that checks host and container logs. This confirms variables are correctly passed and accessible to the agent runtime.

Do I need access to the host file system to troubleshoot Docker container issues?

Yes, you need access to the host file system to troubleshoot Docker container issues effectively. Host file system access is required to examine volume mount configurations and read container runtime logs for diagnostics.

How do I resolve volume mount configuration problems causing inter-process communication failures?

Resolve volume mount configuration problems by verifying that all necessary directories are accessible within the container. Analyze logs to identify inter-process communication issues and ensure mounts are correctly configured on the host.