uniner-cli 1.0.5 → 1.0.7

package/README.md

@@ -2,10 +2,10 @@
 
 `uniner-cli` 是 [Uniner](https://www.uniner.com/) 的 RPA 自动化命令行工具，提供：
 
-- **Web 自动化**（Playwright + CDP）—— 浏览器抓取、表单填写、元素交互
+- **Web 自动化** —— 浏览器抓取、表单填写、元素交互
 - **Excel 操作** —— 读写、批量处理、样式
-- **OCR 识别** —— ddddocr（验证码）+ PaddleOCR（通用）
-- **桌面 / SAP 自动化**（仅 Windows）
+- **OCR 识别** —— 支持验证码和通用 OCR
+- **桌面 / SAP 自动化** —— 支持桌面软件的自动化（仅 Windows）
 - **通用工具** —— 加密、HTTP、邮件、文件、PDF、压缩
 
 安装时会自动注册一个 [Claude Code](https://claude.com/claude-code) 技能（`~/.claude/skills/uniner-cli/SKILL.md`），让 Claude 一启动就能识别并调用本 CLI。
@@ -14,18 +14,27 @@
 
 ## 安装
 
+全局安装：
+
 ```bash
 npm install -g uniner-cli
 ```
 
-安装过程：
+当前目录安装：
+
+```bash
+npm install uniner-cli
+```
+
+> 本地安装后通常通过 `npx uniner-cli --help` 或项目里的 npm scripts 调用；只有全局安装才适合在任意终端直接运行 `uniner-cli`。
 
-1. npm 装本壳包（约 50KB）
-2. `postinstall` 钩子从 `static.uniner.com` 拉取约 250MB 便携包
-3. 解压到 `%USERPROFILE%\.uniner-cli\<version>\`
-4. 写入 `%USERPROFILE%\.claude\skills\uniner-cli\SKILL.md`
+安装过程中会自动完成：
 
-完成后任意终端：
+1. 下载并配置当前平台所需的 uniner-cli 运行时
+2. 注册 Claude Code 技能
+3. 准备 `uniner-cli` 命令入口
+
+全局安装完成后任意终端：
 
 ```bash
 uniner-cli --help
@@ -35,12 +44,12 @@ uniner-cli --help
 
 | 项 | 要求 |
 |---|---|
-| 操作系统 | 64 位 Windows 10 / 11 |
+| 操作系统 | Windows 10/11 x64 · macOS 12+ ARM64 · Linux x64 |
 | Node.js | >= 14 |
-| 磁盘空间 | ≥ 1.5 GB |
+| 磁盘空间 | ≥ 500 MB（单平台） |
 | 网络 | 能访问 `static.uniner.com` |
 
-> Linux / macOS 支持在路上。
+> 安装脚本会自动检测当前系统并下载对应版本。
 
 ## 使用示例
 
@@ -61,7 +70,7 @@ uniner-cli excel data write --file out.xlsx --cell B2 --value "hello"
 uniner-cli tool ocr ddddocr --img captcha.png
 ```
 
-完整命令树（一级 + 二级 + 三级参数）见安装后 `%USERPROFILE%\.uniner-cli\<version>\skills\cli\SKILL.md`。
+完整命令树（一级 + 二级 + 三级参数）可通过 `uniner-cli --help` 查看。
 
 ## 升级
 
@@ -79,24 +88,45 @@ npm install -g uniner-cli@latest
 
 ## 卸载
 
+> **重要提示**：直接使用 `npm uninstall` 可能无法清理运行时文件。
+> 请使用 CLI 自带的一键卸载命令以确保完全清理。
+
+**推荐卸载流程**：
+
 ```bash
-# 1. 先清理运行时数据（删 ~/.uniner-cli/ 和 Claude Code 技能）
-uniner-cli-uninstall
+uniner-cli uninstall
+```
 
-# 2. 再卸载 npm 包本身
-npm uninstall -g uniner-cli
+该命令会先清理运行时残留，再自动判断安装范围并移除 npm 包本体：
+
+- 全局安装：执行 `npm uninstall -g uniner-cli`
+- 本地安装：在当前项目执行 `npm uninstall uniner-cli`
+
+如果自动判断不符合预期，可显式指定：
+
+```bash
+uniner-cli uninstall --global
+uniner-cli uninstall --local
 ```
 
-> **为什么是两步？** npm 7+ 出于安全考虑不再在卸载时运行 lifecycle 脚本，所以我们提供 `uniner-cli-uninstall` 命令让你显式触发清理。
+清理内容：
+
+- `~/.uniner-cli/` 整个运行时目录（含所有版本）
+- `~/.claude/skills/uniner-cli/SKILL.md` 技能文件
 
-清理会移除：
+> `~/.claude/skills/uniner-cli/scenarios/` 下用户积累的场景数据不会被删除，需手动清理。
+
+**备选方式**（如果 npm 包已经先被卸载，`uniner-cli` 不在 PATH 上）：
+
+```bash
+node ~/.uniner-cli/cleanup.js
+```
 
-- `%USERPROFILE%\.uniner-cli\<version>\` 安装目录
-- `%USERPROFILE%\.claude\skills\uniner-cli\SKILL.md` 技能
+> 该脚本只清理运行时残留，不再卸载 npm 包本体。
 
 ## 环境变量
 
-无需手动配置。npm 全局 bin 目录已自动加入 PATH。
+无需手动配置。全局安装时，npm 会把命令链接到全局 bin 目录；如果终端识别不到 `uniner-cli`，按下方排查 PATH。
 
 ## 故障排查
 
@@ -104,13 +134,19 @@ npm uninstall -g uniner-cli
 
 确认 npm 全局 bin 在 PATH 上：
 
-```powershell
+```bash
+# macOS / Linux
+npm config get prefix
+echo $PATH | tr ':' '\n' | grep npm
+
+# Windows (PowerShell)
 npm config get prefix
-# 应输出类似 C:\Users\xxx\AppData\Roaming\npm
 $env:Path -split ';' | Where-Object { $_ -like '*npm*' }
 ```
 
-如果没有，手动加 `%APPDATA%\npm` 到 PATH。
+如果没有，手动将 npm 全局 bin 目录加入 PATH：
+- macOS / Linux: `$(npm config get prefix)/bin`
+- Windows: `%APPDATA%\npm`
 
 ### 安装时下载失败 / 超时
 
@@ -123,39 +159,37 @@ npm config get https-proxy
 npm config set https-proxy http://your-proxy:port
 ```
 
-或者直接走原生安装方式（不走 npm）：
-
-```powershell
-iwr https://static.uniner.com/soft/editor/uninercli/install.ps1 -UseBasicParsing | iex
-```
+### 安装卡住 / 解压慢
 
-### postinstall 卡在解压
-
-杀软（360 / 火绒）会扫描 1279 个新文件，慢则 5–10 分钟。让它跑完即可。
+杀软（360 / 火绒）可能会扫描大量新文件，慢则 5–10 分钟。让它跑完即可。
 
 ### 想重装
 
 ```bash
-npm uninstall -g uniner-cli
+uniner-cli uninstall
 npm install -g uniner-cli
 ```
 
-## 备选安装方式（不走 npm）
-
-如果你不想要 Node.js 依赖，可以用 PowerShell 一行安装（基于 Inno Setup 安装器）：
-
-```powershell
-iwr https://static.uniner.com/soft/editor/uninercli/install.ps1 -UseBasicParsing | iex
-```
-
-两种方式互不干扰，但**不要**同时启用——会有两份 SKILL.md / 两份二进制。
-
 ## 链接
 
 - 官网：[https://www.uniner.com/](https://www.uniner.com/)
 - 技术支持：support@uniner.com
 - Claude Code：[https://claude.com/claude-code](https://claude.com/claude-code)
 
+## Changelog
+
+### 1.0.7 (2026-06-29)
+
+- **fix**: 新增 `uniner-cli uninstall`，自动判断全局 / 本地安装范围，完整清理运行时文件并移除 npm 包。
+
+### 1.0.6 (2026-06-28)
+
+- **fix**: 修复 `npm uninstall -g uniner-cli` 未清理 `~/.uniner-cli/` 和 `~/.claude/skills/uniner-cli/SKILL.md` 的问题。
+
+### 1.0.5 (2026-06-27)
+
+- 首个公开版本，支持 Windows 10/11 (x64)、macOS (Apple Silicon)、Linux (x64)
+
 ## License
 
 Proprietary. (C) 2026 Uniner Tech.

package/bin/uniner-cli-uninstall.js

@@ -1,145 +1,84 @@
 #!/usr/bin/env node
-// uniner-cli-uninstall - removes the runtime tree and Claude Code skill.
+// uniner-cli-uninstall — manual cleanup command.
 //
-// npm 7+ no longer runs preuninstall/postuninstall lifecycle scripts on
-// uninstall (security tightening). So we ship this command for users to
-// run BEFORE `npm uninstall -g uniner-cli` to clean their machine.
+// Background:
+//   npm 7+ (including npm 11) does NOT reliably run the `preuninstall`
+//   lifecycle hook for globally installed packages. This means
+//   `npm uninstall -g uniner-cli` removes the npm package but leaves
+//   residual files behind:
+//     - ~/.uniner-cli/            (runtime binaries, skills, docs)
+//     - ~/.claude/skills/uniner-cli/SKILL.md  (Claude Code skill file)
 //
-// Recommended workflow:
-//   uniner-cli-uninstall              # this script: clean ~/.uniner-cli/ + skill
-//   npm uninstall -g uniner-cli       # npm: remove the npm package itself
+// To solve this, postinstall writes a self-contained cleanup script to
+// ~/.uniner-cli/cleanup.js. That file survives `npm uninstall` and can
+// always be run manually.
+//
+// Recommended workflow (ensures a clean uninstall):
+//   npm uninstall -g uniner-cli
+//   node ~/.uniner-cli/cleanup.js        # always works, even after npm removes the package
+//
+// Alternative (only works BEFORE you run `npm uninstall -g`):
+//   uniner-cli-uninstall                 # this command; removed along with the package
+//   npm uninstall -g uniner-cli
 //
 // Idempotent: if files are already gone, just no-ops.
 
 'use strict';
 
-const fs   = require('fs');
 const path = require('path');
+const os   = require('os');
+const fs   = require('fs');
 
-const {
-    pkg,
-    rootDir,
-    versionDir,
-    skillDir,
-    skillFile,
-} = require('../lib/paths');
-
-function log(msg)  { console.log(`[uniner-cli] ${msg}`); }
-function warn(msg) { console.warn(`[uniner-cli] [WARN] ${msg}`); }
-
-function rmRf(p) {
-    try {
-        if (fs.existsSync(p)) {
-            fs.rmSync(p, { recursive: true, force: true });
-            log(`Removed ${p}`);
-            return true;
-        }
-        return false;
-    } catch (e) {
-        warn(`Could not remove ${p}: ${e.message}`);
-        return false;
-    }
-}
-
-function rmFile(p) {
-    try {
-        if (fs.existsSync(p)) {
-            fs.unlinkSync(p);
-            log(`Removed ${p}`);
-            return true;
-        }
-        return false;
-    } catch (e) {
-        warn(`Could not remove ${p}: ${e.message}`);
-        return false;
-    }
+// Prefer the standalone cleanup.js if it exists (written by postinstall,
+// survives npm uninstall). Fall back to the in-package cleanup module
+// (only works while the npm package is still installed).
+const standalonePath = path.join(os.homedir(), '.uniner-cli', 'cleanup.js');
+
+if (fs.existsSync(standalonePath)) {
+    // Delegate to the standalone script. It handles everything: removing
+    // ~/.uniner-cli/, removing SKILL.md, preserving scenarios/.
+    // Use spawnSync to avoid any require() path issues.
+    const { spawnSync } = require('child_process');
+    const result = spawnSync(process.execPath, [standalonePath], {
+        stdio: 'inherit',
+    });
+    process.exit(result.status || 0);
 }
 
-function main() {
-    console.log('');
-    console.log('==========================================');
-    console.log('  uniner-cli uninstall cleanup');
-    console.log('==========================================');
-
-    const myVersion = pkg.version;
-    const myVersionDir = versionDir(myVersion);
-    let didSomething = false;
-
-    // 1. Remove our version's runtime tree.
-    if (rmRf(myVersionDir)) didSomething = true;
-
-    // 2. If ~/.uniner-cli/ has no other versions, drop the whole directory.
-    try {
-        const root = rootDir();
-        if (fs.existsSync(root)) {
-            const remaining = fs.readdirSync(root);
-            if (remaining.length === 0) {
-                fs.rmdirSync(root);
-                log(`Removed empty ${root}`);
-                didSomething = true;
-            } else {
-                log(`Other uniner-cli versions still installed: ${remaining.join(', ')}`);
-                log(`Keeping ${root}`);
-            }
-        }
-    } catch (e) {
-        warn(`Could not inspect ${rootDir()}: ${e.message}`);
-    }
-
-    // 3. Remove ONLY the SKILL.md file. NEVER rm -rf the whole skill dir,
-    //    because the user's accumulated scenarios/<name>/ subdirectories
-    //    live there and represent real work they've sedimented over time.
-    //    If they really want everything gone they can do it manually; we
-    //    surface the path below so they know where to look.
-    const dir = skillDir();
-    if (rmFile(skillFile())) didSomething = true;
+// Fallback: the standalone script is gone (old install before this fix).
+// Use the in-package cleanup module.
+'use strict';
 
-    // 4. Look for scenarios/ — if there are any, keep them and tell the user.
-    let scenariosKept = 0;
-    const scenariosDir = path.join(dir, 'scenarios');
-    if (fs.existsSync(scenariosDir)) {
-        try {
-            scenariosKept = fs.readdirSync(scenariosDir).filter(n => {
-                const meta = path.join(scenariosDir, n, 'meta.json');
-                return fs.existsSync(meta);
-            }).length;
-        } catch (_) {
-            // best-effort
-        }
-    }
+const { cleanup } = require('../scripts/cleanup');
 
-    // 5. If skill dir is now genuinely empty, remove it. Otherwise keep it.
-    try {
-        if (fs.existsSync(dir)) {
-            const remaining = fs.readdirSync(dir);
-            if (remaining.length === 0) {
-                fs.rmdirSync(dir);
-                log(`Removed empty ${dir}`);
-                didSomething = true;
-            }
-        }
-    } catch (_) {
-        // best-effort
-    }
+console.log('');
+console.log('==========================================');
+console.log('  uniner-cli uninstall cleanup (fallback)');
+console.log('==========================================');
+console.log('');
+console.log('  Note: ~/.uniner-cli/cleanup.js not found.');
+console.log('  This fallback will be removed in a future version.');
+console.log('  Reinstall to get the standalone cleanup script:');
+console.log('    npm install -g uniner-cli');
+console.log('');
 
-    if (!didSomething) {
-        log('Nothing to clean — already removed.');
-    }
+const result = cleanup({ verbose: true });
 
-    console.log('');
-    if (scenariosKept > 0) {
-        console.log('==========================================');
-        console.log(`  ${scenariosKept} scenario(s) PRESERVED at:`);
-        console.log(`    ${scenariosDir}`);
-        console.log('  (your accumulated knowledge — not deleted)');
-        console.log('  To delete them too:');
-        console.log(`    rm -rf "${scenariosDir}"          # bash`);
-        console.log(`    Remove-Item "${scenariosDir}" -Recurse -Force   # PowerShell`);
-        console.log('==========================================');
-    }
-    console.log('Cleanup done. To complete uninstall, also run:');
-    console.log('  npm uninstall -g uniner-cli');
-    console.log('');
+console.log('');
+if (result.scenariosKept > 0) {
+    console.log('==========================================');
+    console.log(`  ${result.scenariosKept} scenario(s) PRESERVED at:`);
+    console.log(`    ${result.scenariosDir}`);
+    console.log('  (your accumulated knowledge — not deleted)');
+    console.log('  To delete them too:');
+    console.log(`    rm -rf "${result.scenariosDir}"          # bash`);
+    console.log(`    Remove-Item "${result.scenariosDir}" -Recurse -Force   # PowerShell`);
+    console.log('==========================================');
 }
 
-main();
+if (result.didSomething) {
+    console.log('Cleanup done.');
+} else {
+    console.log('Nothing to clean — already removed.');
+}
+console.log('');

package/bin/uniner-cli.js

@@ -1,15 +1,207 @@
 #!/usr/bin/env node
-// Tiny launcher: forward every CLI invocation to the real PyInstaller exe.
+// Tiny launcher: handle npm-owned commands, then forward everything else to
+// the real PyInstaller exe.
 //
 // `npm install -g uniner-cli` registers this file as the global `uniner-cli`
-// command (because of the `bin` entry in package.json). We just spawn the real
-// binary with the same argv/stdio and exit with its status code.
+// command (because of the `bin` entry in package.json).
 
 'use strict';
 
 const { spawnSync } = require('child_process');
 const fs = require('fs');
+const path = require('path');
 const { realBinaryPath, isInstalled, pkg } = require('../lib/paths');
+const { cleanup } = require('../scripts/cleanup');
+
+function npmCommand() {
+    return process.platform === 'win32' ? 'npm.cmd' : 'npm';
+}
+
+function printUninstallHelp() {
+    console.log('');
+    console.log('Usage: uniner-cli uninstall [--global|--local]');
+    console.log('');
+    console.log('Cleans ~/.uniner-cli and the installed Claude Code skill,');
+    console.log('then removes this npm package from the detected install scope.');
+    console.log('');
+}
+
+function realPath(p) {
+    try {
+        return fs.realpathSync.native(p);
+    } catch (_) {
+        return path.resolve(p);
+    }
+}
+
+function samePath(a, b) {
+    const left = realPath(a);
+    const right = realPath(b);
+    if (process.platform === 'win32') {
+        return left.toLowerCase() === right.toLowerCase();
+    }
+    return left === right;
+}
+
+function npmOutput(args, opts) {
+    const result = spawnSync(npmCommand(), args, Object.assign({
+        encoding: 'utf8',
+        shell: false,
+        windowsHide: false,
+    }, opts || {}));
+    if (result.error || result.status !== 0) {
+        return null;
+    }
+    return (result.stdout || '').trim();
+}
+
+function packageJsonHasDependency(file) {
+    try {
+        const parsed = JSON.parse(fs.readFileSync(file, 'utf8'));
+        const sections = [
+            parsed.dependencies,
+            parsed.devDependencies,
+            parsed.optionalDependencies,
+            parsed.peerDependencies,
+        ];
+        return sections.some(section => section && section[pkg.name]);
+    } catch (_) {
+        return false;
+    }
+}
+
+function findLocalProjectRoot(startDir) {
+    let dir = path.resolve(startDir);
+    while (true) {
+        const packageJson = path.join(dir, 'package.json');
+        if (fs.existsSync(packageJson) && packageJsonHasDependency(packageJson)) {
+            return dir;
+        }
+        const parent = path.dirname(dir);
+        if (parent === dir) {
+            return null;
+        }
+        dir = parent;
+    }
+}
+
+function localProjectFromPackageDir(packageDir) {
+    const nodeModulesDir = path.dirname(packageDir);
+    if (path.basename(nodeModulesDir) !== 'node_modules') {
+        return null;
+    }
+    const projectRoot = path.dirname(nodeModulesDir);
+    const packageJson = path.join(projectRoot, 'package.json');
+    if (fs.existsSync(packageJson)) {
+        return projectRoot;
+    }
+    return null;
+}
+
+function detectUninstallPlan(args) {
+    if (args.includes('--global') || args.includes('-g')) {
+        return {
+            scope: 'global',
+            npmArgs: ['uninstall', '-g', pkg.name],
+            cwd: process.cwd(),
+            manualCommand: `npm uninstall -g ${pkg.name}`,
+        };
+    }
+
+    if (args.includes('--local')) {
+        const projectRoot = findLocalProjectRoot(process.cwd()) ||
+            localProjectFromPackageDir(path.resolve(__dirname, '..')) ||
+            process.cwd();
+        return {
+            scope: 'local',
+            npmArgs: ['uninstall', pkg.name],
+            cwd: projectRoot,
+            manualCommand: `cd "${projectRoot}" && npm uninstall ${pkg.name}`,
+        };
+    }
+
+    const packageDir = path.resolve(__dirname, '..');
+    const globalRoot = npmOutput(['root', '-g']);
+    if (globalRoot && samePath(packageDir, path.join(globalRoot, pkg.name))) {
+        return {
+            scope: 'global',
+            npmArgs: ['uninstall', '-g', pkg.name],
+            cwd: process.cwd(),
+            manualCommand: `npm uninstall -g ${pkg.name}`,
+        };
+    }
+
+    const projectRoot = findLocalProjectRoot(process.cwd()) ||
+        localProjectFromPackageDir(packageDir);
+    if (projectRoot) {
+        return {
+            scope: 'local',
+            npmArgs: ['uninstall', pkg.name],
+            cwd: projectRoot,
+            manualCommand: `cd "${projectRoot}" && npm uninstall ${pkg.name}`,
+        };
+    }
+
+    return {
+        scope: 'global',
+        npmArgs: ['uninstall', '-g', pkg.name],
+        cwd: process.cwd(),
+        manualCommand: `npm uninstall -g ${pkg.name}`,
+    };
+}
+
+function runFullUninstall() {
+    console.log('');
+    console.log('==========================================');
+    console.log('  uniner-cli uninstall');
+    console.log('==========================================');
+
+    const cleanupResult = cleanup({ verbose: true });
+
+    console.log('');
+    const plan = detectUninstallPlan(process.argv.slice(3));
+    console.log(`[uniner-cli] Removing ${plan.scope} npm package...`);
+    if (plan.scope === 'local') {
+        console.log(`[uniner-cli] Project: ${plan.cwd}`);
+    }
+    const result = spawnSync(npmCommand(), plan.npmArgs, {
+        cwd: plan.cwd,
+        stdio: 'inherit',
+        shell: false,
+        windowsHide: false,
+    });
+
+    if (result.error) {
+        console.error('');
+        console.error(`[uniner-cli] Failed to run npm uninstall: ${result.error.message}`);
+        console.error('[uniner-cli] Runtime cleanup has already been attempted.');
+        console.error(`[uniner-cli] Please run manually: ${plan.manualCommand}`);
+        console.error('');
+        process.exit(1);
+    }
+
+    const status = result.status === null ? 1 : result.status;
+    if (status === 0) {
+        console.log('');
+        if (cleanupResult.scenariosKept > 0) {
+            console.log(`[uniner-cli] Preserved ${cleanupResult.scenariosKept} scenario(s) at:`);
+            console.log(`[uniner-cli]   ${cleanupResult.scenariosDir}`);
+        }
+        console.log('[uniner-cli] Uninstall complete.');
+        console.log('');
+    }
+    process.exit(status);
+}
+
+if (process.argv[2] === 'uninstall' &&
+    (process.argv[3] === '--help' || process.argv[3] === '-h')) {
+    printUninstallHelp();
+    process.exit(0);
+}
+
+if (process.argv[2] === 'uninstall') {
+    runFullUninstall();
+}
 
 const exe = realBinaryPath();
 

package/lib/SKILL.md.template

@@ -5,7 +5,7 @@ description: RPA 自动化 CLI 工具，提供浏览器自动化、Excel 操作
 
 # uniner-cli Skill
 
-> 由 UninerCLI Installer v{{VERSION}} 自动安装到 `%USERPROFILE%\.claude\skills\uniner-cli\`
+> 由 UninerCLI Installer v{{VERSION}} 自动安装到 `~/.claude/skills/uniner-cli/`
 > 安装位置（绝对路径）：`{{INSTALL_PATH}}`
 
 ## 🛑 任务结束硬性规则（最重要，先读这一节）
@@ -152,7 +152,7 @@ uniner-cli [全局选项] <模块> <子命令> <命令> [命令选项]
 ## 关键注意事项（6 条 TOC，详情看链接）
 
 1. **Chrome CDP 自动管理** — 别手动 kill Chrome；客户机必须装 Chrome 或 Edge
-2. **session 持久化** — `$TEMP\.uniner-cli\sessions.json`；CLI 退出后用 `web browser reconnect` 恢复
+2. **session 持久化** — `$TEMP/uniner-cli-sessions/sessions.json`（Windows: `%TEMP%\uniner-cli-sessions\sessions.json`）；CLI 退出后用 `web browser reconnect` 恢复
 3. **Vue/Element UI 组件** — 日期选择器、级联下拉等，用 `execute-js` 直接操作组件模型，不要硬 input
 4. **desktop 返回 -999** = Agent 服务未启动；此时改用 `web action execute-js` 或 `tool system execute`
 5. **Linux 平台** — Playwright 默认 HTTPS-only，访问 HTTP 站点需改 wrapper 加 `--disable-features=HttpsOnlyMode`，或用 Firefox `--browser-type 1`
@@ -162,14 +162,14 @@ uniner-cli [全局选项] <模块> <子命令> <命令> [命令选项]
 
 | 主题 | 路径 |
 |---|---|
-| 命令树全集 + 三级参数 | [{{INSTALL_PATH}}\skills\cli\SKILL.md]({{INSTALL_PATH}}\skills\cli\SKILL.md) |
-| SDK ↔ CLI 命令映射 | [{{INSTALL_PATH}}\skills\cli\sdk-cli-mapping.md]({{INSTALL_PATH}}\skills\cli\sdk-cli-mapping.md) |
-| Windows 配置指南 | [{{INSTALL_PATH}}\skills\windows-setup-guide.md]({{INSTALL_PATH}}\skills\windows-setup-guide.md) |
-| Linux 配置指南 | [{{INSTALL_PATH}}\skills\linux-setup-guide.md]({{INSTALL_PATH}}\skills\linux-setup-guide.md) |
-| 实战案例（TMS 抓单） | [{{INSTALL_PATH}}\skills\tms-workflow-test-report.md]({{INSTALL_PATH}}\skills\tms-workflow-test-report.md) |
-| Helper 脚本（Chrome 启动 / Vue 日期 / 表格提取） | [{{INSTALL_PATH}}\skills\cli\helpers\]({{INSTALL_PATH}}\skills\cli\helpers\) |
-| 用户手册 | [{{INSTALL_PATH}}\docs\]({{INSTALL_PATH}}\docs\) |
-| 工作目录（保存截图/Excel/下载） | [{{INSTALL_PATH}}\workdir\]({{INSTALL_PATH}}\workdir\) |
+| 命令树全集 + 三级参数 | [{{INSTALL_PATH}}/skills/cli/SKILL.md]({{INSTALL_PATH}}/skills/cli/SKILL.md) |
+| SDK ↔ CLI 命令映射 | [{{INSTALL_PATH}}/skills/cli/sdk-cli-mapping.md]({{INSTALL_PATH}}/skills/cli/sdk-cli-mapping.md) |
+| Windows 配置指南 | [{{INSTALL_PATH}}/skills/windows-setup-guide.md]({{INSTALL_PATH}}/skills/windows-setup-guide.md) |
+| Linux 配置指南 | [{{INSTALL_PATH}}/skills/linux-setup-guide.md]({{INSTALL_PATH}}/skills/linux-setup-guide.md) |
+| 实战案例（TMS 抓单） | [{{INSTALL_PATH}}/skills/tms-workflow-test-report.md]({{INSTALL_PATH}}/skills/tms-workflow-test-report.md) |
+| Helper 脚本（Chrome 启动 / Vue 日期 / 表格提取） | [{{INSTALL_PATH}}/skills/cli/helpers/]({{INSTALL_PATH}}/skills/cli/helpers/) |
+| 用户手册 | [{{INSTALL_PATH}}/docs/]({{INSTALL_PATH}}/docs/) |
+| 工作目录（保存截图/Excel/下载） | [{{INSTALL_PATH}}/workdir/]({{INSTALL_PATH}}/workdir/) |
 
 ## 典型完整流程（参考）
 
@@ -182,8 +182,8 @@ uniner-cli web browser open --url "https://example.com/login"
 # 2. 输账号密码 + 截验证码 + OCR
 uniner-cli web element input --xpath "//input[@id='user']" --value "u01"
 uniner-cli web element input --xpath "//input[@id='pwd']" --value "p01"
-uniner-cli web element screenshot --xpath "//img[@id='captcha']" --output "{{INSTALL_PATH}}\workdir\cap.png"
-uniner-cli tool ocr ddddocr --img "{{INSTALL_PATH}}\workdir\cap.png"
+uniner-cli web element screenshot --xpath "//img[@id='captcha']" --output "{{INSTALL_PATH}}/workdir/cap.png"
+uniner-cli tool ocr ddddocr --img "{{INSTALL_PATH}}/workdir/cap.png"
 # 从返回 JSON 的 data.result 取识别文本
 
 # 3. 提交登录
@@ -195,8 +195,8 @@ uniner-cli web navigation wait --type element --xpath "//table"
 uniner-cli web action execute-js --code "return Array.from(document.querySelectorAll('table tr')).map(r => Array.from(r.cells).map(c => c.textContent.trim()))"
 
 # 5. 写 Excel
-uniner-cli excel file create --file "{{INSTALL_PATH}}\workdir\out.xlsx"
-uniner-cli excel data write-range --file "{{INSTALL_PATH}}\workdir\out.xlsx" --cell A1 --values "<上一步的 JSON 二维数组>"
+uniner-cli excel file create --file "{{INSTALL_PATH}}/workdir/out.xlsx"
+uniner-cli excel data write-range --file "{{INSTALL_PATH}}/workdir/out.xlsx" --cell A1 --values "<上一步的 JSON 二维数组>"
 
 # 6. 关浏览器
 uniner-cli web browser close
@@ -209,9 +209,11 @@ uniner-cli web browser close
 每个场景一个目录，三件套：`meta.json` + `steps.json` + `SKILL.md`，存到：
 
 ```
-%USERPROFILE%\.claude\skills\uniner-cli\scenarios\<kebab-case-name>\
+~/.claude/skills/uniner-cli/scenarios/<kebab-case-name>/
 ```
 
+（Windows: `%USERPROFILE%\.claude\skills\uniner-cli\scenarios\<kebab-case-name>\`）
+
 **4 步标准流程**：
 
 ```bash
@@ -331,7 +333,7 @@ Open Claude Code, paste this:
    I ran 'uniner-cli skill run' and step 'click-search' failed.
    Error: timeout
    Please look at the scenario at:
-     C:\Users\xxx\.claude\skills\uniner-cli\scenarios\tms-export
+     ~/.claude/skills/uniner-cli/scenarios/tms-export
    Especially steps.json. Help me figure out why and suggest a fix.
 ──────────────────────────────────
 ```
@@ -368,4 +370,4 @@ uniner-cli skill delete <name> --yes   # 删除（默认 dry-run）
 - `uniner-cli --help` 看一级
 - `uniner-cli web --help` 看二级
 - `uniner-cli web element click --help` 看具体参数
-- 仍不确定 → Read [{{INSTALL_PATH}}\skills\cli\SKILL.md]({{INSTALL_PATH}}\skills\cli\SKILL.md)
+- 仍不确定 → Read [{{INSTALL_PATH}}/skills/cli/SKILL.md]({{INSTALL_PATH}}/skills/cli/SKILL.md)

package/package.json

@@ -1,6 +1,6 @@
 {
     "name":  "uniner-cli",
-    "version":  "1.0.5",
+    "version":  "1.0.7",
     "description":  "uniner-cli — RPA automation CLI: browser automation (Playwright/CDP), Excel, OCR, desktop/SAP, crypto/HTTP/email tools. Auto-installs a Claude Code skill on install.",
     "keywords":  [
                      "rpa",
@@ -25,7 +25,8 @@
                 "uniner-cli-uninstall":  "bin/uniner-cli-uninstall.js"
             },
     "scripts":  {
-                    "postinstall":  "node scripts/postinstall.js"
+                    "postinstall":   "node scripts/postinstall.js",
+                    "preuninstall":  "node scripts/preuninstall.js"
                 },
     "engines":  {
                     "node":  "\u003e=14"
@@ -46,4 +47,4 @@
                   "README.md",
                   "LICENSE"
               ]
-}
+}

package/scripts/cleanup.js

@@ -0,0 +1,123 @@
+// Shared cleanup logic for uninstall.
+// Extracted so both the npm lifecycle hook (preuninstall.js) and the
+// manual command (bin/uniner-cli-uninstall.js) can share it.
+
+'use strict';
+
+const fs   = require('fs');
+const path = require('path');
+
+const {
+    rootDir,
+    skillDir,
+    skillFile,
+} = require('../lib/paths');
+
+function rmRf(p) {
+    try {
+        if (fs.existsSync(p)) {
+            fs.rmSync(p, { recursive: true, force: true });
+            return true;
+        }
+        return false;
+    } catch (_) {
+        return false;
+    }
+}
+
+function rmFile(p) {
+    try {
+        if (fs.existsSync(p)) {
+            fs.unlinkSync(p);
+            return true;
+        }
+        return false;
+    } catch (_) {
+        return false;
+    }
+}
+
+/**
+ * Run the full uninstall cleanup.
+ *
+ * @param {object}  [opts]
+ * @param {boolean} [opts.verbose=false]  Print progress lines to stdout.
+ *                                         The preuninstall hook should pass false
+ *                                         because npm swallows lifecycle output
+ *                                         unless --verbose is used; the manual
+ *                                         command passes true so the user sees
+ *                                         what happened.
+ * @returns {{ didSomething: boolean, scenariosKept: number, scenariosDir: string|null }}
+ */
+function cleanup(opts) {
+    const verbose = (opts && opts.verbose) || false;
+
+    function log(msg) {
+        if (verbose) {
+            console.log(`[uniner-cli] ${msg}`);
+        }
+    }
+
+    const root = rootDir();
+    let didSomething = false;
+
+    // 1. Remove the entire ~/.uniner-cli/ tree (all versions).
+    //    The version-specific layout exists so the installer can support
+    //    multi-version coexistence, but on uninstall the user wants a full
+    //    removal — orphaned old version dirs would just waste disk space.
+    if (rmRf(root)) {
+        log(`Removed ${root}`);
+        didSomething = true;
+    }
+
+    // 2. Remove ONLY the SKILL.md file. NEVER rm -rf the whole skill dir,
+    //    because the user's accumulated scenarios/<name>/ subdirectories
+    //    live there and represent real work they've sedimented over time.
+    const dir = skillDir();
+    if (rmFile(skillFile())) {
+        log(`Removed ${skillFile()}`);
+        didSomething = true;
+    }
+
+    // 3. Count scenarios/ subdirs that contain a meta.json.
+    let scenariosKept   = 0;
+    const scenariosPath = path.join(dir, 'scenarios');
+    if (fs.existsSync(scenariosPath)) {
+        try {
+            scenariosKept = fs.readdirSync(scenariosPath).filter(n => {
+                const meta = path.join(scenariosPath, n, 'meta.json');
+                return fs.existsSync(meta);
+            }).length;
+        } catch (_) {
+            // best-effort
+        }
+    }
+
+    // 4. If skill dir is now genuinely empty, remove it. Otherwise keep it.
+    try {
+        if (fs.existsSync(dir)) {
+            const remaining = fs.readdirSync(dir);
+            if (remaining.length === 0) {
+                fs.rmdirSync(dir);
+                log(`Removed empty ${dir}`);
+                didSomething = true;
+            } else if (verbose) {
+                log(`Keeping ${dir} (${scenariosKept} scenario(s) preserved)`);
+            }
+        }
+    } catch (_) {
+        // best-effort
+    }
+
+    if (!didSomething) {
+        log('Nothing to clean — already removed.');
+    }
+
+    return {
+        didSomething,
+        scenariosKept,
+        scenariosDir: scenariosKept > 0 ? scenariosPath : null,
+    };
+}
+
+module.exports = { cleanup };

package/scripts/postinstall.js

@@ -28,6 +28,7 @@ const { spawnSync } = require('child_process');
 
 const {
     pkg,
+    rootDir,
     versionDir,
     realBinaryPath,
     isInstalled,
@@ -237,6 +238,159 @@ function writeSkillMd(installPath, version) {
     }
 }
 
+// ----------------------------------------------------------------------
+// Write standalone cleanup script to ~/.uniner-cli/cleanup.js
+//
+// npm 7+ no longer reliably runs `preuninstall` hooks for global packages,
+// so `npm uninstall -g uniner-cli` leaves ~/.uniner-cli/ and the SKILL.md
+// behind. To give users a reliable cleanup path, we write a self-contained
+// cleanup script to ~/.uniner-cli/cleanup.js during install. This file lives
+// OUTSIDE the npm package directory, so it survives `npm uninstall`.
+//
+// Usage after `npm uninstall -g uniner-cli`:
+//   node ~/.uniner-cli/cleanup.js
+// ----------------------------------------------------------------------
+
+function writeCleanupScript() {
+    const root = path.join(os.homedir(), '.uniner-cli');
+    const cleanupPath = path.join(root, 'cleanup.js');
+
+    // NOTE: this string is written verbatim to disk — no require(), no
+    // imports, no template tokens. It must be 100% self-contained Node.js.
+    const script = `#!/usr/bin/env node
+// cleanup.js — uninstall cleanup for uniner-cli.
+//
+// WHY THIS FILE EXISTS
+// --------------------
+// npm 7+ (including npm 11) does NOT reliably execute the \`preuninstall\`
+// lifecycle hook for globally installed packages. Running
+// \`npm uninstall -g uniner-cli\` removes the npm package but leaves:
+//   - ~/.uniner-cli/           (runtime binaries, skills, docs)
+//   - ~/.claude/skills/uniner-cli/SKILL.md  (Claude Code skill file)
+//
+// This script was written to this location by the postinstall hook. Because
+// it lives OUTSIDE the npm package directory, it survives \`npm uninstall\`
+// and can always be invoked manually:
+//
+//   node ~/.uniner-cli/cleanup.js
+//
+// Idempotent: running it twice is harmless; the second run just reports
+// "nothing to clean".
+//
+// WHAT IT PRESERVES
+// -----------------
+// The \`scenarios/\` subdirectory under
+//   ~/.claude/skills/uniner-cli/scenarios/
+// contains user-accumulated knowledge (saved workflows). Those are NEVER
+// deleted by this script — only the single SKILL.md file is removed.
+
+'use strict';
+
+const fs   = require('fs');
+const path = require('path');
+const os   = require('os');
+
+const rootDir      = path.join(os.homedir(), '.uniner-cli');
+const claudeSkillRoot = path.join(os.homedir(), '.claude', 'skills', 'uniner-cli');
+const skillFilePath   = path.join(claudeSkillRoot, 'SKILL.md');
+const scenariosDir    = path.join(claudeSkillRoot, 'scenarios');
+
+function rmRf(p) {
+    try {
+        if (fs.existsSync(p)) {
+            fs.rmSync(p, { recursive: true, force: true });
+            return true;
+        }
+        return false;
+    } catch (_) { return false; }
+}
+
+function rmFile(p) {
+    try {
+        if (fs.existsSync(p)) {
+            fs.unlinkSync(p);
+            return true;
+        }
+        return false;
+    } catch (_) { return false; }
+}
+
+console.log('');
+console.log('==========================================');
+console.log('  uniner-cli uninstall cleanup');
+console.log('==========================================');
+
+let didSomething = false;
+
+// 1. Remove entire ~/.uniner-cli/ tree (all versions + this script itself).
+if (rmRf(rootDir)) {
+    console.log('[uniner-cli] Removed ' + rootDir);
+    didSomething = true;
+}
+
+// 2. Remove ONLY the SKILL.md file. NEVER rm -rf the whole skill dir —
+//    scenarios/ lives there and is the user's accumulated knowledge.
+if (rmFile(skillFilePath)) {
+    console.log('[uniner-cli] Removed ' + skillFilePath);
+    didSomething = true;
+}
+
+// 3. Count preserved scenarios.
+let scenariosKept = 0;
+if (fs.existsSync(scenariosDir)) {
+    try {
+        scenariosKept = fs.readdirSync(scenariosDir).filter(function(n) {
+            return fs.existsSync(path.join(scenariosDir, n, 'meta.json'));
+        }).length;
+    } catch (_) {}
+}
+
+// 4. If the skill dir is now empty, remove it. Otherwise keep it.
+try {
+    if (fs.existsSync(claudeSkillRoot)) {
+        var remaining = fs.readdirSync(claudeSkillRoot);
+        if (remaining.length === 0) {
+            fs.rmdirSync(claudeSkillRoot);
+            console.log('[uniner-cli] Removed empty ' + claudeSkillRoot);
+            didSomething = true;
+        } else if (scenariosKept > 0) {
+            console.log('[uniner-cli] Keeping ' + claudeSkillRoot +
+                        ' (' + scenariosKept + ' scenario(s) preserved)');
+        }
+    }
+} catch (_) {}
+
+console.log('');
+if (scenariosKept > 0) {
+    console.log('  ' + scenariosKept + ' scenario(s) PRESERVED at:');
+    console.log('    ' + scenariosDir);
+    console.log('  (your accumulated knowledge — not deleted)');
+    console.log('  To delete them too:');
+    console.log('    rm -rf "' + scenariosDir + '"          # bash');
+    console.log('    Remove-Item "' + scenariosDir + '" -Recurse -Force   # PowerShell');
+    console.log('');
+}
+
+if (didSomething) {
+    console.log('Cleanup done.');
+} else {
+    console.log('Nothing to clean — already removed.');
+}
+console.log('');
+`;
+
+    try {
+        fs.mkdirSync(root, { recursive: true });
+        fs.writeFileSync(cleanupPath, script, 'utf8');
+        log(`Uninstall cleanup helper written to ${cleanupPath}`);
+        log(`  After \`npm uninstall -g uniner-cli\`, run:`);
+        log(`    node ${cleanupPath}`);
+    } catch (e) {
+        // Non-fatal: cleanup.js is a convenience, not required for install to succeed.
+        log(`[WARN] Could not write cleanup helper: ${e.message}`);
+    }
+}
+
 // ----------------------------------------------------------------------
 // Main
 // ----------------------------------------------------------------------
