ClawBot installed via Hostinger Catalog (Docker) — how are ClawHub skills supposed to be installed?
installed ClawBot / OpenClaw via the Hostinger VPS catalog, which deploys the official Docker image. Core setup works as expected:
Gateway is running
Hatch UI is accessible
Telegram channel is configured and responding
I’m trying to understand the supported way to install and use ClawHub skills (https://www.clawhub.com/skills
) in this deployment.
In the catalog/Docker setup:
There is no clawdbot or openclaw CLI available inside the container
Installing CLI tools on the host VPS does not affect the running container
Hatch UI does not expose skill installation or capability configuration
Raw config rejects skill-related keys (e.g. search, capabilities)
This makes it unclear how skills are intended to be added when using the catalog image.
Setup details:
Hosting: Hostinger VPS
OS: Ubuntu
Install method: Hostinger catalog (Docker)
Image: ghcr.io/openclaw/openclaw:main
Channels: Telegram
Question:
What is the recommended / supported workflow for adding ClawHub skills in a Docker-based catalog install?
Specifically:
Should skills be added via a custom Docker image?
Via a mounted skills volume?
Or is there another intended mechanism?
I want to make sure I’m following the correct architecture rather than hacking around limitations.
Gateway is running
Hatch UI is accessible
Telegram channel is configured and responding
I’m trying to understand the supported way to install and use ClawHub skills (https://www.clawhub.com/skills
) in this deployment.
In the catalog/Docker setup:
There is no clawdbot or openclaw CLI available inside the container
Installing CLI tools on the host VPS does not affect the running container
Hatch UI does not expose skill installation or capability configuration
Raw config rejects skill-related keys (e.g. search, capabilities)
This makes it unclear how skills are intended to be added when using the catalog image.
Setup details:
Hosting: Hostinger VPS
OS: Ubuntu
Install method: Hostinger catalog (Docker)
Image: ghcr.io/openclaw/openclaw:main
Channels: Telegram
Question:
What is the recommended / supported workflow for adding ClawHub skills in a Docker-based catalog install?
Specifically:
Should skills be added via a custom Docker image?
Via a mounted skills volume?
Or is there another intended mechanism?
I want to make sure I’m following the correct architecture rather than hacking around limitations.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Similar Threads
Was this page helpful?
