Updated skills

Author: pinebit

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

@@ -6,6 +6,8 @@ user-invokable: true
 
 # Add Operators
 
+> **Warning:** This is an alpha feature and is not yet recommended for production use.
+
 Expand a Charon cluster by adding new operators. This is a coordinated operation involving both existing and new operators.
 
 ## Prerequisites
@@ -14,8 +16,9 @@ Read `scripts/edit/add-operators/README.md` for full details if needed.
 
 Common prerequisites:
 1. `.env` file exists with `NETWORK` and `VC` variables set
-2. Docker is running
-3. `jq` installed
+2. `.charon` directory with `cluster-lock.json` and `charon-enr-private-key`
+3. Docker is running
+4. `jq` installed
 
 ## Role Selection
 
@@ -57,6 +60,7 @@ Ask if the user needs to generate an ENR (first time setup):
 ```
 
 This creates `.charon/charon-enr-private-key` and displays the ENR. Tell the user to **share this ENR with the existing operators**.
+The existing operators, in turn, need to share the `cluster-lock.json` with the new operators, which contains the current cluster configuration and is required for the P2P ceremony.
 
 #### Step 2: Join the Ceremony
 

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

@@ -6,6 +6,8 @@ user-invokable: true
 
 # Add Validators
 
+> **Warning:** This is an alpha feature and is not yet recommended for production use.
+
 Add new validators to an existing Charon distributed validator cluster. All operators must run this simultaneously as it requires a P2P ceremony.
 
 ## Prerequisites

.claude/skills/export-asdb/SKILL.md

@@ -6,6 +6,8 @@ user-invokable: true
 
 # Export Anti-Slashing Database
 
+> **Warning:** This is an alpha feature and is not yet recommended for production use.
+
 Export the EIP-3076 anti-slashing database from the validator client. The VC container must be stopped before export.
 
 ## Prerequisites

.claude/skills/import-asdb/SKILL.md

@@ -6,6 +6,8 @@ user-invokable: true
 
 # Import Anti-Slashing Database
 
+> **Warning:** This is an alpha feature and is not yet recommended for production use.
+
 Import an EIP-3076 anti-slashing database into the validator client. The VC container must be stopped.
 
 ## Prerequisites

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

@@ -6,6 +6,8 @@ user-invokable: true
 
 # Recreate Private Keys
 
+> **Warning:** This is an alpha feature and is not yet recommended for production use.
+
 Refresh private key shares held by operators while keeping the same validator public keys. Validators stay registered on the beacon chain - only the operator key shares change. All operators must participate simultaneously.
 
 ## Use Cases

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

@@ -6,6 +6,8 @@ user-invokable: true
 
 # Remove Operators
 
+> **Warning:** This is an alpha feature and is not yet recommended for production use.
+
 Remove one or more operators from a Charon cluster. Whether removed operators need to participate depends on fault tolerance.
 
 ## Prerequisites

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

@@ -6,6 +6,8 @@ user-invokable: true
 
 # Replace Operator
 
+> **Warning:** This is an alpha feature and is not yet recommended for production use.
+
 Replace a single operator in a Charon cluster with a new one. All participating operators (remaining + new) run a `charon alpha edit replace-operator` ceremony together (P2P via relay). The new operator must receive the current cluster-lock.json before the ceremony begins.
 
 ## Prerequisites
@@ -61,11 +63,12 @@ Ask if the user needs to generate an ENR:
 ./scripts/edit/replace-operator/new-operator.sh --generate-enr
 ```
 
-This creates `.charon/charon-enr-private-key` and displays the ENR. Tell the user to **share this ENR with the remaining operators**.
+This creates `.charon/charon-enr-private-key` and displays the ENR. Tell the user to **share this ENR with the existing operators**.
+The existing operators, in turn, need to share the `cluster-lock.json` with the new operators, which contains the current cluster configuration and is required for the P2P ceremony.
 
 #### Step 2: Run the Ceremony
 
-After receiving the current `cluster-lock.json` from remaining operators (BEFORE the ceremony):
+After receiving the current `cluster-lock.json` from remaining operators:
 - `--cluster-lock`: Path to the received `cluster-lock.json`
 - `--old-enr`: ENR of the operator being replaced
 - Whether to use `--dry-run` first

scripts/edit/add-operators/README.md

@@ -25,7 +25,7 @@ There are two scripts for the two roles involved:
 - Docker running
 - `jq` installed
 - **Existing operators**: `.charon` directory with `cluster-lock.json` and `validator_keys`
-- **New operators**: Charon ENR private key (generated via `--generate-enr`)
+- **New operators**: `cluster-lock.json` received from existing operators, and ENR private key (generated via `--generate-enr`)
 
 ## For Existing Operators
 

scripts/edit/replace-operator/README.md

@@ -36,7 +36,7 @@ Automates the complete workflow for operators staying in the cluster:
     --old-enr "enr:-..."
 ```
 
-**Before running**: Share your current `cluster-lock.json` with the new operator so they can participate in the ceremony.
+**Before running**: Share your current `cluster-lock.json` with the new operator so it can participate in the ceremony.
 
 ### Options
 
@@ -68,7 +68,7 @@ Two-step workflow for the new operator joining the cluster.
 ./scripts/edit/replace-operator/new-operator.sh --generate-enr
 ```
 
-**Step 2:** After receiving `cluster-lock.json` from remaining operators (BEFORE the ceremony), run the ceremony together with all other operators:
+**Step 2:** After receiving `cluster-lock.json` from remaining operators, run the ceremony together with all other operators:
 
 ```bash
 ./scripts/edit/replace-operator/new-operator.sh \