What problem does it solve? Routing rules on a 3x-ui panel fail silently: geo tokens that do not exist never match, broad rules shadow narrow exceptions, and disabled sniffing makes every domain rule miss. This Skill guides building, ordering, validating, and verifying Xray routing so traffic actually goes where intended. ## Core Features & Use Cases - Rule construction and ordering: Add, update, and remove routing rules with correct index placement, since the first match wins and appended rules may never be reached. - Geo token validation: Check geosite and geoip tokens against the server's actual databases before saving, and browse categories instead of guessing names. - Provider outbounds: Register and manage Warp, NordVPN, and PIA outbounds, then target their tags from routing rules. - Router-based verification: Use test_route to see what the running core would do with a destination, plus balancer overrides and outbound health checks. - Use Case: Route OpenAI domains through Warp, block ads and bittorrent, and direct private IPs to the direct outbound, then confirm each rule matches and one unaffected destination still uses the default path. ## Quick Start Ask the agent to route geosite:openai through the Warp outbound on the 3x-ui panel, block the ads category, and verify both rules with test_route.
