From upcloud
Interactive onboarding wizard for UpCloud. Guides the user from zero to a fully provisioned and deployable project through a structured conversation: discovers requirements, recommends architecture, shows a plan for approval, provisions infrastructure, generates standalone management scripts, and provides an onboarding checklist. Use this skill when the user wants to start a new project on UpCloud, is new to the platform, says "set up everything from scratch", "I'm starting fresh", "walk me through setting up UpCloud", or wants a guided experience rather than jumping straight into provisioning.
How this skill is triggered — by the user, by Claude, or both
Slash command
/upcloud:upcloud-startThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Guides a user from zero to a fully deployed project on UpCloud through a structured conversation. This wraps `/upcloud:setup` with a discovery phase, approval step, and script generation.
Guides a user from zero to a fully deployed project on UpCloud through a structured conversation. This wraps /upcloud:setup with a discovery phase, approval step, and script generation.
Phase 1 Phase 2 Phase 3 Phase 4 Phase 5 Phase 6
DISCOVER → RECOMMEND → SHOW PLAN → PROVISION → GENERATE SCRIPTS → ONBOARD
questions architecture upctl execute deploy.sh what's
about the + cost commands the plan migrate.sh next
project estimate for review rollback.sh checklist
Ask the user these questions one group at a time. Don't dump all questions at once — have a conversation. Adapt follow-up questions based on answers.
Ask:
Based on the app type, ask relevant questions:
fi-hel1)
After each group, summarize what you've learned so far. This builds confidence that you understood correctly.
Based on discovery answers, build and present this table:
┌─────────────────────────────────────────────────────────────┐
│ Recommended Architecture for {project_name} │
├──────────────────┬──────────────────────────────────────────┤
│ Server │ {plan} in {zone} │
│ Database │ PostgreSQL ({db_plan}) │
│ Extensions │ {list of extensions} │
│ Roles │ app_rw, app_ro, app_migrate │
│ Object Storage │ {yes/no} — {reason} │
│ Secret Provider │ {provider} — {reason} │
│ Load Balancer │ {yes/no} — {reason} │
│ Domain │ {domain or "configure later"} │
│ Zone │ {zone} ({location}) │
├──────────────────┼──────────────────────────────────────────┤
│ Est. Monthly Cost│ ~€{total}/month │
│ Server │ ~€{server_cost} │
│ Database │ ~€{db_cost} │
│ Storage │ ~€{storage_cost} │
└──────────────────┴──────────────────────────────────────────┘
Ask the user: "Does this look right? Want to change anything before we proceed?"
Adjust if they want changes. Repeat until they approve.
Generate the exact commands that will run and show them:
I'll run these commands to set up your infrastructure:
1. upctl server create --hostname {project}-prod --zone {zone} --plan {plan} ...
2. upctl database create --title {project}-pg --type pg --plan {db_plan} ...
3. [if storage] upctl object-storage create --name {project}-uploads ...
4. SSH into server to install Docker + Caddy + {secret provider}
5. Create database roles (app_rw, app_ro, app_migrate)
6. Enable extensions: {extensions}
7. Store credentials in {secret provider}
8. Generate .deploy.json, docker-compose.prod.yml, Caddyfile
9. Generate management scripts in scripts/
Ask the user: "Ready to provision? This will create billable resources on your UpCloud account."
Wait for explicit approval before proceeding.
Delegate to the existing /upcloud:setup skill logic. Follow the provisioning playbooks in ../upcloud-setup/references/:
provision-server.md — create server, install Docker + Caddyprovision-db.md — create managed PostgreSQL, enable extensions, create rolesprovision-storage.md — create object storage (if requested)provision-secrets.md — set up the chosen secret provider.deploy.json from templateShow progress as each step completes. If any step fails, report the error clearly and ask if the user wants to retry or skip.
Create standalone bash scripts in the project's scripts/ directory. Read the templates from templates/scripts/ and customize them with values from .deploy.json.
Scripts to generate:
scripts/deploy.sh — rsync code + rebuild containersscripts/migrate.sh — run database migrationsscripts/rollback.sh — revert to previous versionscripts/status.sh — health check + container statusscripts/logs.sh — tail container logsscripts/secrets.sh — manage secrets (list/add/update)All scripts:
#!/usr/bin/env bash and set -euo pipefail.deploy.json for config (server IP, project name, provider)secrets.provider)--help flags explaining usagechmod +x)After generating, make them executable:
chmod +x scripts/*.sh
Present a post-setup summary:
┌─────────────────────────────────────────────────────────────┐
│ {project_name} is ready! │
├─────────────────────────────────────────────────────────────┤
│ │
│ Server: ssh root@{server_ip} │
│ Database: {db_host}:{db_port} (credentials in {provider})│
│ Storage: {endpoint} (if created) │
│ Health: {health_url} │
│ │
│ Next steps: │
│ ┌───┐ │
│ │ 1 │ Deploy your first version: │
│ └───┘ ./scripts/deploy.sh │
│ or: /upcloud:deploy push │
│ │
│ ┌───┐ │
│ │ 2 │ Add your secrets: │
│ └───┘ ./scripts/secrets.sh add API_KEY=your_key │
│ or: /upcloud:deploy secrets │
│ │
│ ┌───┐ │
│ │ 3 │ Point your domain: │
│ └───┘ Add A record: {domain} → {server_ip} │
│ Caddy will auto-provision SSL │
│ │
│ ┌───┐ │
│ │ 4 │ Check status anytime: │
│ └───┘ ./scripts/status.sh │
│ or: /upcloud:deploy status │
│ │
│ Config saved to: .deploy.json (commit this to git) │
│ Scripts saved to: scripts/ (commit these to git) │
│ │
└─────────────────────────────────────────────────────────────┘
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
npx claudepluginhub emerging-tech-visma/et-upcloud