← Back to Skills Marketplace
llcsamih

Self-Host Deployer

by Samih Mansour · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
87
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install self-host-deployer
Description
Deploy self-hosted applications to any VPS with Docker Compose. Catalog of 18 apps with production-ready configs, Nginx reverse proxy, SSL via Certbot, autom...
Usage Guidance
This skill does what it says (deploy apps) but requires giving SSH access and running many remote commands — only proceed if you trust the skill's author and you understand the commands it will run. Before using: (1) ask the publisher for a homepage/source and verify GitHub repo URLs are official; (2) prefer creating an unprivileged/deploy user or use an ephemeral SSH key rather than providing root; (3) request the generated docker-compose.yml and .env files for manual review before applying them; (4) snapshot or backup the VPS (or test on a throwaway VM); (5) verify any repos/third-party downloads the instructions use and avoid running npm/global installs blindly; (6) if you want the same automation but less risk, ask the skill to produce step-by-step commands you can run manually instead of giving credentials/upfront remote access.
Capability Analysis
Type: OpenClaw Skill Name: self-host-deployer Version: 1.0.0 The skill bundle is a comprehensive deployment tool for self-hosted applications that requires high-privilege SSH credentials and performs remote shell execution on a VPS. While the logic is aligned with its stated purpose, it exhibits high-risk behaviors including the use of a 'curl|bash' pipe for the Coolify installer and the automated modification of system-level configurations like Nginx and Crontab (SKILL.md). The collection of sensitive credentials and the ability to execute arbitrary commands on remote infrastructure represent a significant security risk if the agent is subverted.
Capability Assessment
Purpose & Capability
The skill's name and description (deploy self-hosted apps with Docker Compose, Nginx, Certbot, backups) align with the runtime instructions. However the registry metadata claims no required binaries or credentials while the SKILL.md clearly expects many host tools (git, docker/docker-compose, openssl, npm/node, certbot, curl, ssh) and root/sudo SSH access. That mismatch between declared requirements and actual steps is inconsistent.
Instruction Scope
The instructions explicitly ask the user for VPS IP and SSH credentials (root or sudo), instruct cloning repos, editing and writing .env files under /opt, generating secrets, installing npm packages and running commands remotely (e.g., running docker-compose, certbot). These are within the stated deployment purpose but are high-risk operations because they give the agent the ability to run arbitrary shell commands on your server and modify system-wide state.
Install Mechanism
There is no install spec (instruction-only), which minimizes what is written to the local agent. However, the skill assumes many binaries and remote installs on the target VPS. The metadata omits required binaries while the instructions rely on external tools and clones from GitHub — this inconsistency is a red flag because it hides the true operational requirements.
Credentials
The skill requests SSH credentials and a domain/email for Certbot — these are legitimately needed to deploy to a VPS, but they are sensitive. The skill does not request unrelated cloud/API keys, which is good. Still, asking for root-level SSH access gives broad control over the target machine and should only be granted with caution and explicit user understanding.
Persistence & Privilege
The skill does not set always:true and is user-invocable only. It will instruct changes on the VPS (writing stacks under /opt, configuring proxy, SSL, backups) which are normal for deployment tools, but these are system-wide changes requiring privileged access — verify commands before running. Autonomous invocation plus ability to collect credentials increases risk if you enable the agent to act without supervision.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install self-host-deployer
  3. After installation, invoke the skill by name or use /self-host-deployer
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Version 1.0.0 - Initial release of "self-host-deployer" skill. - Guides users to deploy 18+ production-ready self-hosted applications on any VPS using Docker Compose, with automated setup for Nginx, SSL (Certbot), backups, resource limits, and health checks. - Includes a detailed application catalog with minimum requirements and key app details. - Interactive workflow: helps users select an app, gathers necessary VPS and domain info, and generates secure, app-specific Docker Compose configurations. - Supports privacy-friendly, open-source tools as alternatives to mainstream SaaS offerings.
Metadata
Slug self-host-deployer
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Self-Host Deployer?

Deploy self-hosted applications to any VPS with Docker Compose. Catalog of 18 apps with production-ready configs, Nginx reverse proxy, SSL via Certbot, autom... It is an AI Agent Skill for Claude Code / OpenClaw, with 87 downloads so far.

How do I install Self-Host Deployer?

Run "/install self-host-deployer" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Self-Host Deployer free?

Yes, Self-Host Deployer is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Self-Host Deployer support?

Self-Host Deployer is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Self-Host Deployer?

It is built and maintained by Samih Mansour (@llcsamih); the current version is v1.0.0.

💬 Comments