1 files changed, 31 insertions, 62 deletions

diff --git a/skills/ship-setup/SKILL.md b/skills/ship-setup/SKILL.md
index e3d08ee..73297b6 100644
--- a/skills/ship-setup/SKILL.md
+++ b/skills/ship-setup/SKILL.md
@@ -8,11 +8,21 @@ argument-hint: "[host-nickname]"
 
 Configure ship and prepare a VPS for deployments.
 
+## Companion Script
+
+Server setup is handled by `setup.sh` in this skill's directory. It is idempotent,
+handles all branching logic, and mirrors the behavior of the original `ship host init`
+Go CLI command.
+
+```
+skills/ship-setup/setup.sh <ssh-host> <base-domain> <nickname> [--default]
+```
+
 ## Config File
 
-All ship skills read from `~/.config/ship/config.json`. This skill creates or updates it.
+All ship skills read from `~/.config/ship/config.json`. The setup script creates or
+updates it — never overwrites the whole file.
 
-Structure:
 ```json
 {
   "default": "prod",
@@ -43,80 +53,39 @@ If it exists, show the user the current hosts so they know what's already config
 
 ### 2. Get host details
 
-If no nickname was provided as an argument, ask the user:
-- **Nickname** — a short name for this host (e.g. `prod`, `staging`, `vps`)
-- **SSH connection string** — e.g. `ubuntu@1.2.3.4` or an SSH config alias like `alaskav6`
+If not already known, ask the user:
+- **Nickname** — short name for this host (e.g. `prod`, `staging`)
+- **SSH connection string** — e.g. `ubuntu@1.2.3.4` or an alias from `~/.ssh/config`
 - **Base domain** — the domain pointing to this server (e.g. `example.com`)
+- **Default?** — if this is the first host, make it default. Otherwise ask.
 
-If this is the first host, ask if it should be the default. If hosts already exist, ask if this should replace the current default.
-
-### 3. Test SSH connection
-
-Verify the connection works before saving anything:
-
-```bash
-ssh -o ConnectTimeout=5 <host> "echo ok"
-```
-
-If it fails, tell the user and stop. Don't save config for an unreachable host.
-
-### 4. Save config
-
-Write or update `~/.config/ship/config.json` with the new host. Merge with existing hosts — never overwrite the whole file. Use Python to safely read/write JSON:
-
-```bash
-python3 -c "
-import json, os
-path = os.path.expanduser('~/.config/ship/config.json')
-os.makedirs(os.path.dirname(path), exist_ok=True)
-cfg = json.load(open(path)) if os.path.exists(path) else {'default': None, 'hosts': {}}
-cfg['hosts']['<nickname>'] = {'host': '<ssh-host>', 'domain': '<domain>'}
-if not cfg['default']:
-    cfg['default'] = '<nickname>'
-json.dump(cfg, open(path, 'w'), indent=2)
-print('saved')
-"
-```
-
-### 5. Install server dependencies
-
-SSH in and ensure the required directories and software exist. This is idempotent — safe to run multiple times.
-
-**Install Caddy** (if not present):
-```bash
-ssh <host> "which caddy || (sudo apt-get install -y debian-keyring debian-archive-keyring apt-transport-https curl && curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | sudo gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg && curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' | sudo tee /etc/apt/sources.list.d/caddy-stable.list && sudo apt-get update && sudo apt-get install -y caddy)"
-```
+### 3. Run the setup script
 
-**Create directory structure:**
 ```bash
-ssh <host> "sudo mkdir -p /etc/ship/env /etc/ship/ports /etc/caddy/sites-enabled /var/www && sudo chmod 755 /etc/ship"
+bash ~/.claude/skills/ship-setup/setup.sh <ssh-host> <domain> <nickname> [--default]
 ```
 
-**Configure main Caddyfile** (only if not already set up):
-```bash
-ssh <host> "sudo test -f /etc/caddy/Caddyfile && echo exists || echo '{
-}
-
-import /etc/caddy/sites-enabled/*' | sudo tee /etc/caddy/Caddyfile"
-```
-
-**Enable and start Caddy:**
-```bash
-ssh <host> "sudo systemctl enable caddy && sudo systemctl start caddy"
-```
+The script will:
+1. Test the SSH connection — stops early if it fails
+2. Detect OS (Ubuntu/Debian only)
+3. Install Caddy if not present
+4. Configure the main Caddyfile if not already set up
+5. Create required directories (`/etc/ship/env`, `/etc/ship/ports`, `/etc/caddy/sites-enabled`, `/var/www`)
+6. Enable and start Caddy
+7. Save the host to `~/.config/ship/config.json`
 
-### 6. Confirm
+### 4. Confirm
 
 Tell the user:
 - Host nickname and SSH target saved
 - Whether it's the default host
 - That the server is ready for deployments
-- How to add another host: `/ship-setup <nickname>`
+- How to add another host: `/ship-setup`
 - How to deploy: `/ship-deploy`
 
 ## Notes
 
-- Never overwrite the entire config file — always merge
-- If a nickname already exists in config, confirm before overwriting it
-- The SSH host can be an alias from `~/.ssh/config` — no need to require raw IP
+- Safe to run multiple times — all steps are idempotent
+- The SSH host can be an alias from `~/.ssh/config`
+- If a nickname already exists in config, the script overwrites it — confirm with the user first
 - Default host is used by all other ship skills when no host is specified