Cluster Gateway

v1.0.0

Verwaltet das OpenClaw Cluster Gateway als zentralen Hub zur Koordination, Task-Verteilung und Kommunikation zwischen Sub-Agenten im Cluster.

⭐ 0· 57·1 current·1 all-time

by@kikikari

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for kikikari/cluster-gateway.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Cluster Gateway" (kikikari/cluster-gateway) from ClawHub.
Skill page: https://clawhub.ai/kikikari/cluster-gateway
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install cluster-gateway

ClawHub CLI

Package manager switcher

npx clawhub@latest install cluster-gateway

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Suspicious

medium confidence

ℹ

Purpose & Capability

The SKILL.md clearly expects use of an 'openclaw' CLI (commands like `openclaw cluster gateway ...`) and refers to cluster configuration files and other node skills. However, the registry metadata lists no required binaries or primary credential. The omission of the required CLI and any network/credentials declarations is inconsistent with the stated purpose.

ℹ

Instruction Scope

Runtime instructions are narrowly scoped to CLI operations and a local JSON config example; they do not explicitly instruct reading unrelated system files or exfiltrating data. However, the document lists messaging providers (Slack/SMTP/etc.) as open blockers — integrating those would normally require credentials and endpoints, which are not specified here.

✓

Install Mechanism

No install spec and no code files are present, so nothing will be written to disk by the skill itself. This is the lowest-risk install pattern for an instruction-only skill.

Credentials

The skill requests no environment variables or credentials, yet it references external messaging providers (Slack/SMTP/GMX/others) that normally require tokens/credentials. That mismatch is disproportionate: either the skill is incomplete, or it will expect secrets at runtime but doesn't declare them.

✓

Persistence & Privilege

always is false and model invocation is allowed (platform default). The skill does not request elevated persistence or modifications to other skills' configs.

What to consider before installing

Before installing, verify the following: (1) confirm whether the 'openclaw' CLI is available on the agent host — the skill's commands depend on it but it is not declared as a required binary; (2) ask the author/source for a homepage or repo to review full behavior and for clarity about required credentials; (3) if you plan to enable messaging (Slack/SMTP/etc.), expect the skill to need tokens/credentials — only provide scoped, least-privilege credentials and preferably test in an isolated environment; (4) check that the node host addresses and ports in the config will only target internal, trusted network endpoints (avoid exposing private credentials to unknown hosts); (5) be cautious granting this skill network access or secrets until the dependency/credential gaps are resolved.

Like a lobster shell, security has layers — review code before you run it.

clustervk972k72m5c9ppzhjnevdyrsf7n8522m7gatewayvk972k72m5c9ppzhjnevdyrsf7n8522m7latestvk972k72m5c9ppzhjnevdyrsf7n8522m7relayvk972k72m5c9ppzhjnevdyrsf7n8522m7

57downloads

0stars

1versions

Updated 1w ago

v1.0.0

MIT-0

Cluster Gateway Node Skill

Status: 🚧 Vorbereitend - Wartet auf Messaging-Schnittstelle

Zweck

Verwaltet das OpenClaw Gateway als zentraler Hub für Sub-Agent-Kommunikation, Task-Verteilung und Cluster-Koordination.

Verwendung

# Gateway-Status prüfen
openclaw cluster gateway status

# Sub-Agent auf Node deployen
openclaw cluster gateway deploy --node <node-id> --agent <agent-type>

# Task an Worker Node senden
openclaw cluster gateway task --target <node-id> --command "<task>"

# Relay Node konfigurieren
openclaw cluster gateway relay --enable --node <node-id>

Architektur

┌─────────────────────────────────────┐
│         CLUSTER GATEWAY              │
│        (Node 1 - Haupt-Hub)          │
├─────────────────────────────────────┤
│  • Task Queue                         │
│  • Node Registry                      │
│  • Sub-Agent Orchestration            │
│  • Resource Scheduler                 │
│  • Messaging Router (zukünftig)       │
└──────────────┬──────────────────────┘
               │
    ┌──────────┼──────────┐
    │          │          │
┌───▼───┐  ┌──▼───┐  ┌───▼──┐
│ Node 2│  │Node 3│  │Node 4│
│Worker │  │Relay │  │Worker│
└───────┘  └──────┘  └──────┘

Node-Typen

Typ	Funktion	Beispiel
`gateway`	Zentraler Hub	Node 1
`worker`	Task-Ausführung	Node 2, Node 4
`relay`	Weiterleitung/Proxy	Node 3
`storage`	Datenspeicherung	Node 5

Konfiguration

// cluster-gateway.config.json
{
  "gateway": {
    "id": "node-1",
    "role": "hub",
    "bind": "0.0.0.0",
    "port": 18789
  },
  "nodes": [
    {"id": "node-2", "role": "worker", "host": "10.10.0.2"},
    {"id": "node-3", "role": "relay", "host": "10.10.0.3"},
    {"id": "node-4", "role": "worker", "host": "10.10.0.4"}
  ],
  "messaging": {
    "enabled": false,
    "provider": "pending"
  }
}