proxy-doctor

Diagnose Claude Code CLI local proxy failures affecting GLM and MiniMax routing.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/fukukei23/claude-config --skill proxy-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proxy-doctor
Source: https://github.com/fukukei23/claude-config/tree/main/.claude/worktrees/make-song-analyze-song-bridge/skills/proxy-doctor
Command: npx skills add https://github.com/fukukei23/claude-config --skill proxy-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps troubleshoot failures in the glm-rate-proxy local routing layer that connects Claude Code CLI to GLM and MiniMax, reducing downtime caused by proxy crashes, API errors, and fallback failures.

Core Features & Use Cases

  • Proxy Health Diagnosis: Collects process status, connection settings, proxy status, and recent logs to identify common failure patterns.
  • Error Pattern Resolution: Guides fixes for issues including 400 tool errors, 401 authentication failures, 429 rate limits, timeout problems, routing issues, and MiniMax fallback failures.
  • Use Case: When Claude Code CLI cannot access its configured LLM backend, use this Skill to classify the issue, explain the cause, and provide safe recovery steps without automatically modifying source code.

Quick Start

Ask the proxy-doctor skill to diagnose why Claude Code CLI is failing to connect to GLM or MiniMax through the local proxy.

Frequently Asked Questions about proxy-doctor

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

FAQPage Schema
How do I fix Claude Code CLI failing to connect to GLM or MiniMax through a local proxy?

To fix Claude Code CLI failing to connect through a local proxy, diagnose process status, environment routing, proxy status endpoints, and recent logs to classify the issue and apply safe recovery steps without modifying source code.

What causes 429 rate limit errors in localhost LLM proxy routing?

429 rate limit errors in localhost LLM proxy routing occur when backend API limits are exceeded. Diagnostic validation of proxy status endpoints and recent logs helps identify the failure pattern and guide appropriate resolution steps.

How does proxy health diagnosis work for LLM routing failures?

Proxy health diagnosis for LLM routing failures works by collecting process status, connection settings, proxy status endpoints, and recent logs to identify common failure patterns like API errors, crashes, and fallback failures.

Can I resolve MiniMax fallback failures without automatically modifying source code?

Yes, you can resolve MiniMax fallback failures without modifying source code by diagnosing backend connectivity problems and applying safe recovery steps guided by error pattern classification from recent logs.

Why does my local proxy return 400 tool errors when routing to GLM?

Local proxy 400 tool errors when routing to GLM indicate malformed requests or tool configuration issues. Diagnosing recent logs and proxy status endpoints classifies the error pattern to guide safe resolution steps.