@@ -267,6 +421,9 @@ async function main() {
         // Still re-render the skill — it's tiny and lets users edit the template
         // and re-run rebuild to refresh.
         writeSkillMd(versionDir(version), version);
+        // Refresh the cleanup helper too — it's idempotent and ensures the
+        // script is always present after any postinstall run.
+        writeCleanupScript();
         return;
     }
 
@@ -344,6 +501,13 @@ async function main() {
     step('Installing Claude Code skill');
     writeSkillMd(targetDir, version);
 
+    // Write the standalone cleanup helper to ~/.uniner-cli/cleanup.js.
+    // This survives `npm uninstall` (the npm package dir is gone but this
+    // file persists), giving users a reliable way to clean up residual
+    // files even when the `preuninstall` hook doesn't fire.
+    step('Writing uninstall cleanup helper');
+    writeCleanupScript();
+
     console.log('');
     console.log('==========================================');
     console.log(`  uniner-cli ${version} installed`);
@@ -352,6 +516,10 @@ async function main() {
     console.log(`  Location: ${targetDir}`);
     console.log(`  Skill:    ${skillFile()}`);
     console.log('');
+    console.log('  To uninstall:');
+    console.log('    uniner-cli uninstall   # auto-detects global vs local install');
+    console.log(`    node ${path.join(rootDir(), 'cleanup.js')}   # fallback cleanup after npm uninstall`);
+    console.log('');
 
     // macOS 首次运行提示（无代码签名）
     if (platformInfo.platform === 'darwin') {

package/scripts/preuninstall.js

@@ -0,0 +1,25 @@
+#!/usr/bin/env node
+// preuninstall.js — npm lifecycle hook, runs automatically on
+// `npm uninstall -g uniner-cli`.
+//
+// Cleans up the runtime tree (~/.uniner-cli/<version>/) and the skill file
+// (~/.claude/skills/uniner-cli/SKILL.md). Preserves user scenarios under
+// ~/.claude/skills/uniner-cli/scenarios/ — those represent accumulated
+// knowledge and are never deleted automatically.
+//
+// IMPORTANT: This script MUST exit 0 in all cases, otherwise it would
+// abort the user's `npm uninstall`. Errors are swallowed silently.
+//
+// The manual `uniner-cli-uninstall` command is still useful for users who
+// want verbose feedback, or who want to clean up before the npm package is
+// gone (e.g. if the hook somehow didn't fire).
+
+'use strict';
+
+const { cleanup } = require('./cleanup');
+
+try {
+    cleanup({ verbose: false });
+} catch (_) {
+    // Never fail the uninstall — swallow all errors.
+}