From 67125c378d579fe8d53a68972856d1453d80c7d9 Mon Sep 17 00:00:00 2001
From: xlrrrr <lrxu0818@gmail.com>
Date: Sat, 28 Mar 2026 10:53:53 +0800
Subject: [PATCH] docs: update openclaw setup instructions in host_skills
 README

---
 openspace/host_skills/README.md | 33 ++-------------------------------
 1 file changed, 2 insertions(+), 31 deletions(-)

diff --git a/openspace/host_skills/README.md b/openspace/host_skills/README.md
index 6d23815..0a555ed 100644
--- a/openspace/host_skills/README.md
+++ b/openspace/host_skills/README.md
@@ -55,17 +55,9 @@ cp -r host_skills/skill-discovery/ /path/to/openclaw/skills/
 cp -r host_skills/delegate-task/ /path/to/openclaw/skills/
 ```
 
-### 2. Register MCP server
+### 2. Register MCP server with env vars
 
-openclaw uses [mcporter](https://github.com/steipete/mcporter) as its MCP runtime:
-
-```bash
-mcporter config add openspace --command "openspace-mcp"
-```
-
-### 3. Configure env vars
-
-You can pass env vars directly when registering the MCP server in step 2, combining both steps into one command:
+openclaw uses [mcporter](https://github.com/steipete/mcporter) as its MCP runtime. Register the server and pass env vars in one command:
 
 ```bash
 mcporter config add openspace --command "openspace-mcp" \
@@ -74,27 +66,6 @@ mcporter config add openspace --command "openspace-mcp" \
   --env OPENSPACE_API_KEY=sk-xxx
 ```
 
-> [!TIP]
-> If you already ran step 2 without `--env`, you can re-run the command above to update the registration.
-
-Alternatively, if you prefer to keep env vars separate from the mcporter registration, set them in `~/.openclaw/openclaw.json` (openclaw will pass them to the MCP server at launch time):
-
-```json
-{
-  "skills": {
-    "entries": {
-      "openspace": {
-        "env": {
-          "OPENSPACE_HOST_SKILL_DIRS": "/path/to/openclaw/skills",
-          "OPENSPACE_WORKSPACE": "/path/to/OpenSpace",
-          "OPENSPACE_API_KEY": "sk-xxx"
-        }
-      }
-    }
-  }
-}
-```
-
 ---
 
 ## Environment Variables (Agent-Specific)