skills.rest
VincentChong123
VincentChong123COMMUNITY
Explore all skills by this author →
GitHub

debug

Diagnose containerized agent failures by analyzing SQLite databases and Docker runtime logs.

Updated Jun 27, 2026
Search Tags:#debugging#troubleshooting#sqlite#docker#containers#nanoclaw
One-click install
npx skills add https://github.com/VincentChong123/nanoclaw-v2-agy-api-proxy --skill debug-vincentchong123
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/VincentChong123/nanoclaw-v2-agy-api-proxy/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/VincentChong123/nanoclaw-v2-agy-api-proxy --skill debug-vincentchong123

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires better-sqlite3, tsx, and includes scripts (resource) components.

What problem does it solve?

This Skill provides a structured framework for troubleshooting containerized agent execution, helping you identify and fix failures in message routing, container lifecycle, and database synchronization.

Core Features & Use Cases

  • System Diagnostics: Quickly verify the health of the host process, container runtime, and OneCLI gateway.
  • Session Inspection: Query inbound and outbound message databases to trace message flow and identify delivery bottlenecks.
  • Use Case: If an agent stops responding, use this Skill to check if the container exited prematurely, verify if the message reached the inbound database, and inspect logs for specific container stderr output.

Quick Start

Run the debug skill to check the status of your container runtime and verify the health of your current agent session.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I diagnose NanoClaw container agent execution failures?▼

To diagnose NanoClaw container agent execution failures, you analyze local SQLite databases, Docker runtime logs, and container lifecycle events. This process reconstructs the execution state to identify message routing, database synchronization, and environment configuration errors.

Why does my containerized agent stop responding during message routing?▼

An agent stops responding during message routing when the container exits prematurely or delivery bottlenecks block the inbound database. Inspecting host logs and querying outbound message databases traces the message flow to isolate the failure.

What is the best way to trace delivery errors in a NanoClaw architecture?▼

The best way to trace delivery errors in a NanoClaw architecture is querying inbound and outbound message databases. This session inspection traces exact message flow and pinpoints synchronization issues between the host process and the container runtime.

Do I need access to SQLite databases to troubleshoot Docker container lifecycle issues?▼

Yes, you need access to local SQLite databases to troubleshoot Docker container lifecycle issues. Querying these databases verifies if messages reached the inbound store and reconstructs the execution state alongside Docker runtime logs.

How to verify the health of a container runtime and OneCLI gateway?▼

Verify the health of a container runtime and OneCLI gateway by running system diagnostics. This checks the host process status, container lifecycle events, and gateway connectivity to ensure the execution environment is operating correctly.

Related Skills

Explore More Software Engineering Skills→
tharunramagiritharunramagiri

debug

Diagnose containerized agent failures by inspecting session databases and host logs.

Community
Advanced
FortemiFortemi
4

aiwg-doctor

Diagnose AIWG installation health and provide remediation commands.

Official
Intermediate
stevengonsalvezstevengonsalvez

init-onecli

Install OneCLI, migrate .env credentials to the Agent Vault, and verify setup.

Community
Intermediate
MovchanetsMovchanets

aspire-monitoring

Route Aspire diagnostics to the correct observability toolchain.

Community
Advanced