Agent skill

Higress Openclaw Integration

by higress-group in higress-group/higress

Deploy and configure Higress AI Gateway for OpenClaw integration.

Apache-2.0Auto-check passedAI & LLM Engineering

Install Higress Openclaw Integration

skills CLI
$ npx skills add higress-group/higress --skill higress-openclaw-integration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install higress-group/higress higress-openclaw-integration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/higress-group/higress.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/higress-openclaw-integration .claude/skills/higress-openclaw-integration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
higress-openclaw-integration
GitHub stars
9.5k
Token cost
~2.5k tokens
SKILL.md length
729 words
Files
7 (incl. scripts, references)
Skills in repo
11
Repo updated
First seen
Licence
Apache-2.0

At a glance

Deploy and configure Higress AI Gateway for OpenClaw integration.

  • Works in 3 steps: Collect Information from User → Deploy Gateway → Install OpenClaw Plugin
  • User wants to deploy Higress AI Gateway
  • SKILL.md covers Quick Start, Post-Deployment Management, Endpoints and Testing, plus 2 more sections
  • Runs Shell and TypeScript scripts from its folder; calls curl, claude and bash; reaches higress.ai

What it does

Higress Openclaw Integration is an agent skill from higress-group/higress. Deploy and configure Higress AI Gateway for OpenClaw integration. Use when: (1) User wants to deploy Higress AI Gateway, (2) User wants to configure OpenClaw to use more model providers, (3) User mentions 'higress', 'ai gateway', 'model gateway', 'AI网关', (4) User wants to set up model routing or auto-routing, (5) User needs to manage LLM provider API keys.

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts and reference files (for example `references/TROUBLESHOOTING.md`, `scripts/detect-region.sh` and `scripts/plugin/README.md`).

It sits in AI & LLM Engineering, covering Model routing and gateways. It works with Zhipu GLM and Mistral AI. The repository describes itself as: 🤖 AI Gateway | AI Native API Gateway. The licence is Apache-2.0.

When your agent uses it

  • User wants to deploy Higress AI Gateway
  • User wants to configure OpenClaw to use more model providers
  • User mentions higress
  • User wants to set up model routing

Example prompts

  • “higress”
  • “ai gateway”
  • “model gateway”
  • “/higress-openclaw-integration”

Requirements

  • Node.js
  • A Bash shell
  • Docker

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Collect Information from User
  2. Deploy Gateway
  3. Install OpenClaw Plugin

What it can do on your machine

Read from SKILL.md and the folder at commit c74d7e2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 5 files in scripts/ (Shell and TypeScript), which the agent can run.

    Shell commands in SKILL.md call:

    • curl
    • claude
    • bash
    • docker

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • higress.ai

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Higress Openclaw Integration loads about 2.5k tokens when it runs, and up to ~4k if it reads all its reference files. Until then it costs about 97 tokens; SKILL.md has 729 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~97
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from higress-group/higress at commit c74d7e2, republished under its Apache-2.0 licence (© higress-group). 729 words, ~2,490 tokens.

Download SKILL.mdSave it as .claude/skills/higress-openclaw-integration/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
higress-openclaw-integration
description
Deploy and configure Higress AI Gateway for OpenClaw integration. Use when: (1) User wants to deploy Higress AI Gateway, (2) User wants to configure OpenClaw to use more model providers, (3) User mentions 'higress', 'ai gateway', 'model gateway', 'AI网关', (4) User wants to set up model routing or auto-routing, (5) User needs to manage LLM provider API keys.

Higress AI Gateway Integration

Deploy Higress AI Gateway and configure OpenClaw to use it as a unified model provider.

Quick Start

Step 1: Collect Information from User

