skills.rest
chrisfrantz
chrisfrantzCOMMUNITY
Explore all skills by this author →
GitHub

debug

Diagnose container agent issues by collecting and interpreting logs, environment, mounts, and IPC states.

Updated Aug 23, 2026
Search Tags:#troubleshooting#logs#codex#debug#diagnostics#container#ipc
One-click install
npx skills add https://github.com/chrisfrantz/nanoclaw --skill debug-chrisfrantz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/chrisfrantz/nanoclaw/tree/main/.codex/skills/debug
Command: npx skills add https://github.com/chrisfrantz/nanoclaw --skill debug-chrisfrantz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug container agent issues by collecting and interpreting logs, environment, mounts, and IPC states.

Core Features & Use Cases

  • Provides guidance to diagnose authentication problems, container failures, or misconfigurations across the NanoClaw container workflow.
  • Documents log locations, environment and mount checks, IPC tracing, and session behavior to identify root causes.
  • Includes practical steps for validating container health via manual testing and common failure scenarios.

Quick Start

Run the container in debug mode and inspect the logs to diagnose the issue.

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 failures and authentication issues?▼

Debug container agent failures by collecting and interpreting logs, environment variables, mount points, and IPC states. This diagnostic process identifies root causes for authentication problems and misconfigurations blocking normal container operation.

What's the best way to troubleshoot Codex CLI interactions inside a container?▼

Troubleshoot Codex CLI interactions by tracing IPC states and session behavior within the container. Inspecting log locations and applying manual testing procedures verifies container health and resolves communication blockages.

Where do I find container logs to diagnose misconfigurations?▼

Container logs for diagnosing misconfigurations are found by running the container in debug mode. This exposes detailed log locations, environment checks, and mount states to help identify the root cause of failures.

How do I verify container health after fixing an IPC or mount issue?▼

Verify container health by performing manual testing procedures that validate session behavior and environment configurations. This confirms that the resolved IPC states and mounts allow normal agent operation.

Why does my container agent fail to stabilize after a configuration change?▼

Container agents fail to stabilize after configuration changes due to broken IPC states, mount errors, or environment mismatches. Diagnose the exact failure by inspecting logs and running manual health checks.

Can I use this diagnostic approach for any container workflow or only Codex CLI?▼

This diagnostic approach applies across the container workflow and specifically addresses Codex CLI interactions. It enforces a repeatable workflow to resolve authentication problems, container failures, and misconfigurations.

Related Skills

Explore More Software Engineering Skills→
clsandovalclsandoval

setup

Automate NanoClaw setup by installing dependencies, configuring channels, and starting services.

Community
Advanced
webbotywebboty

debug

Analyzes logs, environment variables, mounts, and session data to identify root causes of NanoClaw/FlexClaw container issues.

Community
Intermediate
lookleelooklee

debug

Enable session debug logging and analyze logs for errors and warnings.

Community
Intermediate
githubgithub
123

awf-debug-tools

Parse AWF logs and container health to diagnose firewall problems.

Official
Intermediate