juliaz-debug

Diagnose cross-system failures across bridge, orchestrator, OpenClaw, backend, and frontend.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-system diagnostics for the juliaz_agents ecosystem to identify and triage failures across bridge, orchestrator, OpenClaw, backend, and frontend.

Core Features & Use Cases

  • Quick Health Scan: Provides a rapid, end-to-end snapshot of system health, listing running services, containers, ports, and endpoint statuses for quick triage.
  • Diagnostic Decision Tree: Step-by-step guidance for common failure modes (communication between components, API timeouts, and deployment issues) to determine root causes quickly.
  • Logs & Readability: Best practices for reading PM2, orchestrator, bridge, and MCP logs to extract actionable insights without noise.
  • Recovery & Escalation: Clear restart and remediation steps, including service restarts, queue fixes, and configuration checks to restore operation.
  • End-to-end triage: Enables cross-service coordination to diagnose multi-component failures and ensure system recovery.

Quick Start

Run a quick health scan by checking running services, container status, port usage, and health endpoints to get the system state in seconds.

Frequently Asked Questions about juliaz-debug

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

FAQPage Schema
How do I troubleshoot messages not arriving in a multi-component agent ecosystem?

To troubleshoot messages not arriving, run a quick health scan checking running services, containers, and endpoint statuses, then follow the diagnostic decision tree to trace communication failures across the bridge, orchestrator, backend, and frontend.

What is the best way to read PM2 and orchestrator logs for silent failures?

The best way to read PM2 and orchestrator logs is to apply readability best practices that filter out noise, allowing you to extract actionable insights and identify whether silent failures or queue stalls originate in the bridge or backend systems.

How do I diagnose cross-system failures when an agent stops responding?

Diagnose cross-system failures by running an end-to-end health snapshot to verify endpoint statuses, then use the decision tree to check for API timeouts, rate limits, or orchestrator stalls preventing the agent from responding.

What steps are needed to restart services and fix queue stalls after a bridge error?

To fix queue stalls and bridge errors, follow the recovery and escalation steps to perform service restarts, apply queue fixes, and run configuration checks across the orchestrator and backend to restore system operation.

Does this diagnostics workflow cover rate limits and API timeouts across all components?

Yes, the diagnostics workflow covers rate limits and API timeouts by providing step-by-step guidance for common failure modes, ensuring you can determine root causes across the bridge, orchestrator, OpenClaw, backend, and frontend.