uniner-cli 1.0.24 → 1.0.26

package/README.md

@@ -8,7 +8,7 @@
 - **桌面 / SAP 自动化** —— 支持桌面软件的自动化（仅 Windows）
 - **通用工具** —— 加密、HTTP、邮件、文件、PDF、压缩、FTP
 
-安装时会自动注册一个 [Claude Code](https://claude.com/claude-code) 技能（`~/.claude/skills/uniner-cli/SKILL.md`），让 Claude 一启动就能识别并调用本 CLI。
+在项目目录运行 `uniner-cli setup-for-agent` 可把 skill 文档部署到该项目 `.agents/skills/`，Claude Code / Codex / pi 等 Agent 即可识别并调用本 CLI。
 
 ---
 
@@ -112,10 +112,9 @@ uniner-cli uninstall --local
 
 清理内容：
 
-- `~/.uniner-cli/` 整个运行时目录（含所有版本）
-- `~/.claude/skills/uniner-cli/SKILL.md` 技能文件
+- `~/.uniner-cli/` 整个运行时目录（含所有版本、文档与场景库 `scenarios/`）
 
-> `~/.claude/skills/uniner-cli/scenarios/` 下用户积累的场景数据不会被删除，需手动清理。
+> 项目里的 `.agents/skills/`（`setup-for-agent` 部署）与 `.claude/skills/` 桥接在用户项目内，卸载不会触碰，不需要时请自行删除。
 
 **备选方式**（如果 npm 包已经先被卸载，`uniner-cli` 不在 PATH 上）：
 

package/bin/uniner-cli-uninstall.js

@@ -6,8 +6,7 @@
 //   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)
+//     - ~/.uniner-cli/            (runtime binaries, skills, docs, scenarios)
 //
 // To solve this, postinstall writes a self-contained cleanup script to
 // ~/.uniner-cli/cleanup.js. That file survives `npm uninstall` and can
@@ -36,7 +35,7 @@ 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/.
+    // the ~/.uniner-cli/ tree (binaries, docs, scenarios).
     // Use spawnSync to avoid any require() path issues.
     const { spawnSync } = require('child_process');
     const result = spawnSync(process.execPath, [standalonePath], {
@@ -65,17 +64,6 @@ console.log('');
 const result = cleanup({ verbose: true });
 
 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('==========================================');
-}
-
 if (result.didSomething) {
     console.log('Cleanup done.');
 } else {

package/bin/uniner-cli.js

@@ -21,7 +21,7 @@ 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('Cleans ~/.uniner-cli (binaries, docs, scenarios),');
     console.log('then removes this npm package from the detected install scope.');
     console.log('');
 }
@@ -196,10 +196,6 @@ function runFullUninstall() {
     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('');
     }

package/lib/paths.js

@@ -44,19 +44,6 @@ function realBinaryPath(version) {
     return path.join(versionDir(ver), 'bin', 'uniner-cli', 'uniner-cli');
 }
 
-function skillDir() {
-    // Same place Claude Code looks for user-global skills.
-    return path.join(homeDir(), '.claude', 'skills', 'uniner-cli');
-}
-
-function skillFile() {
-    return path.join(skillDir(), 'SKILL.md');
-}
-
-function templatePath() {
-    return path.join(__dirname, 'SKILL.md.template');
-}
-
 function isInstalled(version) {
     try {
         return fs.statSync(realBinaryPath(version)).isFile();
@@ -71,8 +58,5 @@ module.exports = {
     rootDir,
     versionDir,
     realBinaryPath,
-    skillDir,
-    skillFile,
-    templatePath,
     isInstalled,
 };

package/package.json

@@ -1,7 +1,7 @@
 {
     "name": "uniner-cli",
-    "version": "1.0.24",
-    "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.",
+    "version": "1.0.26",
+    "description": "uniner-cli — RPA automation CLI: browser automation (Playwright/CDP), Excel, OCR, desktop/SAP, crypto/HTTP/email tools. Deploy Agent skills to your project via `uniner-cli setup-for-agent`.",
     "keywords": [
         "rpa",
         "automation",
@@ -9,7 +9,10 @@
         "playwright",
         "excel",
         "ocr",
+        "agent-skills",
         "claude-code",
+        "codex",
+        "pi",
         "ai-agent"
     ],
     "homepage": "https://www.uniner.com/",

package/scripts/cleanup.js

@@ -1,123 +1,68 @@
-// 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 };
+// 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.
+//
+// Full removal: ~/.uniner-cli/ holds binaries, docs AND the scenarios
+// library (moved out of ~/.claude/ in 1.0.25), so deleting the whole tree
+// is the correct uninstall semantics. Project-level .agents/skills/ and
+// .claude/ bridges created by `uniner-cli setup-for-agent` live inside
+// user projects and are intentionally NOT touched here.
+
+'use strict';
+
+const fs = require('fs');
+
+const {
+    rootDir,
+} = 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;
+    }
+}
+
+/**
+ * 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 }}
+ */
+function cleanup(opts) {
+    const verbose = (opts && opts.verbose) || false;
+
+    function log(msg) {
+        if (verbose) {
+            console.log(`[uniner-cli] ${msg}`);
+        }
+    }
+
+    const root = rootDir();
+
+    // Remove the entire ~/.uniner-cli/ tree (all versions, scenarios, docs).
+    // 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.
+    const didSomething = rmRf(root);
+    if (didSomething) {
+        log(`Removed ${root}`);
+    } else {
+        log('Nothing to clean — already removed.');
+    }
+
+    return { didSomething };
+}
+
+module.exports = { cleanup };

package/scripts/postinstall.js

@@ -9,9 +9,7 @@
 //      - Up to 3 retries with exponential backoff.
 //   4. Verify SHA-256.
 //   5. Extract via PowerShell's Expand-Archive (no native dep).
-//   6. Render SKILL.md.template with {{INSTALL_PATH}} / {{VERSION}} substituted
-//      and write to ~/.claude/skills/uniner-cli/SKILL.md.
-//   7. Print "ready" and how to validate.
+//   6. Print "ready", how to enable the Agent skill (setup-for-agent), validate.
 //
 // Failures throw -> non-zero exit -> npm marks install as failed (strict mode).
 // User can then `npm install -g uniner-cli` again to retry cleanly.
@@ -32,9 +30,6 @@ const {
     versionDir,
     realBinaryPath,
     isInstalled,
-    skillDir,
-    skillFile,
-    templatePath,
 } = require('../lib/paths');
 
 const {
@@ -196,48 +191,6 @@ function sha256OfFile(file) {
     });
 }
 
-// ----------------------------------------------------------------------
-// SKILL.md template render
-// ----------------------------------------------------------------------
-
-function writeSkillMd(installPath, version) {
-    const tplPath = templatePath();
-    if (!fs.existsSync(tplPath)) {
-        log(`    [WARN] SKILL.md.template missing at ${tplPath}; skipping skill install.`);
-        return;
-    }
-    let content = fs.readFileSync(tplPath, 'utf8');
-    // PowerShell-side StringChangeEx is case-insensitive; here we keep it strict
-    // because our template uses exactly these tokens.
-    content = content.split('{{INSTALL_PATH}}').join(installPath);
-    content = content.split('{{VERSION}}').join(version);
-
-    const dir = skillDir();
-    fs.mkdirSync(dir, { recursive: true });
-
-    // IMPORTANT: only writeFileSync the single SKILL.md file. Do NOT touch
-    // anything else under ~/.claude/skills/uniner-cli/. In particular, the
-    // scenarios/ subdirectory is the user's accumulated knowledge — if we
-    // ever rmdir or rmSync this directory we'd wipe their library on every
-    // upgrade. Single-file write is the contract.
-    fs.writeFileSync(skillFile(), content, 'utf8');
-    log(`    SKILL.md written to ${skillFile()}`);
-
-    // Tell the user we kept their scenarios (if any).
-    const scenariosDir = path.join(dir, 'scenarios');
-    if (fs.existsSync(scenariosDir)) {
-        try {
-            const count = fs.readdirSync(scenariosDir).filter(n => {
-                const meta = path.join(scenariosDir, n, 'meta.json');
-                return fs.existsSync(meta);
-            }).length;
-            log(`    [INFO] Preserved ${count} scenario(s) in ${scenariosDir}`);
-        } catch (_) {
-            // best-effort; never fail postinstall over a logging stat
-        }
-    }
-}
-
 // ----------------------------------------------------------------------
 // Write standalone cleanup script to ~/.uniner-cli/cleanup.js
 //
@@ -264,9 +217,8 @@ function writeCleanupScript() {
 // --------------------
 // 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)
+// \`npm uninstall -g uniner-cli\` removes the npm package but leaves
+// ~/.uniner-cli/ (runtime binaries, skills, docs, scenarios).
 //
 // This script was written to this location by the postinstall hook. Because
 // it lives OUTSIDE the npm package directory, it survives \`npm uninstall\`
@@ -276,24 +228,14 @@ function writeCleanupScript() {
 //
 // 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 fs = require('fs');
 const path = require('path');
-const os   = require('os');
+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');
+const rootDir = path.join(os.homedir(), '.uniner-cli');
 
 function rmRf(p) {
     try {
@@ -305,73 +247,14 @@ function rmRf(p) {
     } 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.');
@@ -418,9 +301,6 @@ async function main() {
         log(`Already installed at ${realBinaryPath(version)}; skipping download.`);
         log('To force a clean reinstall:');
         log('  npm uninstall -g uniner-cli && npm install -g uniner-cli');
-        // 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();
@@ -498,13 +378,6 @@ async function main() {
     try { fs.rmdirSync(tmpDir); } catch (_) {}
     log('    Removed temporary files.');
 
-    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();
 
@@ -514,7 +387,10 @@ async function main() {
     console.log('==========================================');
     console.log('');
     console.log(`  Location: ${targetDir}`);
-    console.log(`  Skill:    ${skillFile()}`);
+    console.log('');
+    console.log('  Enable the Agent skill (Claude Code / Codex / pi):');
+    console.log('    cd <your-project-dir>');
+    console.log('    uniner-cli setup-for-agent');
     console.log('');
     console.log('  To uninstall:');
     console.log('    uniner-cli uninstall   # auto-detects global vs local install');

package/scripts/preuninstall.js

@@ -2,10 +2,10 @@
 // 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.
+// Cleans up the runtime tree (~/.uniner-cli/ — binaries, docs, scenarios;
+// full removal). Project-level .agents/skills/ and .claude/ bridges created
+// by `uniner-cli setup-for-agent` live inside user projects and are not
+// touched.
 //
 // IMPORTANT: This script MUST exit 0 in all cases, otherwise it would
 // abort the user's `npm uninstall`. Errors are swallowed silently.

package/lib/SKILL.md.template

@@ -1,404 +0,0 @@
----
-name: uniner-cli
-description: RPA 自动化 CLI 工具，提供浏览器自动化、Excel 操作、OCR 识别、魔像云流程开发与发布（流程发布/上传流程/魔微子）、加密/HTTP/邮件等通用工具能力。Use when user mentions RPA、自动化、抓取网页、抓数据、填表、读 Excel、写 Excel、识别验证码、OCR、流程发布、上传流程、业务流程、魔像云、魔微子、uniner-cli、爬虫、表单自动化.
----
-
-# uniner-cli Skill
-
-> 由 UninerCLI Installer v{{VERSION}} 自动安装到 `~/.claude/skills/uniner-cli/`
-> 安装位置（绝对路径）：`{{INSTALL_PATH}}`
-
-## 🛑 任务结束硬性规则（最重要，先读这一节）
-
-**每次用 uniner-cli 完成一个任务后，在你要说"任务完成"或写汇总表之前，必须先执行下面这段：**
-
-如果这次任务**满足任一条件**：
-
-- 调用了 ≥ 3 个 uniner-cli 命令
-- 涉及 web / OCR 任何一个模块（desktop 暂不开放，不在其列）
-- 涉及魔像云流程开发（init/validate/publish 多步链路，沉淀后可 0 token 重放）
-- 用户提到过"以后还会跑" / "每天都要" / "做成自动化"
-- 任务里踩过坑（XPath 不稳、参数名错、Vue 组件、超时调整等）
-
-→ **必须主动问用户**："这个流程涉及多步，要不要保存为可重放场景？以后 `uniner-cli skill run <name> --param ...` 就能 0 token 重放，可以放定时任务/RPA 平台里跑。要保存吗？"
-
-不要等用户开口，**主动**问。这是最有价值的一步——你刚刚花了上千 token 调通的流程，沉淀下来下次就能秒跑。
-
-如果用户说"好" / "可以" / "保存吧"：按下面"场景沉淀（4 步流程）"章节执行。
-
-如果用户说"不用"：直接结束，不再追问。
-
-**违反这条规则 = 任务未完成。** 不管你跑得多顺，没问就是没问完整。
-
----
-
-## 何时使用本 Skill
-
-用户提到以下任一关键词或任务，**优先调用 uniner-cli**：
-
-- **网页类**：打开网页、抓取数据、点击/填表/登录、获取标题/表格、OCR 验证码
-- **Excel 类**：创建/读写 Excel、单元格操作、批量数据导出
-- **工具类**：MD5/AES/RSA 加密、HTTP 请求、收发邮件、文件/PDF/ZIP 操作
-
-## 调用前提（已自动配置）
-
-- ✅ `uniner-cli` 命令已加入 PATH（安装时自动配置，新终端立即生效）
-- ✅ 环境变量 `UNINER_CLI_HOME = {{INSTALL_PATH}}`
-- ✅ Web 模块自动通过 CDP 连接本机 Chrome / Edge —— **不要手动启动 Chrome**
-- ⚠️ desktop 模块**暂不开放**（测试覆盖少）；桌面/SAP 场景告知用户后改用 web 或 tool system execute
-
-## 命令结构（一级 + 二级）
-
-```
-uniner-cli <模块> <子模块> <命令> [选项]
-
-excel              Excel 文件操作
-├── file           创建 / 打开 / 关闭 / 保存 / 复制 / 删除 / info / list
-├── sheet          工作表 创建 / 删除 / 重命名 / 复制 / info / list
-├── data           读 / 写 / 区域读 / 区域写 / 查找 / 清除
-└── style          字体 / 边框 / 填充 / 对齐 / 数字格式
-
-web                浏览器自动化（Playwright + CDP）
-├── browser        open / close / reconnect
-├── navigation     goto / back / forward / refresh / wait
-├── element        click / input / get-text / get-value / select / check / hover / screenshot
-├── iframe         enter / exit / list
-├── page           list / switch / close
-└── action         screenshot / pdf / execute-js / get-cookie / set-cookie
-
-tool               通用工具
-├── list           创建 / append / remove / find / sort / unique
-├── dict           创建 / get / set / remove / keys / values
-├── time           now / format / parse / calc / diff
-├── string         format / replace / split / join / trim / upper / lower
-├── data           json-parse / json-stringify / csv-parse / csv-write
-├── file           read / write / copy / move / delete / list / info / exists
-├── system         execute / kill-app / env / clipboard      [Windows]
-├── ui             alert / confirm / prompt                   [Windows]
-├── crypto         md5 / sha256 / aes-encrypt / aes-decrypt / rsa-* / base64-*
-├── math           add / sub / mul / div / round / abs / min / max
-├── pdf            read / merge / split / extract-text
-├── ocr            ddddocr（验证码） / paddleocr（通用） / image-to-text
-├── zip            create / extract / list
-├── ftp            connect / upload / download / list / delete
-├── email          send / receive / list
-└── http           get / post / put / delete
-
-desktop            桌面自动化 [暂不开放] —— 测试覆盖少，当前版本未开放。
-                   AI 检测到任务需要桌面/SAP 操作时：停下告知用户"desktop 模块
-                   暂不开放"，改用 web（浏览器场景）或 tool system execute
-                   （执行外部程序），不要尝试调用 desktop 命令。
-
-cloud              魔像云操作（编辑器账号登录态；见"魔像云流程"章节）
-├── login          登录（多组织时交互列出、**必须用户本人输入序号选定**）
-├── logout         登出
-├── status         查看登录状态（含当前组织）
-└── flow           流程管理
-    ├── init       生成流程脚手架（无参 = 当前目录五件套、流程名=目录名；--dir <路径> 指定目录自动创建；init <流程名> 已废弃）
-    ├── validate   基础检查流程目录（publish 时自动执行，也可单独运行）
-    ├── test       本地真跑流程（不强制，建议发布前手动跑）
-    ├── list-local 列本地流程、发布状态与绑定组织
-    ├── list       列云端流程（标注来源 CLI / 编辑器）
-    ├── publish    发布流程目录（自动 validate + 版本号用户确认 + 外发确认）
-    ├── download   下载云端流程回流当前目录（覆盖前确认，默认 N）
-    └── pack       打包当前目录流程为 .7z（无参数，输出上级目录）
-
-config             配置管理
-├── set            设置配置项（仅 editor.path：魔微子安装目录）
-├── list           查看当前配置
-└── clear          清除配置
-```
-
-## 全局选项（写在子命令前）
-
-```bash
-uniner-cli [全局选项] <模块> <子命令> <命令> [命令选项]
-
---timeout, -t <毫秒>    超时（默认 3000ms）
---exc <0|1>             异常处理：0=抛错退出，1=静默返回错误 JSON
---verbose, -v           详细日志
---quiet, -q             静默
---json/--plain          输出格式（默认 --json）
---config, -c <PATH>     配置文件路径
-```
-
-## 输出格式（始终是 JSON）
-
-```json
-// 成功
-{"success": true, "command": "web browser open", "data": {"session_id": "abc123"}, "timestamp": "..."}
-
-// 失败
-{"success": false, "error": "元素未找到: xpath=...", "error_type": "ElementNotFoundError"}
-```
-
-调用方应 `json.loads(stdout)` 解析，**不要 grep/regex**。
-
-## 场景 → 命令映射（高频）
-
-| 用户意图 | 命令模板 |
-|---|---|
-| 打开网页 | `web browser open --url <URL>` |
-| 等待元素出现 | `web navigation wait --type element --xpath <X>` |
-| 点击 | `web element click --xpath <X>` |
-| 输入文本 | `web element input --xpath <X> --value <V>` |
-| 获取文本 | `web element get-text --xpath <X>` |
-| 获取表格 / 复杂提取 | `web action execute-js --code "..."` |
-| 元素截图 | `web element screenshot --xpath <X> --output <PATH>` |
-| 进 iframe | `web iframe enter --xpath <X>`（或 XPath JSON 写法） |
-| 创建 Excel | `excel file create --file <PATH>` |
-| 读单元格 | `excel data read --file <PATH> --cell A1` |
-| 写单元格 | `excel data write --file <PATH> --cell A1 --value <V>` |
-| 区域写入 | `excel data write-range --file <PATH> --cell A1 --values <2D-JSON>` |
-| OCR 验证码 | `tool ocr ddddocr --img <PATH>` |
-| OCR 通用 | `tool ocr paddleocr --img <PATH>` |
-| MD5 / SHA256 | `tool crypto md5 --text <S>` |
-| HTTP GET | `tool http get --url <URL>` |
-| 发送邮件 | `tool email send --to <addr> --subject <S> --body <B>` |
-| 结束进程 | `tool system kill-app --name chrome.exe` |
-| SAP / 桌面操作 | **不可用**：desktop 暂不开放，停下告知用户并改用 web / tool system execute | "登录 SAP 系统" |
-| 流程发布 / 上传流程 | **先 Read** [{{INSTALL_PATH}}/skills/cloud-flow-publish.md]({{INSTALL_PATH}}/skills/cloud-flow-publish.md)，再走 `cloud login → cloud flow init → validate → publish`；加输入参数看该文档「添加输入参数的标准动作」（字段表 + 可复制示例，validate V6/V7 静态拦错） | "把这个流程发到魔像云" |
-| 下载云端流程 | `cloud flow download [流程名]`（覆盖前确认默认 N；AI 不得代答） | "把云端流程拉下来改" |
-
-## 命令选择优先级
-
-1. **网页操作只用 `web`**（即使是桌面里嵌的 web）
-2. **`web action execute-js` 是万能 fallback**：Vue/React 组件、动态元素、复杂表格提取，普通 element 命令做不到时直接 JS
-3. **iframe 嵌套**用 XPath JSON 格式：`{"ElementName":"...","XPaths":[["iframe_xpath","element_xpath"],["backup_xpath"]]}`
-4. **session 自动管理**：第一次 `web browser open` 后，后续 web 命令默认用最新 session，可省 `--session`；报 `Session not found`（如 CLI 进程退出过）时先 `web browser reconnect` 恢复，不要重开浏览器
-5. **业务产物写当前目录**：Excel/JSON/中间文件等业务产物一律用**相对路径**写当前工作目录（或流程目录），**禁止写 `{{INSTALL_PATH}}/workdir/`**——workdir 是 CLI 安装目录里的临时工作区（路径含版本号，升级即失效），内容也不随流程发布进包
-
-## 关键注意事项（6 条 TOC，详情看链接）
-
-1. **Chrome CDP 自动管理** — 别手动 kill Chrome；客户机必须装 Chrome 或 Edge
-2. **session 持久化** — `$TEMP/.uniner-cli/sessions.json`（Windows: `%TEMP%\.uniner-cli\sessions.json`）；CLI 退出后用 `web browser reconnect` 恢复
-3. **Vue/Element UI 组件** — 日期选择器、级联下拉等，用 `execute-js` 直接操作组件模型，不要硬 input
-4. **desktop 暂不开放** — 测试覆盖少，当前版本未开放；任何 desktop 子命令都提示暂不开放，改用 `web action execute-js` 或 `tool system execute`
-5. **Linux 平台** — Playwright 默认 HTTPS-only，访问 HTTP 站点需改 wrapper 加 `--disable-features=HttpsOnlyMode`，或用 Firefox `--browser-type 1`
-6. **Windows GBK 编码** — CLI 内部已强制 UTF-8 输出；调用方读 stdout 也要 UTF-8
-
-## 详细文档（按需 Read）
-
-| 主题 | 路径 |
-|---|---|
-| **魔像云流程开发与发布工作流**（login→init→validate→publish，含版本号确认 + 添加入参标准动作） | [{{INSTALL_PATH}}/skills/cloud-flow-publish.md]({{INSTALL_PATH}}/skills/cloud-flow-publish.md) |
-| 命令树全集 + 三级参数 | [{{INSTALL_PATH}}/skills/cli/SKILL.md]({{INSTALL_PATH}}/skills/cli/SKILL.md) |
-| 完整命令结构（120+ 命令） | [{{INSTALL_PATH}}/skills/cli/command-tree.md]({{INSTALL_PATH}}/skills/cli/command-tree.md) |
-| execute-js 使用指南 | [{{INSTALL_PATH}}/skills/cli/execute-js-guide.md]({{INSTALL_PATH}}/skills/cli/execute-js-guide.md) |
-| 典型场景示例 | [{{INSTALL_PATH}}/skills/cli/examples.md]({{INSTALL_PATH}}/skills/cli/examples.md) |
-| Windows 配置指南 | [{{INSTALL_PATH}}/skills/windows-setup-guide.md]({{INSTALL_PATH}}/skills/windows-setup-guide.md) |
-| macOS 配置指南 | [{{INSTALL_PATH}}/skills/macos-setup-guide.md]({{INSTALL_PATH}}/skills/macos-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/) |
-| 工作目录（CLI 内部临时缓存：截图/下载；**业务产物不要写这里**，写当前目录） | [{{INSTALL_PATH}}/workdir/]({{INSTALL_PATH}}/workdir/) |
-
-## 触发词路由
-
-用户提到【流程发布】【上传流程】【业务流程】【魔像云】【魔微子】等关键词时，
-**先 Read** [{{INSTALL_PATH}}/skills/cloud-flow-publish.md]({{INSTALL_PATH}}/skills/cloud-flow-publish.md)
-再操作——流程生产走 CLI 命令链（login 选组织 → init → validate → （建议手动
-test）→ publish，publish 时提示云端最新版本号、版本号由用户确认），有独立的
-环境前提与 AI 行为红线。
-
-## 典型完整流程（参考）
-
-**网页 → OCR → 提取 → Excel**：
-
-```bash
-# 1. 打开浏览器
-uniner-cli web browser open --url "https://example.com/login"
-
-# 2. 输账号密码 + 截验证码 + OCR（截图 temp 文件放当前目录，勿写 workdir）
-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 "cap.png"
-uniner-cli tool ocr ddddocr --img "cap.png"
-# 从返回 JSON 的 data.result 取识别文本
-
-# 3. 提交登录
-uniner-cli web element input --xpath "//input[@id='captcha']" --value "<识别结果>"
-uniner-cli web element click --xpath "//button[@type='submit']"
-
-# 4. 等表格 + 提取
-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 "out.xlsx"
-uniner-cli excel data write-range --file "out.xlsx" --cell A1 --values "<上一步的 JSON 二维数组>"
-
-# 6. 关浏览器
-uniner-cli web browser close
-```
-
-## 场景沉淀（4 步流程）
-
-> 这是顶部"任务结束硬性规则"提到的"4 步流程"。用户同意保存场景后，按这里走。
-
-每个场景一个目录，三件套：`meta.json` + `steps.json` + `SKILL.md`，存到：
-
-```
-~/.claude/skills/uniner-cli/scenarios/<kebab-case-name>/
-```
-
-（Windows: `%USERPROFILE%\.claude\skills\uniner-cli\scenarios\<kebab-case-name>\`）
-
-**4 步标准流程**：
-
-```bash
-# Step 1: 生成骨架（自动创建目录和模板文件）
-uniner-cli skill init <name>
-
-# Step 2: 用 Write 工具改 meta.json / steps.json / SKILL.md（见下方 schema）
-
-# Step 3: 校验
-uniner-cli skill validate <name>
-
-# Step 4: 试跑一次
-uniner-cli skill run <name> --param ...
-```
-
-### meta.json schema
-
-```json
-{
-  "name": "<kebab-case-name>",
-  "version": "1.0",
-  "description": "一句话描述（会被用来匹配触发关键词）",
-  "params": {
-    "URL": { "type": "string", "required": true, "description": "登录页地址" },
-    "USERNAME": { "type": "string", "required": true, "description": "账号" },
-    "PASSWORD": { "type": "string", "required": true, "sensitive": true, "description": "密码" },
-    "DATE_FROM": { "type": "string", "required": false, "default": "today", "pattern": "^\\d{4}-\\d{2}-\\d{2}$" }
-  }
-}
-```
-
-### steps.json schema
-
-```json
-{
-  "version": "1.0",
-  "name": "<同 meta.name>",
-  "steps": [
-    {
-      "id": "open-browser",
-      "cmd": "web browser open",
-      "args": { "url": "${URL}" },
-      "timeout_ms": 10000
-    },
-    {
-      "id": "ocr-captcha",
-      "cmd": "tool ocr ddddocr",
-      "args": { "img": "out/captcha.png" },
-      "store": "ocrResult",
-      "comment": "整个 stdout JSON 存到 ocrResult，下面用 ${ocrResult.data.result} 取"
-    },
-    {
-      "id": "input-captcha",
-      "cmd": "web element input",
-      "args": { "xpath": "//input[@placeholder='验证码']", "value": "${ocrResult.data.result}" }
-    },
-    {
-      "id": "close-browser",
-      "cmd": "web browser close",
-      "always_run": true,
-      "comment": "无论前面成功与否都跑（清理用）"
-    }
-  ]
-}
-```
-
-### 每个 step 支持的字段
-
-| 字段 | 必需 | 说明 |
-|---|---|---|
-| `id` | ✅ | 步骤 ID（唯一） |
-| `cmd` | ✅ | uniner-cli 子命令，**不带 `uniner-cli` 前缀**，如 `web element input` |
-| `args` | ✅ | dict 形式参数，对应 CLI 的 `--key value` |
-| `store` | ❌ | 把 stdout JSON 整个存到变量名 |
-| `if` | ❌ | 条件表达式（见下） |
-| `on_fail` | ❌ | `abort`（默认）/ `continue` / `goto:<step_id>` |
-| `retry` | ❌ | 失败重试次数（不含首次） |
-| `retry_delay_ms` | ❌ | 重试间隔（默认 1000） |
-| `timeout_ms` | ❌ | 单步超时（覆盖全局） |
-| `always_run` | ❌ | 即使前面失败也跑（清理用） |
-| `comment` | ❌ | 给人/AI 看的注释 |
-
-### 变量替换语法
-
-| 写法 | 含义 |
-|---|---|
-| `${URL}` | 用户传入的 `--param URL=xxx` |
-| `${ocrResult.data.result}` | 上一步 store 的 dict 字段（点号路径） |
-| `${tableData.0.1}` | list 索引（0-based） |
-| `${env:USERPROFILE}` | 环境变量 |
-
-### 条件表达式语法（白名单）
-
-| 写法 | 含义 |
-|---|---|
-| `${var}` | 真值判断 |
-| `!${var}` | 取反 |
-| `${var} == 'yes'` | 字符串/数值相等 |
-| `${var} != 'no'` | 不等 |
-| `${var} > 5` | 数值比较（>=, <=, < 同理） |
-| `${var}.includes('login')` | 包含 |
-| `${var}.startsWith('https')` / `endsWith('.xlsx')` | 前/后缀 |
-| `!${var}.includes('admin')` | 取反组合 |
-
-**故意不支持** `&&` / `||` / `()`。要复合逻辑用多步 + `if` + `on_fail` 拆开。
-
-### 失败时的客户体验
-
-```
-$ uniner-cli skill run tms-export --param URL=...
-{"success": false, "failed_step": "click-search", ...}
-
-────────── How to debug ──────────
-Step 'click-search' failed: timeout
-Open Claude Code, paste this:
-
-   I ran 'uniner-cli skill run' and step 'click-search' failed.
-   Error: timeout
-   Please look at the scenario at:
-     ~/.claude/skills/uniner-cli/scenarios/tms-export
-   Especially steps.json. Help me figure out why and suggest a fix.
-──────────────────────────────────
-```
-
-客户复制这段给你 → 你 Read steps.json 调试 → 改完 `Write` 回去 → 让客户重跑。
-
-### 给 Claude 的对话范式（用户同意保存后）
-
-按这个顺序，**不要跳步**：
-
-1. 想一个 kebab-case 名字（如 `tms-export-waybills` / `sap-monthly-report`）
-2. Bash 跑 `uniner-cli skill init <name>`（生成骨架）
-3. Write 写**真正的**：
-   - `meta.json`：含动态参数 schema（URL / USERNAME / PASSWORD / DATE_FROM 等）
-   - `steps.json`：把刚才跑过的命令序列**完整**写进去，含已知坑的避坑配置（retry / on_fail / always_run）
-   - `SKILL.md`：经验文档（已知坑、用法说明）
-4. Bash 跑 `uniner-cli skill validate <name>` 确认格式无误
-5. 让用户 `uniner-cli skill run <name> --param ...` 自己跑一次确认 0 token 重放可行
-
-**关键**：steps.json 不是命令清单的注释——是**真正可执行的工作流**。要把 `${URL}` `${USERNAME}` `${ocrResult.data.result}` 这种变量绑好，让 `skill run` 真能跑通。
-
-### 已沉淀的场景库
-
-```bash
-uniner-cli skill list                  # 看所有
-uniner-cli skill show <name>           # 看某个的元数据 + 步骤摘要
-uniner-cli skill show <name> --steps   # 看完整步骤
-uniner-cli skill where                 # 看场景库根目录（可手动浏览）
-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)