clash-meta-proxy

Original：🇨🇳 Chinese

Translated

1 scriptsChecked / no sensitive code detected

Update clash-meta proxy configuration. Use when updating proxy nodes for clash-meta service, editing config.yaml with new proxies from .proxies.yaml, or maintaining proxy-groups consistency. Use the provided Python script with uv for automated backup, proxy update, and proxy-groups review.

3installs

Sourceqin2dim/skills

Added on2026-03-06

NPX Install

npx skill4agent add qin2dim/skills clash-meta-proxy

SKILL.md Content (Chinese)

View Translation Comparison →

Update Clash-Meta Configuration

Update the clash-meta proxy configuration on the server.

Environment Information

Default Working Directory:
```
./
```
Current Configuration File:
```
config.yaml
```
New Proxy Configuration:
```
.proxies.yaml
```

Automated Script Usage (Recommended)

A script with PEP 723 inline metadata is provided, supporting direct execution via

uv run

without manual dependency installation.

Execution Methods

Method 1: Direct Execution (Recommended)

bash

# In the work_dir
uv run scripts/update_clash_config.py

Method 2: Execute with Specified Working Directory

bash

uv run --cwd ./ scripts/update_clash_config.py

The script automatically performs the following:

File backup (creates
```
config.yaml.bak
```
, timestamped backup, and
```
config.yaml.editing
```
)
Reads
```
.proxies.yaml
```
and fully overwrites the
```
proxies
```
section
Verifies
```
proxy-groups
```
and comments out invalid proxies
Generates a diff output to the console and
```
.update.diff
```
file

Manual Confirmation and Activation (Critical Step)

The script will not automatically rename files; manual confirmation is required before execution:

Check Diff Output

bash

cat ./.update.diff

Activate After Confirmation

bash

mv ./config.yaml.editing ./config.yaml

Manual Operation Process

If the script cannot be used, follow these steps manually:

Backup Configuration

Copy
```
config.yaml
```
to
```
config.yaml.bak
```
Copy
```
config.yaml
```
to
```
config.yaml.editing
```

Update Proxies Configuration
- Read
```
.proxies.yaml
```
  to obtain new proxy nodes
- Fully overwrite the
```
proxies
```
  field in
```
config.yaml.editing
```
  with the new proxy list
Verify Proxy-Groups
- Check if the names referenced in
```
proxy-groups[*].proxies
```
  exist in the
```
proxies
```
  list
- Comment out invalid proxies instead of deleting them
Diff Confirmation and Rename
- Execute
```
diff config.yaml.bak config.yaml.editing
```
  to compare changes
- After confirmation, rename
```
config.yaml.editing
```
  to
```
config.yaml
```

Configuration Examples

.proxies.yaml Structure

yaml

proxies:
  - name: hy2.node.proxychain.top
    type: hysteria2
    server: IP
    port: PORT
    password: PASSWORD
    sni: hy2.node.proxychain.top
    skip-cert-verify: false

Proxy-Groups Structure

yaml

proxy-groups:
  - name: G-SELECT
    type: select
    proxies:
      # - 失效节点名    # 已失效，需注释
      - hy2.node.proxychain.top   # 有效节点

Notes

The names referenced in
```
proxy-groups[*].proxies
```
must strictly match
```
proxies[*].name
```
Only comment out invalid proxy names; keep the configuration structure intact
Always retain
```
config.yaml.bak
```
for rollback purposes
The final rename operation must be performed manually after confirmation

clash-meta-proxy

NPX Install

Tags

SKILL.md Content (Chinese)

Update Clash-Meta Configuration

Environment Information

Automated Script Usage (Recommended)

Execution Methods

Manual Confirmation and Activation (Critical Step)

Manual Operation Process

Configuration Examples

.proxies.yaml Structure

Proxy-Groups Structure

Notes