higress-openclaw-integration_skill

This skill helps you deploy Higress AI Gateway and configure OpenClaw to route to multiple model providers for seamless AI powered APIs.

Go

7.5k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill alibaba/higress --skill higress-openclaw-integration

SKILL.md9.8 KB

Overview

This skill deploys and configures the Higress AI Gateway and integrates it with OpenClaw as a unified model provider. It guides collection of provider keys, optional auto-routing setup, deployment commands, and the OpenClaw plugin installation steps. Use it to centralize multiple LLM providers behind a single gateway and enable hot-reloadable provider and routing configuration.

How this skill works

The skill prepares a non-interactive Higress installation command tailored to the LLM providers and region (for z.ai). It installs a Higress provider plugin into OpenClaw and instructs the user how to enable and authenticate the provider in OpenClaw. Post-deployment, provider keys, domains, and routing rules can be added or updated through Higress hot-reload commands without restarting services.

When to use it

You want to deploy Higress AI Gateway as a model gateway for multiple providers
You need OpenClaw to access models from many LLM providers under a single prefix
You want automatic routing of requests to the best model based on message content
You need to centrally manage LLM provider API keys and update them live
You mention terms like "higress", "ai gateway", or "model gateway"

Best practices

Collect provider API keys and required extra config (region, service URLs) before deployment
Enable auto-routing during initial deployment if you plan to use higress/auto
For z.ai users, allow region detection so the correct domain (api.z.ai or open.bigmodel.cn) is set
Install the OpenClaw plugin files locally and run interactive OpenClaw auth commands yourself
Use hot-reload commands to add/update keys or change domains instead of restarting the gateway

Example use cases

Deploy Higress locally to expose OpenAI, z.ai, and other providers to OpenClaw under higress/* model names
Enable auto-routing so user messages are routed to the most suitable model automatically
Add a new provider API key after launch using higress config add without downtime
Set up routing rules that send code-related prompts to a coding-optimized model
Switch z.ai domain for international users to api.z.ai via hot-reload

FAQ

No. API key and provider changes are hot-reloaded through Higress; no restart is required.

How do I enable auto-routing?

Add --auto-routing and --auto-routing-default-model during initial ./get-ai-gateway.sh start; routing rules can be added later with ./get-ai-gateway.sh route add.

What must I run interactively on my terminal?

You must run OpenClaw commands to enable the plugin and perform provider auth (openclaw plugins enable higress, openclaw models auth login, and openclaw gateway restart as needed).