Unified skills and scripts

Author: pinebit

.claude/skills/add-operators/SKILL.md

@@ -39,7 +39,7 @@ Ask the user: **"Are you an existing operator in the cluster, or a new operator
     [--dry-run]
 ```
 
-The script will export the anti-slashing database, run the P2P ceremony, update keys, and provide restart instructions. After completion, remind the user to **wait ~2 epochs before restarting** containers.
+The script will export the anti-slashing database, run the P2P ceremony, update keys, and print commands to start containers manually. After completion, remind the user to **wait ~2 epochs before starting** containers.
 
 ### If New Operator
 
@@ -71,4 +71,4 @@ After the existing operators have the ENR, gather:
     [--dry-run]
 ```
 
-Remind the user that **all operators (existing AND new) must participate simultaneously** in the P2P ceremony.
+Remind the user that **all operators (existing AND new) must participate simultaneously** in the P2P ceremony. After completion, the script will print commands to start containers manually. The new operator does NOT have slashing protection history (fresh start).

.claude/skills/add-validators/SKILL.md

@@ -46,8 +46,9 @@ The script will:
 1. Validate prerequisites
 2. Display current cluster info (operators, validators)
 3. Run a P2P ceremony (all operators must participate simultaneously)
-4. Backup `.charon/` to `./backups/`
-5. Install new configuration
-6. Restart containers if they were previously running
+4. Stop containers if they were running
+5. Backup `.charon/` to `./backups/`
+6. Install new configuration
+7. Print commands to start containers manually
 
 Remind the user that **all operators must run this script at the same time** for the P2P ceremony to succeed.

.claude/skills/recreate-private-keys/SKILL.md

@@ -41,7 +41,8 @@ The script will:
 6. Backup `.charon/` to `./backups/`
 7. Install new key shares
 8. Import updated ASDB
+9. Print commands to start containers manually
 
-After completion, remind the user to **wait ~2 epochs before restarting** containers.
+After completion, remind the user to **wait ~2 epochs before starting** containers.
 
 Remind the user that **all operators must run this script at the same time** for the P2P ceremony to succeed.

.claude/skills/remove-operators/SKILL.md

@@ -51,7 +51,7 @@ Ask the user: **"Are you a remaining operator (staying in the cluster) or a remo
     [--dry-run]
 ```
 
-After completion, remind the user to **wait ~2 epochs before restarting** containers.
+After completion, the script will print commands to start containers manually. Remind the user to **wait ~2 epochs before starting** containers.
 
 ### If Removed Operator
 

.claude/skills/replace-operator/SKILL.md

@@ -43,7 +43,7 @@ Ask the user: **"Are you a remaining operator (performing the replacement) or th
     [--dry-run]
 ```
 
-After completion, the script will output the new `cluster-lock.json`. Remind the user to **share the new cluster-lock.json with the new operator** and to **wait ~2 epochs before restarting** containers.
+After completion, the script will print commands to start containers manually. Remind the user to **share the new cluster-lock.json with the new operator** and to **wait ~2 epochs before starting** containers.
 
 ### If New Operator
 
