ZES System Debugging

Diagnose ZES Orchestration System failures by auditing service status, logs, and connectivity.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/ZESCODE/Zes-Orchestration-System --skill zes-system-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ZES System Debugging
Source: https://github.com/ZESCODE/Zes-Orchestration-System/tree/main/backups/snapshots/zes-20260711_161654/zes-system/.agents/skills/openclaw-debugging
Command: npx skills add https://github.com/ZESCODE/Zes-Orchestration-System --skill zes-system-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured diagnostic framework for troubleshooting the ZES Orchestration System, including 9Router, MCP servers, and background services.

Core Features & Use Cases

  • Service Health Monitoring: Quickly verify the status of runsv-managed services like the MCP server and Dashboard.
  • Connectivity Validation: Automate the verification of 9Router provider tokens and API model availability.
  • Use Case: When the AI sidepanel fails to respond, use this skill to check if the Chrome CDP is disconnected or if the MCP server requires a service restart.

Quick Start

Run the ZES system debugging skill to check the status of all background services and verify 9Router connectivity.

Frequently Asked Questions about ZES System Debugging

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

FAQPage Schema
How do I troubleshoot an unresponsive AI sidepanel and check Chrome CDP status?

To troubleshoot an unresponsive AI sidepanel, you can diagnose Chrome CDP disconnections or MCP server failures by auditing runsv-managed service health and executing automated shell commands to validate system integrity.

How do I verify 9Router connectivity and API model availability?

Verify 9Router connectivity by automating API health checks to validate provider tokens and confirm API model availability, ensuring the orchestration network routing layer correctly processes upstream requests and returns expected model responses.

What is the best way to monitor runsv-managed service health for MCP servers?

Monitor runsv-managed service health by auditing operational status logs for MCP servers and Dashboard background services, diagnosing infrastructure failures through automated status checks and network connectivity validation.

Why does my MCP server require a service restart during system administration?

Your MCP server requires a service restart when operational failures occur within the ZES Orchestration System, identifiable by auditing service status, log files, and API health checks to detect degraded background components.

Does this system debugging skill work without external dependencies?

Yes, this system debugging skill operates without external dependencies, diagnosing infrastructure issues by executing internal shell commands and API health checks to validate the ZES Orchestration System components.

What are the limitations of diagnosing ZES infrastructure failures through automated shell commands?

The limitation of diagnosing ZES infrastructure through automated shell commands is the scope, targeting only 9Router, MCP servers, and Chrome CDP interfaces, which may not detect external network outages or unrelated hardware faults.