clash-doctor

Diagnose Clash Verge and mihomo connectivity and manage profile routing configurations.

1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/rockcookies/skills --skill clash-doctor-rockcookies
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clash-doctor
Source: https://github.com/rockcookies/skills/tree/main/skills/majiayu-spellbook/clash-doctor
Command: npx skills add https://github.com/rockcookies/skills --skill clash-doctor-rockcookies

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Proxy failures, misconfigured AI tool routing, and multi-machine configuration drift in Clash Verge (mihomo) setups are hard to diagnose and risky to fix by hand. This Skill inspects the live kernel state, diagnoses connectivity issues, and safely manages profile overlays, local hub YAML, and TUN exclusions. ## Core Features & Use Cases - Connectivity Diagnosis: Runs read-only checks on DNS resolution, proxy ports, system proxy settings, and mihomo API state, then maps results to a diagnosis matrix with concrete fixes. - Profile & AI Routing Management: Lists profiles, clones enhancement overlays between remote subscriptions, configures AI tool routing rules (Claude, Codex, Cursor, Warp), and switches the active profile with confirmation gates. - Local Hub & Multi-Machine Alignment: Inspects local hub topology, compares configurations across Tailscale-connected machines read-only, and manages TUN route exclusions for relay IPs. - Use Case: When Claude Code stops connecting through your proxy, run a diagnosis to discover TUN DNS hijacking is active but traffic interception failed, then follow the guided fix to restart Clash Verge or adjust the configuration. ## Quick Start Ask the assistant to diagnose why github.com is unreachable through Clash Verge, or run "status" to see the current kernel, TUN, and selected node overview.

Frequently Asked Questions about clash-doctor

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

FAQPage Schema
How do I diagnose why my proxy is not working in Clash Verge?▼

Run the diagnosis mode with no argument or a target domain. It checks DNS resolution for fake-ip patterns, tests direct and proxied connectivity, scans common proxy ports, and queries the mihomo API, then maps results to a diagnosis matrix with prioritized fixes.

How to configure AI tool routing for Claude Code and Cursor in Clash Verge?▼

Use the setup-ai mode with a profile name. It writes process-name and domain rules for Claude, Codex, Cursor, and Warp into the profile's enhancement overlays, adds a residential proxy node and AI group, and requires confirmation before writing.

Why does my Clash Verge config not take effect after editing?▼

PUT /configs reloads merged output but does not re-merge enhancement overlays. After any overlay or hub YAML write, you must quit and reopen Clash Verge for changes to apply.

Can I clone overlay configurations between Clash Verge profiles?▼

Yes, the clone mode copies merge, script, rules, proxies, and groups overlays between two remote-type profiles. It refuses local-type targets and instead shows a minimal patch for the local hub YAML, with confirmation required before writing.

What is a fake-ip address in Clash TUN mode?▼

Fake-ip addresses come from ranges like 198.18.0.0/15 and indicate TUN DNS hijacking is active. If direct connections to fake-ip time out while proxied ones work, TUN traffic interception has failed and the proxy app likely needs a restart.

When should I not use this diagnostic skill?▼

Do not use it for general network speed testing, as it explicitly excludes that scope. It is specific to Clash Verge and mihomo on macOS; other proxy clients or platforms are outside its coverage.