Ask the user for the following information upfront:

  1. Which LLM provider(s) to use? (at least one required)

    Commonly Used Providers:

    ProviderParameterNotes
    智谱 / z.ai--zhipuai-keyModels: glm-*, Code Plan mode enabled by default
    Claude Code--claude-code-keyRequires OAuth token from claude setup-token
    Moonshot (Kimi)--moonshot-keyModels: moonshot-, kimi-
    Minimax--minimax-keyModels: abab-*
    阿里云通义千问 (Dashscope)--dashscope-keyModels: qwen*
    OpenAI--openai-keyModels: gpt-, o1-, o3-*
    DeepSeek--deepseek-keyModels: deepseep-*
    Grok--grok-keyModels: grok-*

    Other Providers:

    ProviderParameterNotes
    Claude--claude-keyModels: claude-*
    Google Gemini--gemini-keyModels: gemini-*
    OpenRouter--openrouter-keySupports all models (catch-all)
    Groq--groq-keyFast inference
    Doubao (豆包)--doubao-keyModels: doubao-*
    Mistral--mistral-keyModels: mistral-*
    Baichuan (百川)--baichuan-keyModels: Baichuan*
    01.AI (Yi)--yi-keyModels: yi-*
    Stepfun (阶跃星辰)--stepfun-keyModels: step-*
    Cohere--cohere-keyModels: command*
    Fireworks AI--fireworks-key-
    Together AI--togetherai-key-
    GitHub Models--github-key-

    Cloud Providers (require additional config):

    • Azure OpenAI: --azure-key (requires service URL)
    • AWS Bedrock: --bedrock-key (requires region and access key)
    • Google Vertex AI: --vertex-key (requires project ID and region)

    Brand Name Display (z.ai / 智谱):

    • If user communicates in Chinese: display as "智谱"
    • If user communicates in English: display as "z.ai"
  2. Enable auto-routing? (recommended)

    • If yes: --auto-routing --auto-routing-default-model <model-name>
    • Auto-routing allows using model="higress/auto" to automatically route requests based on message content
  3. Custom ports? (optional, defaults: HTTP=8080, HTTPS=8443, Console=8001)

Step 2: Deploy Gateway

Auto-detect region for z.ai / 智谱 domain configuration:

When user selects z.ai / 智谱 provider, detect their region:

bash
# Run region detection script (scripts/detect-region.sh relative to skill directory)
REGION=$(bash scripts/detect-region.sh)
# Output: "china" or "international"

Based on detection result:

  • If REGION="china": use default domain open.bigmodel.cn, no extra parameter needed
  • If REGION="international": automatically add --zhipuai-domain api.z.ai to deployment command

After deployment (for international users): Notify user in English: "The z.ai endpoint domain has been set to api.z.ai. If you want to change it, let me know and I can update the configuration."

bash
# Create installation directory
mkdir -p higress-install
cd higress-install

# Download script (if not exists)
curl -fsSL https://higress.ai/ai-gateway/install.sh -o get-ai-gateway.sh
chmod +x get-ai-gateway.sh

# Deploy with user's configuration
# For z.ai / 智谱: always include --zhipuai-code-plan-mode
# For non-China users: include --zhipuai-domain api.z.ai
./get-ai-gateway.sh start --non-interactive \
  --<provider>-key <api-key> \
  [--auto-routing --auto-routing-default-model <model>]

z.ai / 智谱 Options:

OptionDescription
--zhipuai-code-plan-modeEnable Code Plan mode (enabled by default)
--zhipuai-domain <domain>Custom domain, default: open.bigmodel.cn (China), api.z.ai (international)

Example (China user):

bash
./get-ai-gateway.sh start --non-interactive \
  --zhipuai-key sk-xxx \
  --zhipuai-code-plan-mode \
  --auto-routing \
  --auto-routing-default-model glm-5

Example (International user):

bash
./get-ai-gateway.sh start --non-interactive \
  --zhipuai-key sk-xxx \
  --zhipuai-domain api.z.ai \
  --zhipuai-code-plan-mode \
  --auto-routing \
  --auto-routing-default-model glm-5
Step 3: Install OpenClaw Plugin

Install the Higress provider plugin for OpenClaw:

bash
# Copy plugin files (PLUGIN_SRC is relative to skill directory: scripts/plugin)
PLUGIN_SRC="scripts/plugin"
PLUGIN_DEST="$HOME/.openclaw/extensions/higress"

