openclaw/skills/openclaw-layer/SKILL.md
OpenClaw AI gateway service on port 18789 via npm with persistent data. Use when working with OpenClaw, AI gateway configuration, or model routing.
npx skillsauth add overthinkos/overthink-plugins openclaw-layerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Property | Value |
|----------|-------|
| Dependencies | nodejs, socat, supervisord |
| Ports | 18789 |
| Port relay | 18789 (eth0 -> loopback) |
| Volumes | data -> ~/.openclaw |
| Aliases | openclaw -> openclaw |
| Service | openclaw (supervisord) |
| Install files | package.json |
| Variable | Value |
|----------|-------|
| NODE_ENV | production |
# charly.yml
openclaw:
candy:
- openclaw
charly alias install openclaw # install host 'openclaw' command
openclaw config # uses the alias
/charly-openclaw:openclaw/charly-openclaw:openclaw-fullThe gateway binds to 127.0.0.1:18789 (loopback only). A socat relay forwards from the container's network interface to loopback. This avoids OpenClaw's allowedOrigins requirement for the Control UI — all connections appear as loopback to the gateway.
Same pattern as the chrome candy (CDP on port 9222).
/charly-coder:nodejs -- Node.js runtime dependency/charly-infrastructure:socat -- port relay dependency (eth0 -> loopback)/charly-infrastructure:supervisord -- process manager dependency/charly-ollama:ollama -- optional local LLM backendUse when the user asks about:
openclaw host alias/charly-image:layer — candy authoring reference (charly.yml schema, task verbs, service declarations)/charly-check:check — declarative testing (check: block, charly check box, charly check live)tools
Use when authoring or modifying a charly PLUGIN — a candy with a `plugin:` block that contributes Providers (verbs/kinds/deploy-targets/steps/builders/commands), its own CUE schema, builtin (compiled-in) or external (out-of-tree git repo). Covers the unified Provider model, the per-plugin CUE-schema contract (single source → Go params for dev + schema-over-Describe RPC for runtime), the SDK, and the loader.
tools
The CUE data-validation / configuration CLI (cue), pinned to v0.16.1. Use when working with the cue candy, installing the cue binary into a box or onto a target:local dev host, or running the offline schema-vendoring pipeline that feeds charly's egress validation.
tools
CUE EGRESS validation — validating (and, where it adds value, generating) the config files charly WRITES to a system BEFORE the bytes hit disk. MUST be invoked before working on charly/egress.go, the vendored schemas under candy/plugin-egress/egress-schemas/vendor/, the ValidateEgress / registerVendoredEgressKind path, the offline `task cue:vendor` pipeline, or adding an egress schema for any written artifact (cloud-init, k8s manifests, traefik routes, runtime config, install ledger, systemd/quadlet units, ssh_config, libvirt XML).
tools
Kubernetes cluster-probe declarative check verb — the `kube:` check verb (nodes, pods, ingress, storage class, addon health, apply/delete, and arbitrary resource GETs) served out-of-process by the candy/plugin-kube plugin (vendored client-go; no external kubectl required).