From easypanel
Use when the user wants to deploy a project, app, or service to EasyPanel. Triggers on: 'deploy to EasyPanel', 'set up hosting', 'push this to my server', 'deploy this app', 'host this on EasyPanel'.
How this skill is triggered — by the user, by Claude, or both
Slash command
/easypanel:easypanel-deployThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Guide the user through deploying to their EasyPanel instance using the ep_* MCP tools.
Guide the user through deploying to their EasyPanel instance using the ep_* MCP tools.
Check existing projects: Use ep_list_projects (with includeServices=true) to see what's already deployed. This prevents creating duplicate projects.
Determine service type: Ask the user or infer from the codebase:
ep_create_app)ep_create_wordpress)ep_create_box)docker-compose.yml present -> Compose service (ep_manage_compose)Create or select project:
ep_create_project (name must be lowercase, alphanumeric, dashes, underscores)Configure source: Based on how the code should get to EasyPanel:
sourceGithub with repo URL and branchsourceImage with image name and tagsourceDockerfile with path to DockerfilesourceGit with repo URLSet up domains: Configure domain routing with ep_configure_app using the deploy setting. Default to HTTPS.
Set environment variables: If the project needs env vars, use ep_configure_app with env setting or ep_update_project_env for project-level vars.
Deploy: Trigger with ep_deploy_app (use forceRebuild=true if redeploying).
Verify:
ep_inspect_appep_system_stats if neededep_github_deploy for repo-based projectsep_service_stats to verify the service is running after deploymentep_create_wordpress with initialize=true for a ready-to-use sitenpx claudepluginhub dtsoden/easypanel-claude-plugin --plugin easypanelDeploys apps to Render by analyzing codebases, generating render.yaml blueprints, and providing dashboard deeplinks. For Git-backed services, Docker images, databases, and cron jobs.
Automate self-hosting of open-source apps on cloud infrastructure the user owns. Use when the user asks to "self-host", "deploy to my own cloud", "install X on AWS/Lightsail/Hetzner/DigitalOcean", "set up my own Ghost blog / Mastodon / WordPress / Nextcloud", or names a combination of an open-source app and a cloud provider. Walks the user through provisioning, DNS, TLS, outbound email (SMTP), and inbound email, in phases that are resumable across sessions via a state file at `~/.open-forge/deployments/<name>.yaml`. Supported today: Ghost on AWS Lightsail (Bitnami). More projects and infras added under `references/projects/` and `references/infra/`.
Generates deployment configurations for hosting providers like Vercel, Railway, AWS, covering env vars, domains, SSL, strategies, rollback plans, and health checks. Useful for production deploys.