solo-deploy

What This Skill Does

The solo-deploy skill acts as the intelligent orchestration engine for transitioning code from a local development environment to live production infrastructure. It functions as the crucial second step in the OpenClaw development lifecycle, picking up exactly where the /build skill leaves off.

Upon activation, the skill performs a deep-context analysis of your project by scanning stack template YAML files (templates/stacks/*.yaml) to understand specific infrastructure requirements, environment configurations, and deployment patterns. It dynamically probes your local environment to identify installed CLI tools—such as Vercel, Wrangler, Supabase, Fly, or SST—ensuring that it utilizes your local toolchain rather than falling back to inefficient or generic commands.

Beyond simple execution, solo-deploy bridges the gap between generic stack configurations and project-specific requirements by parsing docs/plan/*/plan.md. If your active development plan dictates specific deployment sequences or specialized infrastructure tasks, the skill incorporates these as primary instructions. Finally, it validates the deployment to ensure the live environment reflects the desired state, providing peace of mind through a verified hand-off.

Installation

To add this skill to your OpenClaw agent, execute the following command in your terminal:

clawhub install openclaw/skills/skills/fortunto2/solo-deploy

Use Cases

• Automated Production Pushes: When a feature set is complete and needs to be moved to the live hosting environment.
• Environment Syncing: Setting up production database instances or cloud environment variables as specified in the project stack files.
• CI/CD Orchestration: Executing deployment sequences for complex, multi-tier architectures that require coordinated pushes across frontend and backend services.
• Infrastructure Verification: Ensuring that the newly deployed code is live, healthy, and reachable after the automated push.

Example Prompts

1. "The build phase is finished, please go ahead and deploy it to our production environment."
2. "Everything is ready for launch; push the code to Vercel using the standard deployment procedure."
3. "Set up the staging hosting environment and deploy the current branch following the infrastructure plan."

Tips & Limitations

• Dependency Order: Always wait for the /build skill to complete. If the project state indicates the build stage is incomplete, the skill will issue a warning to prevent deployment of broken artifacts.
• Tooling Awareness: The skill is designed to prioritize native CLI tools found on your machine. Ensure your PATH is configured correctly so the skill can detect your installed utilities (like fly or gh).
• Plan Priority: When in doubt, the skill prioritizes custom deployment phases found within your active plan.md. Keep these documents updated to reflect any deviations from standard deployment patterns.