diagnostics

Diagnose protocol-proxy failures via health checks, logs, and request analysis.

4|Updated May 9, 2026
One-click install
npx skills add https://github.com/liaoxinjie666/protocol-proxy --skill diagnostics-liaoxinjie666
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnostics
Source: https://github.com/liaoxinjie666/protocol-proxy/tree/main/skills/system/diagnostics
Command: npx skills add https://github.com/liaoxinjie666/protocol-proxy --skill diagnostics-liaoxinjie666

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users rapidly identify why a protocol proxy is unhealthy, slow, failing to forward requests, or unable to use MCP tools by running structured diagnostics and summarizing findings into clear next actions.

Core Features & Use Cases

  • Health checks: Collects runtime, proxy, provider, and API key health data, then highlights abnormal items and severity for quick triage.
  • Log and request analysis: Pulls system logs and recent request failures to detect error patterns, frequency spikes, and affected proxies/providers/models.
  • Targeted proxy diagnostics: Diagnoses a specific proxy’s connectivity, provider availability, key health, request chain behavior, routing strategy, and (optionally) end-to-end client connectivity.
  • MCP troubleshooting: Checks MCP server connectivity, validates common misconfigurations (package name, stdio vs HTTP, port conflicts), and reports tool availability.
  • Sub-agent/delegation debugging: Investigates failed delegated tasks by reviewing task details, exec-policy behavior, sandbox and permission issues, and configuration settings.

Quick Start

Ask the AI to run a system health check and, if problems are found, automatically drill down into the most likely failing proxy, provider key, or MCP service.

Frequently Asked Questions about diagnostics

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

FAQPage Schema
How do I diagnose protocol proxy failures and connection errors?

Diagnose protocol proxy failures by orchestrating internal function calls to check system health, proxy status, and recent request outcomes. This approach identifies abnormal items and pinpoints the root cause of connection errors or forwarding exceptions across running proxies.

Why does my MCP server connectivity fail and how to troubleshoot it?

Troubleshoot MCP server connectivity by validating common misconfigurations like package names, stdio versus HTTP transport, and port conflicts. This diagnostic process checks server connectivity and reports tool availability to resolve MCP tool failures.

What is the best way to investigate high request latency and slow proxy responses?

Investigate high request latency by pulling system logs and recent request failures to detect error patterns and frequency spikes. This analysis diagnoses proxy routing strategies, provider availability, and API key health to isolate slow response bottlenecks.

How do I debug failed sub-agent delegated tasks and exec-policy issues?

Debug failed sub-agent delegated tasks by reviewing task details, exec-policy behavior, and sandbox permission issues. This diagnostic process inspects configuration settings to identify why delegated sub-agent failures occur across running proxies.

Can I check API key health and provider availability across multiple proxies?

Check API key health and provider availability across proxies by orchestrating targeted diagnostic function calls. This process collects runtime data and queries specific proxy connectivity to highlight key health abnormalities and provider status for rapid triage.