network-proxy

---
name: network-proxy
description: Helps when network-related commands (like curl, git, npm, pip, brew) are failing, timing out, or running slowly due to network issues. It suggests and applies proxy environment variables to fix connectivity problems.
---

# Network Proxy Skill

This skill helps you troubleshoot and fix network connectivity issues by applying proxy settings.

## When to use
- A command fails with a network error (e.g., "connection refused", "timeout", "network unreachable").
- A download or installation is extremely slow.
- You explicitly ask to "use proxy" or "turn on proxy".

## Default Proxy Configuration
Unless the user specifies otherwise, assume the local proxy is running at:
- HTTP Proxy: `http://127.0.0.1:7892`
- HTTPS Proxy: `http://127.0.0.1:7892`
- SOCKS Proxy: `socks5://127.0.0.1:7892`

(Note: Port 7892 is common for tools like Clash/V2Ray. Adjust if the user provides a different port.)

## How to Apply

### 1. Temporary (One-off command)
For a single command execution, prepend the environment variables:

```bash
export https_proxy=http://127.0.0.1:7892 http_proxy=http://127.0.0.1:7892 all_proxy=socks5://127.0.0.1:7892
[original command]
```

Example:
```bash
export https_proxy=http://127.0.0.1:7892 http_proxy=http://127.0.0.1:7892 all_proxy=socks5://127.0.0.1:7892
git clone https://github.com/some/repo.git
```

### 2. Session-wide (Current terminal)
To set it for the current session:

```bash
export https_proxy=http://127.0.0.1:7892
export http_proxy=http://127.0.0.1:7892
export all_proxy=socks5://127.0.0.1:7892
```

### 3. Unset (Turn off)
To clear the proxy settings:

```bash
unset https_proxy http_proxy all_proxy
```

## Troubleshooting
If the default port (7892) doesn't work:
1. Ask the user for their proxy port (common alternatives: 1080, 1087, 8080).
2. Check if a proxy tool is running.

More agent context in didi/mpx

13 other files this repository gives its agents.