What problem does it solve? When a 3x-ui proxy client reports "it stopped working", this Skill provides a systematic, fastest-first diagnostic sequence that isolates whether the cause is the Xray core, the inbound, the client's own limits, routing and outbounds, or the node — using only read-only MCP tool calls. ## Core Features & Use Cases - Scoped triage: Classifies the outage as panel-wide, per-inbound, per-client, or per-destination before running any checks, so diagnosis starts at the right layer. - Client limit inspection: Checks enable flags, expiryTime, totalGB quotas, limitIp, and HWID device slots, and decodes common Xray log lines such as flow mismatches for VLESS Vision. - Routing and outbound verification: Uses test_route, test_outbound, balancer and geodata checks to find why a destination fails while the connection itself works. - Use Case: A user reports one client cannot connect while others work fine. The Skill walks through get_client, get_client_traffic, and get_last_online to discover the client's expiryTime passed, distinguishing it from a network failure. ## Quick Start Ask the assistant to diagnose why a 3x-ui client cannot connect, providing the client's email or a description of who is affected.