القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| 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.agentteams.io
Example: worker alice exposing port 8080 → worker-alice-8080-local.agentteams.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
agentteams-worker-{name}) automatically within agentteams-netexpose list and re-applyAnalyze current OpenClaw setup and generate a migration package (ZIP) for importing into HiClaw as a managed Worker
Use before direct filesync calls, reading non-task shared files, pushing mid-task progress, or troubleshooting missing shared files. Do not use for normal task acceptance or submission; taskflow ack_task and submit_task handle lifecycle sync internally.
Discover and install agent skills from the open ecosystem. Use when you encounter an unfamiliar domain, framework, or workflow that you lack specialized knowledge about, or when your coordinator suggests searching for skills before starting a task.
Use only when you need to look up team topology, worker phase, runtime state, or identity that is NOT available from the current message context. Do not use for standard task flows — the coordinator is the message sender, and the task room is in meta.json.room_id.
Sync files with centralized storage. Use when your coordinator or another Worker notifies you of file updates (config changes, task files, shared data, collaboration artifacts).
Discover and install agent skills from the open ecosystem. Use when you encounter an unfamiliar domain, framework, or workflow that you lack specialized knowledge about, or when your coordinator suggests searching for skills before starting a task.