mkdir -p "$PLUGIN_DEST"
cp -r "$PLUGIN_SRC"/* "$PLUGIN_DEST/"

Tell user to run the following commands manually in their terminal (interactive commands, cannot be executed by AI agent):

bash
# Step 1: Enable the plugin
openclaw plugins enable higress

# Step 2: Configure provider (interactive - will prompt for Gateway URL, API Key, models, etc.)
openclaw models auth login --provider higress --set-default

# Step 3: Restart OpenClaw gateway to apply changes
openclaw gateway restart

The openclaw models auth login command will interactively prompt for:

  1. Gateway URL (default: http://localhost:8080)
  2. Console URL (default: http://localhost:8001)
  3. API Key (optional for local deployments)
  4. Model list (auto-detected or manually specified)
  5. Auto-routing default model (if using higress/auto)

After configuration and restart, Higress models are available in OpenClaw with higress/ prefix (e.g., higress/glm-5, higress/auto).

Future Configuration Updates (No Restart Needed)

After the initial setup, you can manage your configuration through conversation with OpenClaw:

  • Add New Providers: Add new LLM providers (e.g., DeepSeek, OpenAI, Claude) and their models dynamically.
  • Update API Keys: Update existing provider API keys without service restart.
  • Configure Auto-routing: If you've set up multiple models, ask OpenClaw to configure auto-routing rules. Requests will be intelligently routed based on your message content, using the most suitable model automatically.

All configuration changes are hot-loaded through Higress — no openclaw gateway restart required. Iterate on your model provider setup dynamically without service interruption!

Show full SKILL.md (201 more words)Show less

Post-Deployment Management

Add/Update API Keys (Hot-reload)
bash
./get-ai-gateway.sh config add --provider <provider> --key <api-key>
./get-ai-gateway.sh config list
./get-ai-gateway.sh config remove --provider <provider>

Provider aliases: dashscope/qwen, moonshot/kimi, zhipuai/zhipu

Update z.ai Domain (Hot-reload)

If user wants to change the z.ai domain after deployment:

bash
# Update domain configuration
./get-ai-gateway.sh config add --provider zhipuai --extra-config "zhipuDomain=api.z.ai"
# Or revert to China endpoint
./get-ai-gateway.sh config add --provider zhipuai --extra-config "zhipuDomain=open.bigmodel.cn"
Add Routing Rules (for auto-routing)
bash
# Add rule: route to specific model when message starts with trigger
./get-ai-gateway.sh route add --model <model> --trigger "keyword1|keyword2"

# Examples
./get-ai-gateway.sh route add --model glm-4-flash --trigger "quick|fast"
./get-ai-gateway.sh route add --model claude-opus-4 --trigger "think|complex"
./get-ai-gateway.sh route add --model deepseek-coder --trigger "code|debug"

# List/remove rules
./get-ai-gateway.sh route list
./get-ai-gateway.sh route remove --rule-id 0
Stop/Delete Gateway
bash
./get-ai-gateway.sh stop
./get-ai-gateway.sh delete

Endpoints

EndpointURL
Chat Completionshttp://localhost:8080/v1/chat/completions
Consolehttp://localhost:8001
Logs./higress-install/logs/access.log

Testing

bash
# Test with specific model
curl 'http://localhost:8080/v1/chat/completions' \
  -H 'Content-Type: application/json' \
  -d '{"model": "<model-name>", "messages": [{"role": "user", "content": "Hello"}]}'

# Test auto-routing (if enabled)
curl 'http://localhost:8080/v1/chat/completions' \
  -H 'Content-Type: application/json' \
  -d '{"model": "higress/auto", "messages": [{"role": "user", "content": "What is AI?"}]}'

Troubleshooting

IssueSolution
Container fails to startCheck docker logs higress-ai-gateway
Port already in useUse --http-port, --console-port to change ports
API key errorRun ./get-ai-gateway.sh config list to verify keys
Auto-routing not workingEnsure --auto-routing was set during deployment
Slow image downloadScript auto-selects nearest registry based on timezone

Important Notes

  1. Claude Code Mode: Requires OAuth token from claude setup-token command, not a regular API key
  2. z.ai Code Plan Mode: Enabled by default, uses /api/coding/paas/v4/chat/completions endpoint, optimized for coding tasks
  3. z.ai Domain Selection:
    • China users: open.bigmodel.cn (default)
    • International users: api.z.ai (auto-detected based on timezone)
    • Users can update domain anytime after deployment
  4. Auto-routing: Must be enabled during initial deployment (--auto-routing); routing rules can be added later
  5. OpenClaw Integration: The openclaw models auth login and openclaw gateway restart commands are interactive and must be run by the user manually in their terminal
  6. Hot-reload: API key changes take effect immediately; no container restart needed

© higress-group, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files (scripts, references) in .agents/skills/higress-openclaw-integration of higress-group/higress.

  • SKILL.md
  • references/TROUBLESHOOTING.md
  • scripts/detect-region.sh
  • scripts/plugin/README.md
  • scripts/plugin/index.ts
  • scripts/plugin/openclaw.plugin.json
  • scripts/plugin/package.json

Open the folder on GitHubat commit c74d7e2

Compare with similar skills

Higress Openclaw Integration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Higress Openclaw Integration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Higress Openclaw Integration this skillhigress-group/higress9.5k—~2.5kAutomated safety check: PassApache-2.0
Embeddings via 9Routerdecolua/9router31k—~604Automated safety check: PassMIT
Model Hierarchyzscole/model-hierarchy-skill346—~2.3kAutomated safety check: PassMIT
LLM Council on Fireworks AIdair-ai/dair-academy-plugins614—~5kAutomated safety check: NotesMIT
Model Routersundial-org/awesome-openclaw-skills663—~2.2kAutomated safety check: PassNone
Openrouter Multi Providerjeremylongshore/tons-of-skills-marketplace2.8k—~2.5kAutomated safety check: PassMIT

Similar skills

  • Embeddings via 9Router

    decolua/9router

    Generates vector embeddings through the 9Router /v1/embeddings endpoint, using models from providers such as OpenAI, Gemini, Mistral and Voyage for RAG and semantic search.

    31k GitHub stars~604 tokensUpdated 3 days ago
    AI & LLM EngineeringAuto-check passed
  • Model Hierarchy

    zscole/model-hierarchy-skill

    Cost-optimize AI agent operations by routing tasks to appropriate models based on complexity.

    346 GitHub stars~2.3k tokensUpdated 7 mo ago
    AI & LLM EngineeringAuto-check passed
  • LLM Council on Fireworks AI

    dair-ai/dair-academy-plugins

    Has several open-weight models answer a question, rank each other's anonymized answers, then lets a chairman model write the final response through Fireworks AI.

    614 GitHub stars~5k tokensUpdated 2 mo ago
    AI & LLM EngineeringAuto-check: notes
  • Model Router

    sundial-org/awesome-openclaw-skills

    A comprehensive AI model routing system that automatically selects the optimal model for any task.

    663 GitHub stars~2.2k tokensUpdated 7 mo ago
    AI & LLM EngineeringAuto-check passed
  • Openrouter Multi Provider

    jeremylongshore/tons-of-skills-marketplace

    Use multiple AI providers (OpenAI, Anthropic, Google, Meta) through OpenRouter's unified API.

    2.8k GitHub stars~2.5k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed
  • Awesome Free LLM APIs

    LeoYeAI/openclaw-master-skills

    Reference guide for permanent free-tier LLM APIs with rate limits, model lists, and OpenAI-compatible integration patterns.

    2.2k GitHub stars~4.1k tokensUpdated 2 mo ago
    AI & LLM EngineeringAuto-check passed

More from higress-group/higress

All 11 skills in this repo
  • Nginx To Higress Migration

    higress-group/higress

    Migrate from ingress-nginx to Higress in Kubernetes environments.

    9.5k GitHub stars~3.9k tokensUpdated 3 days ago
    Auto-check passed
  • Agent Session Monitor

    higress-group/higress

    Real-time agent conversation monitoring - monitors Higress access logs, aggregates conversations by session, tracks token usage.

    9.5k GitHub stars~3.3k tokensUpdated 3 days ago
    Auto-check passed
  • Higress Wasm Go Plugin

    higress-group/higress

    Develop Higress WASM plugins using Go 1.24+. An agent skill from higress-group/higress.

    9.5k GitHub stars~1.8k tokensUpdated 3 days ago
    Auto-check passed
  • Higress Auto Router

    higress-group/higress

    Configure automatic model routing using the get-ai-gateway.sh CLI tool for Higress AI Gateway.

    9.5k GitHub stars~954 tokensUpdated 3 days ago
    Auto-check passed
  • Higress Daily Report

    higress-group/higress

    生成 Higress 项目每日报告,追踪 issue/PR 动态,沉淀问题处理经验,驱动社区问题闭环。用于生成日报、跟进 issue、记录解决方案。

    9.5k GitHub stars~1.1k tokensUpdated 3 days ago
    Auto-check passed
  • Higress Update Envoy Gateway

    higress-group/higress

    Update Higress Envoy binary and gateway image dependencies for e2e validation.

    9.5k GitHub stars~1.2k tokensUpdated 3 days ago
    Auto-check passed

Questions about Higress Openclaw Integration

What does Higress Openclaw Integration do?

Deploy and configure Higress AI Gateway for OpenClaw integration. Higress Openclaw Integration is an agent skill from higress-group/higress. Deploy and configure Higress AI Gateway for OpenClaw integration.

When should I use Higress Openclaw Integration?

Higress Openclaw Integration fits situations like: user wants to deploy Higress AI Gateway; user wants to configure OpenClaw to use more model providers; user mentions higress; user wants to set up model routing.

How do I install Higress Openclaw Integration in Claude Code?

Run `npx skills add higress-group/higress --skill higress-openclaw-integration -a claude-code`. Or copy the skill folder (.agents/skills/higress-openclaw-integration in higress-group/higress) into .claude/skills/higress-openclaw-integration in your project. Claude Code loads it when a task matches its description.

How do I install Higress Openclaw Integration in Codex?

Run `npx skills add higress-group/higress --skill higress-openclaw-integration -a codex`. Or copy the skill folder (.agents/skills/higress-openclaw-integration in higress-group/higress) into .agents/skills/higress-openclaw-integration in your project. Codex loads it when a task matches its description.

Can I use Higress Openclaw Integration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add higress-group/higress --skill higress-openclaw-integration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/higress-openclaw-integration, .gemini/skills/higress-openclaw-integration, .github/skills/higress-openclaw-integration and .opencode/skills/higress-openclaw-integration in your project.

What does Higress Openclaw Integration need to run?

Going by SKILL.md and its folder, Higress Openclaw Integration needs a shell and TypeScript for the scripts in its folder and the command-line tools its instructions call (curl, claude, bash and docker). Our summary lists: Node.js; A Bash shell; Docker.

Does Higress Openclaw Integration access the network?

SKILL.md names 1 domain. In commands or code: higress.ai; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Higress Openclaw Integration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Higress Openclaw Integration use?

Higress Openclaw Integration is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Higress Openclaw Integration use?

About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.

What are the alternatives to Higress Openclaw Integration?

Skills that share tags, products or a category with Higress Openclaw Integration: Embeddings via 9Router (decolua/9router, 31k stars), Model Hierarchy (zscole/model-hierarchy-skill, 346 stars), LLM Council on Fireworks AI (dair-ai/dair-academy-plugins, 614 stars) and Model Router (sundial-org/awesome-openclaw-skills, 663 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Higress Openclaw Integration?

higress-group (a GitHub organization) maintains it in higress-group/higress, which has 9,516 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 8, 2026.

Source: higress-group/higress on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.