openclaw-setup

What This Skill Does

The openclaw-setup skill serves as an orchestration layer for Claude Code, automating the end-to-end deployment of a personal AI assistant. It manages the complex lifecycle of infrastructure provisioning, environment hardening, and application installation. By standardizing the setup process, it ensures that your OpenClaw agent is deployed with best practices, including secure SSH configuration, proper API integration, and persistent storage management. It acts as a concierge, prompting you for necessary credentials and handling the technical heavy lifting across your AWS environment.

Installation

To begin, ensure you have Claude Code installed and authenticated. Simply provide the agent with the command: clawhub install openclaw/skills/skills/j540/openclaw-setup. Once installed, invoke the agent and state your intent to setup OpenClaw. The agent will guide you through the two-phase process: gathering your API keys (Anthropic, Groq, OpenAI) and configuring your cloud resources. The setup phase involves provisioning an EC2 instance, configuring security groups, and initializing the OpenClaw codebase on the server.

Use Cases

This skill is perfect for users who want to transition from local testing to a dedicated, always-on AI assistant. It is ideal for those who need a 24/7 autonomous agent for managing daily schedules, processing emails, summarizing documents, or interacting with Telegram via custom automated workflows. Whether you are a busy professional needing an automated secretary or a developer wanting a sandbox for AI-driven automation, this skill simplifies the transition from concept to cloud.

Example Prompts

1. "I'm ready to start the OpenClaw setup; walk me through the requirements and let's get the EC2 instance provisioned."
2. "I have my AWS credentials and Anthropic key ready, can we proceed to Phase 2 of the OpenClaw installation?"
3. "Help me configure my Telegram bot settings and link my Google Calendar to the OpenClaw instance we just deployed."

Tips & Limitations

• Security: Always store your .pem files and API keys in a secure password manager. Never commit them to version control.
• Cost Awareness: Keep an eye on your AWS billing dashboard. While the instance is often free-tier eligible, API calls (especially to Claude Opus) can accrue costs based on usage volume.
• Connectivity: Ensure your local machine has a stable internet connection during the initial deployment phase to prevent SSH timeouts during environment setup.