debug

Diagnose container agent issues in Claude-based workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug container agent issues: troubleshoot logs, environment variables, mounts, authentication, and session behavior to keep Claude-based workflows running smoothly.

Core Features & Use Cases

  • Provides structured guidance to identify and resolve container-spawn issues, misconfigurations, and authentication problems.
  • Documents common failure points, log locations, and debugging workflows for rapid triage.
  • Used by engineers to reproduce issues locally and validate fixes across host and container boundaries.

Quick Start

Run diagnostic commands to reproduce issues, identify misconfigurations, and verify container logs.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I debug Claude container agent issues with logs and environment variables?

Debug Claude container agent issues by running diagnostic commands to inspect logs, environment variables, and Docker configuration. This guides remediation for misconfigurations and authentication failures across host and container boundaries.

Why does my Claude container agent fail to spawn or authenticate?

Container agent spawn and authentication failures usually stem from misconfigurations in Docker setup or environment variables. Inspect container logs and session behavior to identify the specific failure point for rapid triage.

What is the best way to troubleshoot container mounts and session behavior in Claude workflows?

Troubleshoot container mounts and session behavior by accessing Docker configuration and log locations to reproduce issues locally. Validate fixes across host and container boundaries to keep Claude-based workflows running smoothly.

Do I need Docker configuration access to diagnose container agent problems?

Yes, diagnosing container agent problems requires access to logs, Docker configuration, and container environment details. This access is necessary to identify misconfigurations and guide remediation for Claude-based workflows.

What are common limitations when debugging container environment variables across host and container boundaries?

Limitations arise when container environment variables and mounts are inaccessible or lack proper configuration. Reproduce issues locally and verify container logs to validate fixes across host and container boundaries.

Can I reproduce container agent issues locally to validate fixes before deploying?

Yes, you can reproduce container agent issues locally by running diagnostic commands and inspecting logs. Validate fixes across host and container boundaries to ensure Claude-based workflows run smoothly after deployment.