diff --git a/README.md b/README.md
index 0d4f253..a2a96e7 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,4 @@
-# opencli-skill × Claude Code
+# opencli × Claude Code
 
 > Control Bilibili, Zhihu, Twitter/X, YouTube, Weibo, Reddit and 10 more platforms with natural language — reusing your Chrome login session, no API keys needed.
 >
@@ -159,9 +159,33 @@ Known risks:
 | `opencli: command not found` | Re-run `npm install -g @jackwener/opencli`; check your PATH |
 | Chrome not being controlled | Make sure Chrome is open; verify Playwright MCP Bridge extension is enabled |
 | Login state not recognized | In Chrome, manually log in to the target site first |
+| Repeated browser authorization prompts / works in terminal but not in agent runtime | Check `PLAYWRIGHT_MCP_EXTENSION_TOKEN`. In OpenClaw, write it to `~/.openclaw/.env` and restart Gateway. In Claude Code or a direct terminal workflow, persist it in the shell env used to launch the agent, then restart the session |
 | "Playwright MCP not found" error | Re-run Step 3: `claude mcp add playwright ...` |
 | `npx skills add` fails | Make sure Node.js v16+ is installed |
 
+#### Environment Token Check
+
+If the browser bridge keeps asking you to authorize again, or `opencli` works in a normal terminal but fails inside an agent runtime, verify that the current process can see:
+
+```bash
+PLAYWRIGHT_MCP_EXTENSION_TOKEN
+```
+
+Quick verification:
+
+```bash
+python -c "import os; print('PRESENT' if os.getenv('PLAYWRIGHT_MCP_EXTENSION_TOKEN') else 'MISSING')"
+```
+
+OpenClaw users should usually persist the token here:
+
+```bash
+echo 'PLAYWRIGHT_MCP_EXTENSION_TOKEN=your-token' >> ~/.openclaw/.env
+openclaw gateway restart
+```
+
+Claude Code or direct terminal users should persist the token in the shell environment that launches the agent, then start a new session before retrying `opencli`.
+
 ### Credits
 
 Built on **[jackwener/opencli](https://github.com/jackwener/opencli)**.
@@ -330,9 +354,33 @@ opencli reddit hot --subreddit MachineLearning
 | `opencli: command not found` | 重新运行 `npm install -g @jackwener/opencli`，检查 PATH 配置 |
 | Chrome 无法被控制 | 确保 Chrome 已打开，且 Playwright MCP Bridge 扩展已启用 |
 | 登录态未识别 | 在 Chrome 中手动登录目标网站后再试 |
+| 浏览器反复要求授权，或 terminal 能跑但 agent 里不行 | 检查 `PLAYWRIGHT_MCP_EXTENSION_TOKEN`。如果是 OpenClaw，优先写入 `~/.openclaw/.env` 并重启 Gateway；如果是 Claude Code 或普通终端工作流，把它持久化到启动 agent 的 shell 环境后重开会话 |
 | 提示找不到 Playwright MCP | 重新执行第三步的配置命令 |
 | `npx skills add` 报错 | 确认 Node.js v16+ 已安装 |
 
+#### 环境变量检查
+
+如果浏览器桥接链路反复要求你重新授权，或者 `opencli` 在普通 terminal 里可用、但在 agent 运行时里失效，先确认当前进程是否能看到：
+
+```bash
+PLAYWRIGHT_MCP_EXTENSION_TOKEN
+```
+
+快速验证：
+
+```bash
+python -c "import os; print('PRESENT' if os.getenv('PLAYWRIGHT_MCP_EXTENSION_TOKEN') else 'MISSING')"
+```
+
+如果你在 OpenClaw 中使用，通常建议把 token 写到这里：
+
+```bash
+echo 'PLAYWRIGHT_MCP_EXTENSION_TOKEN=your-token' >> ~/.openclaw/.env
+openclaw gateway restart
+```
+
+如果你在 Claude Code 或普通终端里使用，请把 token 持久化到启动 agent 的 shell 环境中，然后开启一个新的会话后再重试 `opencli`。
+
 ### 致谢
 
 本 Skill 基于 **[jackwener/opencli](https://github.com/jackwener/opencli)** 构建。
diff --git a/SKILL.md b/SKILL.md
index 2b52b4f..8eb12d5 100644
--- a/SKILL.md
+++ b/SKILL.md
@@ -129,6 +129,83 @@ opencli 有对应命令？
 - Chrome browser open with target site logged in
 - Playwright MCP Bridge extension installed in Chrome（未安装时见上方引导）
 
+## Environment Preflight
+
+Before retrying browser-backed opencli commands or asking the user to re-authorize repeatedly, do a one-time environment check for:
+
+```bash
+PLAYWRIGHT_MCP_EXTENSION_TOKEN
+```
+
+### Required behavior for the agent
+
+1. Check whether `PLAYWRIGHT_MCP_EXTENSION_TOKEN` exists in the current execution environment.
+2. If the variable is present, continue with normal opencli execution.
+3. If the variable is missing, stop the retry loop and explain that the browser bridge token is not available to the current process.
+4. Ask the user to provide the token or confirm that the agent should help persist it in the correct place for the current runtime.
+5. After the token is written, re-check the environment and run one small `opencli ... -f json` command to verify the fix.
+
+### Runtime-specific remediation
+
+- **OpenClaw / Gateway service**: prefer `~/.openclaw/.env`, then run `openclaw gateway restart`
+- **Claude Code / direct terminal**: prefer the env location already used by the user's shell or tool bootstrap. If no existing convention is visible, suggest persisting it in the login shell startup file such as `~/.zshrc` or `~/.bashrc`, then restarting the session
+
+### Safety rules
+
+- Never invent a token value
+- Never print the full token back to the user after they provide it
+- Do not keep retrying commands that trigger repeated browser authorization if the env check already failed
+
+## OpenClaw 环境提醒
+
+如果任务运行在 **OpenClaw** 里，而不是普通 terminal / Claude Code 直连环境，优先检查浏览器扩展 token 是否真的进入了 Gateway 的执行环境。
+
+关键变量：
+
+```bash
+PLAYWRIGHT_MCP_EXTENSION_TOKEN
+```
+
+原因：OpenClaw 的 Gateway 常常作为后台服务运行（例如 launchd/systemd），**不会自动继承你当前 shell 的环境变量**。这会导致一种很迷惑的现象：
+
+- 在 terminal 里直接运行 `opencli ...` 可以成功
+- 但在 OpenClaw 里调用同样命令时，登录态失效或浏览器链路不可用
+
+### OpenClaw 下的优先排查动作
+
+1. 先检查当前执行环境里有没有这个变量
+2. 如果没有，不要继续重复拉起浏览器授权，而是先提醒当前进程缺少 token
+3. 如果用户希望 agent 直接协助修复，优先把它写进 `~/.openclaw/.env`
+4. 然后提醒重启 Gateway：`openclaw gateway restart`
+5. 再重新测试 opencli 命令
+
+推荐提示模板：
+
+> 如果你是在 OpenClaw 里用 opencli，而不是在 terminal 里直接运行，请先确认 `PLAYWRIGHT_MCP_EXTENSION_TOKEN` 已写入 `~/.openclaw/.env`。因为 Gateway 作为服务运行时，通常不会自动继承你 shell 里的环境变量。写入后执行 `openclaw gateway restart`，再重新测试。
+
+### 推荐修法
+
+```bash
+echo 'PLAYWRIGHT_MCP_EXTENSION_TOKEN=你的token' >> ~/.openclaw/.env
+openclaw gateway restart
+```
+
+### 可选方案
+
+OpenClaw 官方还支持：
+
+- 在 `~/.openclaw/openclaw.json` 中配置 `env` block
+- 开启 `env.shellEnv.enabled: true`
+
+但如果当前现象是“terminal 能跑、OpenClaw 里不行”，默认优先建议 `~/.openclaw/.env`，因为这条路最稳，也最容易验证。
+
+### 建议验证命令
+
+```bash
+python -c "import os; print('PRESENT' if os.getenv('PLAYWRIGHT_MCP_EXTENSION_TOKEN') else 'MISSING')"
+opencli xiaohongshu search --keyword "opencli" --limit 5 -f json
+```
+
 ## 自迭代能力：为新网站创建 CLI
 
 **当 opencli 不支持某个网站时，不要放弃——自己创建！**