Menu
Expose worker HTTP services via Higress gateway. Use when admin asks to publish a worker's web app or API to make it externally accessible.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when a QwenPaw-backed Worker needs to decide whether to do work directly, use native subagents for internal parallelism, or create a temporary QwenPaw agent with a custom AGENTS.md and skills.
Use when admin requests creating a team, importing a team, managing team composition, adding/removing workers from a team, or delegating tasks to a Team Leader.
Use when admin requests hand-creating or resetting a Worker, starting/stopping a Worker, managing Worker skills, enabling peer mentions, or opening a QwenPaw console. Use hiclaw-find-worker only as a helper for Nacos-backed market import or when task assignment needs you to discover a suitable Worker.
Discover and call MCP Server tools via the mcporter CLI. Use when your coordinator notifies you about new MCP tools, or when you need to call external APIs. Includes workflow for generating skill documentation for new MCP servers.
Use when TEAMS.md Communication Contract needs detailed routing: Channel / Room Selection Protocol, Requester Report Delivery Protocol, or Message Tool Protocol. It resolves current session vs Team Room vs assignment room vs requester reply_route vs external channel, and explains when to use the message MCP tool. Do not use it to choose Quick Task or Project Work, create rooms, delegate tasks, check results, or accept project state.
Use for TeamHarness shared workspace paths, explicit filesync operations, and shared project/task artifact boundaries.
| name | service-publishing |
| description | Expose worker HTTP services via Higress gateway. Use when admin asks to publish a worker's web app or API to make it externally accessible. |
Expose HTTP services running inside worker containers to the outside world via the Higress gateway. Each exposed port gets an auto-generated domain name.
Add expose to a Worker's spec to publish container ports. The controller automatically creates the Higress domain, service source, and route.
Auto-generated domain pattern:
worker-{name}-{port}-local.hiclaw.io
Example: worker alice exposing port 8080 → worker-alice-8080-local.hiclaw.io
# Expose port 8080 for worker alice
hiclaw apply worker --name alice --model qwen3.5-plus --expose 8080
# Expose multiple ports
hiclaw apply worker --name alice --model qwen3.5-plus --expose 8080,3000
# Check exposed ports
hiclaw get worker alice
# Look for status.exposedPorts in the output
# Remove exposed ports (update without --expose)
hiclaw apply worker --name alice --model qwen3.5-plus
apiVersion: agentteams.io/v1beta1
kind: Worker
metadata:
name: alice
spec:
model: qwen3.5-plus
expose:
- port: 8080
- port: 3000
Apply with:
hiclaw apply -f worker.yaml
Team workers also support expose:
apiVersion: agentteams.io/v1beta1
kind: Team
metadata:
name: dev-team
spec:
leader:
name: lead
model: qwen3.5-plus
workers:
- name: backend
model: qwen3.5-plus
expose:
- port: 8080
- name: frontend
model: qwen3.5-plus
expose:
- port: 3000
hiclaw-worker-{name}) automatically within hiclaw-netexpose list and re-apply