@@ -73,4 +73,4 @@ After receiving the new `cluster-lock.json` from remaining operators:
     [--dry-run]
 ```
 
-The script will verify the ENR is present in the cluster-lock, install the configuration, and start charon and VC containers. Note: the new operator does NOT have slashing protection history (fresh start).
+The script will verify the ENR is present in the cluster-lock, install the configuration, and print commands to start containers manually. Note: the new operator does NOT have slashing protection history (fresh start).

scripts/edit/add-operators/README.md

@@ -46,13 +46,13 @@ Automates the complete workflow for operators already in the cluster:
 
 ### Workflow
 
-1. **Export ASDB** - Export anti-slashing database from running VC
+1. **Export ASDB** - Stop VC if running and export anti-slashing database
 2. **Run ceremony** - P2P coordinated add-operators ceremony with all operators
 3. **Update ASDB** - Replace pubkeys in exported ASDB to match new cluster-lock
 4. **Stop containers** - Stop charon and VC
 5. **Backup and replace** - Backup current `.charon/` to `./backups/`, install new configuration
 6. **Import ASDB** - Import updated anti-slashing database
-7. **Print restart commands** - Display commands to start containers after waiting ~2 epochs
+7. **Print start commands** - Display commands to start containers manually (wait ~2 epochs before starting)
 
 ## For New Operators
 

scripts/edit/add-operators/new-operator.sh

@@ -349,24 +349,19 @@ log_info "New cluster configuration installed to .charon/"
 
 echo ""
 
-# Step 4: Start containers
-log_step "Step 4: Starting containers..."
-
-run_cmd docker compose up -d charon "$VC"
-
-log_info "Containers started"
-
 echo ""
 echo "╔════════════════════════════════════════════════════════════════╗"
 echo "║     New Operator Setup COMPLETED                               ║"
 echo "╚════════════════════════════════════════════════════════════════╝"
 echo ""
 log_info "Summary:"
 log_info "  - Cluster configuration installed in: .charon/"
-log_info "  - Containers started: charon, $VC"
 echo ""
-log_info "Next steps:"
-log_info "  1. Wait for charon to sync with peers: docker compose logs -f charon"
+log_info "When ready, start containers with:"
+echo "  docker compose up -d charon $VC"
+echo ""
+log_info "After starting, verify:"
+log_info "  1. Check charon logs: docker compose logs -f charon"
 log_info "  2. Verify VC is running: docker compose logs -f $VC"
 log_info "  3. Monitor validator duties once synced"
 echo ""

scripts/edit/add-validators/README.md

@@ -51,7 +51,7 @@ The script performs the following steps:
 2. **Run ceremony** - P2P coordinated add-validators ceremony with all operators
 3. **Stop containers** - Stop charon and VC (only if they were running)
 4. **Backup and replace** - Backup current `.charon/` to `./backups/`, install new configuration
-5. **Restart containers** - Start charon and VC (only if they were running before)
+5. **Print start commands** - Display commands to start containers manually
 
 ## Related
 

scripts/edit/add-validators/add-validators.sh

@@ -305,22 +305,6 @@ log_info "Current .charon backed up to $BACKUP_DIR/.charon-backup.$TIMESTAMP"
 run_cmd mv "$OUTPUT_DIR" .charon
 log_info "New cluster configuration installed to .charon/"
 
-echo ""
-
-# Step 4: Restart containers (if they were running before)
-log_step "Step 4: Restarting containers..."
-
-if [ "$CHARON_WAS_RUNNING" = true ] || [ "$VC_WAS_RUNNING" = true ]; then
-    if [ "$UNVERIFIED" = true ]; then
-        log_warn "Starting charon with CHARON_NO_VERIFY=true (required for --unverified mode)"
-    fi
-    run_cmd docker compose up -d charon "$VC"
-    log_info "Containers restarted"
-else
-    log_info "Containers were not running before, skipping restart"
-    log_info "Start manually with: docker compose up -d charon $VC"
-fi
-
 echo ""
 echo "╔════════════════════════════════════════════════════════════════╗"
 echo "║     Add Validators Workflow COMPLETED                          ║"
@@ -330,17 +314,22 @@ log_info "Summary:"
 log_info "  - Old .charon backed up to: $BACKUP_DIR/.charon-backup.$TIMESTAMP"
 log_info "  - New cluster configuration installed in: .charon/"
 log_info "  - $NUM_VALIDATORS new validator(s) added"
-if [ "$CHARON_WAS_RUNNING" = true ] || [ "$VC_WAS_RUNNING" = true ]; then
-    log_info "  - Containers restarted: charon, $VC"
-else
-    log_info "  - Containers not restarted (were not running)"
-fi
-
+echo ""
+log_info "When ready, start containers with:"
+echo "  docker compose up -d charon $VC"
+echo ""
+log_info "After starting, verify:"
+log_info "  1. Check charon logs: docker compose logs -f charon"
+log_info "  2. Verify VC is running: docker compose logs -f $VC"
+log_info "  3. Verify cluster is producing attestations"
+echo ""
 if [ "$UNVERIFIED" = true ]; then
-    echo ""
     log_warn "IMPORTANT: You used --unverified mode."
     log_warn "Ensure CHARON_NO_VERIFY=true is set in your .env file for future restarts."
+    echo ""
 fi
+log_warn "Keep the backup until you've verified normal operation for several epochs."
+echo ""
 
 echo ""
 log_info "Next steps:"

scripts/edit/recreate-private-keys/README.md

@@ -38,7 +38,7 @@ The script will:
 5. Backup current `.charon` directory to `./backups/`
 6. Move new keys from `./output/` to `.charon/`
 7. Import the updated anti-slashing database
-8. Print restart commands (wait ~2 epochs before starting)
+8. Print start commands (wait ~2 epochs before starting)
 
 ## Options