clash-proxy

What This Skill Does

The clash-proxy skill is a robust, high-performance proxy management service for the OpenClaw environment, built on the industry-standard Mihomo (Clash.Meta) kernel. It acts as a central networking hub, enabling seamless internet connectivity for other OpenClaw skills by routing traffic through secure, customizable proxy chains. Beyond basic connectivity, it offers advanced traffic management, including automatic node selection based on latency, load balancing, automatic failover when a server node becomes unresponsive, and granular rule-based routing to ensure that only designated traffic passes through the proxy.

Installation

To integrate this utility into your OpenClaw ecosystem, execute the following command in your terminal: clawhub install openclaw/skills/skills/brucetangc/clash-proxy Once installed, you can manage the service using the provided bash scripts or standard systemd commands: systemctl start clash-proxy. Ensure your config.yaml is populated with your subscription URL or manual proxy credentials to begin routing traffic.

Use Cases

This skill is indispensable for users needing to bypass regional network restrictions or optimize connection speeds for external APIs. Common use cases include: 1) Enabling global access for web scraping tools or automated browser agents. 2) Centralizing proxy configuration across multiple AI skills, ensuring consistency in network identity. 3) Automating network maintenance for resource-intensive data synchronization tasks, such as syncing Garmin data, which may otherwise be blocked by regional ISP filtering.

Example Prompts

1. "OpenClaw, check if the clash-proxy service is running and report the current active proxy node for my traffic."
2. "Update my subscription nodes in clash-proxy and switch the active proxy group to the fastest available server."
3. "Restart the clash-proxy service and verify that I can successfully reach google.com through the local 7890 port."

Tips & Limitations

To maintain optimal performance, regularly update your subscription providers to avoid using deprecated nodes. While the service supports complex rule-based routing, be mindful that excessive rule definitions can slightly increase CPU overhead. Always use the provided health check tools (clash -t -d .) after modifying your configuration to prevent service crashes. Note that this skill manages network traffic at the process/service level; ensure that other skills are explicitly configured to point their proxy settings to 127.0.0.1:7890 to take advantage of this tunnel.