skills.rest
sskarz
sskarzCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debug

Diagnose and fix container issues in NanoClawbster, including authentication, logs, and mounts.

2|2|Updated Feb 25, 2026
Search Tags:#debugging#troubleshooting#logs#container#environment-variables#session-persistence#mounts
One-click install
npx skills add https://github.com/sskarz/nanoclawbster --skill debug-sskarz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/sskarz/nanoclawbster/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/sskarz/nanoclawbster --skill debug-sskarz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug container issues in NanoClawbster by diagnosing container runs, logs, mounts, and authentication problems.

Core Features & Use Cases

  • Guided debugging for the containerized agent execution system, including session persistence and mount configurations.
  • Troubleshooting workflows for logs, environment variables, and MCP/server initialization misconfigurations.
  • Best-practice references for diagnosing common failures and validating container startup conditions.

Quick Start

Follow the guide to check logs, verify the /home/node/.claude mount path, and validate environment variables to resolve container 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 authentication problems and failed startup runs?▼

Debug container authentication issues by following guided workflows to check container logs, verify the /home/node/.claude mount path, and validate environment variable propagation to resolve startup failures.

Where do I find container logs to troubleshoot agent execution failures?▼

Container logs for troubleshooting agent execution failures are located in specific log directories identified during the debugging workflow, allowing you to diagnose MCP and server initialization misconfigurations.

Why does my container lose session persistence and fail to resume?▼

Container session persistence failures often stem from incorrect mount configurations or environment variable propagation issues; verifying the /home/node/.claude mount path helps diagnose and fix session resumption problems.

How do I fix MCP or server initialization misconfigurations in a containerized environment?▼

Fix MCP and server initialization misconfigurations by applying troubleshooting workflows that validate container startup conditions, check environment variables, and verify mount configurations for proper server initialization.

What environment variables need to be validated when a container run fails?▼

When a container run fails, validate environment variables related to authentication and server configuration by checking their propagation paths to ensure the containerized agent receives the correct runtime parameters.

Can I use this debugging workflow to verify mount configurations for containerized agents?▼

Yes, the debugging workflow specifically covers verifying mount configurations like the /home/node/.claude path, diagnosing common mount-related failures, and validating container startup conditions for agent execution.

Related Skills

Explore More Software Engineering Skills→
mgkyawzayyamgkyawzayya
1

debug

Diagnose container agent issues by inspecting logs, mounts, and environment variables.

Community
Intermediate
zhaosj0315zhaosj0315

debug

Diagnose and fix containerized NanoClaw agent issues via logs and environment checks.

Community
Advanced
alangebalangeb

docker

Manage Docker container lifecycles and service orchestration via compose operations.

Community
Intermediate
DingyangLyuDingyangLyu
85

debug

Diagnoses Docker/AJSHA client container and agent-run failures including authentication, mounts, permissions, sessions, and MCP/SDK errors.

Community
Advanced