Deploy Kit

What This Skill Does

The Deploy Kit, developed by hugosbl, acts as an intelligent abstraction layer for web deployment operations. It allows OpenClaw users to interface seamlessly with industry-standard deployment platforms—Vercel, Railway, and Supabase—directly from their CLI environments. The skill automates the detection of frameworks and build configurations, ensuring that whether a user is deploying a static Next.js frontend, a dynamic Python backend, or a complex full-stack application with database dependencies, the deployment path is optimized. By managing CLI requirements and providing structured commands for environment variables and domain configuration, it removes the friction typically associated with manual cloud infrastructure setup.

Installation

To add this skill to your OpenClaw agent, execute the following command in your terminal or within the agent's command interface: clawhub install openclaw/skills/skills/hugosbl/deploy-kit. Ensure you have the necessary CLIs installed globally on your machine (Vercel CLI, Railway CLI, and Supabase CLI) for full feature availability. The tool includes a pre-flight check functionality to help you identify missing dependencies before attempting a deployment.

Use Cases

This skill is ideal for developers who want to streamline their CI/CD workflow without leaving the terminal. Use it when you need to initialize a project deployment on Vercel, move a backend service to Railway, or synchronize your Supabase database schema. It is particularly powerful when working on multi-service applications that require coordinated environment variable injection across different hosting providers. It serves as a central orchestrator for project detection, platform recommendation, and the final execution of deployment commands.

Example Prompts

1. "I just finished my Next.js project in the current directory. Can you detect the framework and recommend the best way to deploy it?"
2. "I need to deploy my Flask backend to Railway and set the DATABASE_URL environment variable. Can you handle this for me?"
3. "Check if I have the required CLIs installed to push my Supabase migrations, then deploy my edge functions."

Tips & Limitations

• Safety First: Always review the detected framework and the target deployment platform before confirming a deployment. The tool intentionally requires explicit user confirmation to prevent accidental overwrites or misconfigurations in production environments.
• Environment Variables: Always audit your .env or .env.local files before running the deployment commands, as these are not automatically sanitized.
• Platform Specifics: The tool leverages native platform CLIs, meaning you must be authenticated with each provider (e.g., via vercel login or railway login) prior to using the skill. If a deployment fails, use the 'logs' commands provided by the skill to diagnose the issue in the target environment.