Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Claw Service Hub
v0.1.0OpenClaw 服务市场核心 - 服务注册、发现与调用，支持 Provider 注册服务、Consumer 发现服务、WebSocket 隧道调用、Key 授权机制
⭐ 1· 86·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The skill's description claims a full 'core' Hub (registration, discovery, WebSocket tunneling, storage, authorization, negotiation, load balancing). However the bundle only contains a CLI client (cli.py) and no server implementation (the start command imports server.main.HubServer which is not included). Required env vars include STORAGE_PATH and HUB_HOST but those are not read/used by the provided CLI. This mismatch suggests the provided files are incomplete or the skill metadata overstates capability.
Instruction Scope
SKILL.md instructs users to 'pip install -e .' and to start the Hub with python -m claw_service_hub.cli (implying the package includes a server). In practice the CLI will try to import server.main which is missing and will fail to start a hub. The CLI uses network operations (WebSocket and HTTP requests) to arbitrary hosts; these are expected for a hub client but you should not run it against untrusted endpoints. The docs declare env vars (HUB_PORT, HUB_HOST, STORAGE_PATH) but the CLI sets HUB_PORT/HUB_HTTP_PORT and does not read STORAGE_PATH, so the runtime instructions and code disagree.
Install Mechanism
There is no explicit install spec in the registry metadata (instruction-only skill). SKILL.md suggests 'pip install -e .', but the bundle does not include package metadata files (setup.py/pyproject.toml not shown here). The code imports third-party libs (aiohttp, websockets, click) that would need to be installed; lack of an explicit dependency spec is inconvenient but not itself high risk.
Credentials
Required env vars listed are HUB_PORT, HUB_HOST, STORAGE_PATH. The CLI sets HUB_PORT/HUB_HTTP_PORT defaults but does not read STORAGE_PATH anywhere; HUB_HOST is declared but not used as an environment variable by the code. No credentials are required. Requesting STORAGE_PATH (a database path) is disproportionate given the provided files don't implement storage. This misalignment could be accidental but is unexpected.
Persistence & Privilege
The skill is not marked always:true and does not request elevated system-wide privileges. It does modify process environment variables at runtime (os.environ.setdefault) but does not persist changes beyond the process or modify other skills. Autonomous invocation is allowed by default (no disable-model-invocation), which is normal for skills.
What to consider before installing
This package appears incomplete or inconsistent: the README and metadata describe a full Hub server but the bundle only contains a CLI that expects a server module (server.main) which is not present. Before installing or running: (1) inspect or obtain the missing server implementation and package metadata (setup.py/pyproject) so dependencies and runtime behavior are clear; (2) do not set or expose sensitive paths/credentials (e.g., STORAGE_PATH pointing at production data) until you confirm storage code and access patterns; (3) be aware the CLI makes network calls (WebSocket/HTTP) to hosts you specify — test in an isolated environment and avoid connecting to untrusted endpoints; (4) confirm required Python dependencies (aiohttp, websockets, click) and review their versions; (5) if the author can provide the missing server.main or clarify why env vars are declared but unused, re-evaluate. My confidence is high because the missing server module and unused env vars are concrete, reproducible inconsistencies.Like a lobster shell, security has layers — review code before you run it.
latestvk971wcchhe39qayr1z0eq9hp5184gkd5
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Binspython3
EnvHUB_PORT, HUB_HOST, STORAGE_PATH