mihomo-proxy-debugging

Diagnose misrouted proxy traffic by validating Mihomo controller state and domain-to-proxy mappings.

1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/terencefan/inority-workspace --skill mihomo-proxy-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mihomo-proxy-debugging
Source: https://github.com/terencefan/inority-workspace/tree/main/skills/mihomo-proxy-debugging
Command: npx skills add https://github.com/terencefan/inority-workspace --skill mihomo-proxy-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps diagnose misrouted proxy traffic on Windows by validating local proxy paths, Mihomo controller state, and domain-to-proxy mappings for Mihomo, Clash, and related tools.

Core Features & Use Cases

  • Validate local proxy configuration and controller state to confirm traffic routing.
  • Map domain rules to the active proxy node and distinguish DNS, rule, and exit-node issues.
  • Use cases include verifying access to chatgpt.com/openai.com through a specific proxy or diagnosing 403/Cloudflare blocks.

Quick Start

Run the Mihomo proxy debugging workflow to verify the local proxy path and confirm domain-to-proxy mappings.

Frequently Asked Questions about mihomo-proxy-debugging

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

FAQPage Schema
How do I diagnose misrouted proxy traffic on Windows using Mihomo?

To diagnose misrouted proxy traffic, validate your local proxy paths and Mihomo controller state to confirm traffic routing. This helps map domain rules to the active proxy node and distinguish between DNS, rule, and exit-node issues.

Why does Cloudflare return a 403 block when accessing chatgpt.com through Mihomo proxy rules?

A Cloudflare 403 block occurs when domain-to-proxy mappings route traffic to an incorrect exit node. Diagnosing Mihomo proxy rules helps verify if chatgpt.com is properly routed through the intended proxy to bypass regional restrictions.

Do I need Mihomo controller listening on port 9090 to debug Clash proxy rules?

Yes, debugging Mihomo or Clash proxy rules requires the Mihomo controller listening on port 9090. You also need access to local proxy configuration and visibility into proxies, rules, and configurations to validate traffic routing.

How do I check if my domain-to-proxy mappings are routing traffic to the correct exit node?

Check domain-to-proxy mappings by validating local proxy configuration and controller state. This allows you to distinguish DNS resolution failures from rule mismatches and exit-node rejections within your Mihomo proxy setup.

Can I use this proxy debugging workflow for Shadowsocks rules on Windows?

Yes, this workflow applies to Windows environments debugging Mihomo, Clash, and SS (Shadowsocks) rules. It validates local proxy paths and maps domain rules to identify whether DNS, rule configurations, or exit-nodes are causing misrouted traffic.