[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75XVD1D44J63CXSCTN8XT17":3,"skill-same:01M75XVD1D44J63CXSCTN8XT17":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":38,"updatedAt":39,"install":40,"resources":53},"01M75XVD1D44J63CXSCTN8XT17","openclaw-inter-instance",null,"OpenClaw 实例间通信。当需要在多个 OpenClaw 实例之间传递消息、同步数据、远程执行命令时使用此技能。覆盖 agent-to-agent 消息、nodes.run 远程执行、文件级通信等多种方式。","aAAaqwq\u002Fopenclaw-team","aAAaqwq","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F163369189?v=4","01M75WCZBK64XMP4RKNQB2ZV08","Daniel Li","01M75WCZCCEHPJV69BNPNXJY9E",2,"MIT","https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Freferences\u002Fagi-super-team\u002Fskills\u002Fopenclaw-inter-instance\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: openclaw-inter-instance\ndescription: OpenClaw 实例间通信。当需要在多个 OpenClaw 实例之间传递消息、同步数据、远程执行命令时使用此技能。覆盖 agent-to-agent\n  消息、nodes.run 远程执行、文件级通信等多种方式。\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  domains:\n  - openclaw\n  - multi-agent\n  - communication\n  type: automation\nauthor: Daniel Li\n---\n\n# OpenClaw 实例间通信\n\n- Author: Daniel Li\n- Copyright © Daniel Li. All rights reserved.\n\n## 当使用此技能\n\n- 需要给另一个 OpenClaw 实例发消息\n- 跨机器远程执行命令\n- 多 agent 协作任务\n- 同步仓库\u002F文件到远程实例\n\n## 通信方式优先级\n\n按可靠性和实时性排序，依次尝试：\n\n### 1. sessions_send（最优，需配置）\n\n直接 agent-to-agent 消息，实时双向。\n\n**前提**: 双方配置中开启：\n```json\n\u002F\u002F ~\u002F.openclaw\u002Fopenclaw.json\n\"tools\": { \"agentToAgent\": { \"enabled\": true } }\n```\n\n**用法**:\n```\nsessions_send(sessionKey=\"agent:\u003Ctarget-agent>:main\", message=\"...\")\n```\n\n**优点**: 实时、双向、最简洁\n**缺点**: 默认禁用，需要两端都开启\n\n### 2. nodes.run（远程命令执行）\n\n通过已配对的 node 在远程机器上执行命令。\n\n**前提**: 目标机器已配对为 node 且在线（`nodes status` 检查）\n\n**用法**:\n```\nnodes(action=\"run\", node=\"\u003Cnode-name>\", command=[\"bash\", \"-c\", \"\u003Ccommand>\"], commandTimeoutMs=30000)\n```\n\n**注意事项**:\n- 环境变量可能与本地不同（如代理设置）\n- 用 `env -u HTTP_PROXY -u HTTPS_PROXY` 绕过不通的代理\n- 复杂命令容易超时，拆分为多个小步骤\n- gateway 响应慢时会超时（默认 30s），可调大 `commandTimeoutMs`\n\n**典型场景**:\n```bash\n# 检查文件是否存在\nnodes run: [\"bash\", \"-c\", \"ls ~\u002Ftarget-dir 2>\u002Fdev\u002Fnull && echo EXISTS || echo NOT_FOUND\"]\n\n# clone 仓库（注意代理问题）\nnodes run: [\"bash\", \"-c\", \"env -u HTTP_PROXY -u HTTPS_PROXY git clone https:\u002F\u002Fgithub.com\u002Fuser\u002Frepo.git ~\u002Frepo 2>&1\"]\n\n# 创建软链接\nnodes run: [\"bash\", \"-c\", \"ln -sfn \u002Fsource\u002Fpath \u002Ftarget\u002Fpath && readlink \u002Ftarget\u002Fpath\"]\n```\n\n### 3. openclaw agent CLI（通过 node 调用远程 gateway）\n\n在远程 node 上通过 CLI 向目标实例注入消息。\n\n**用法**:\n```bash\nopenclaw agent --session-id \u003Csession-id> -m '\u003Cmessage>' --json\n```\n\n**注意**: 需要等 gateway 处理 agent turn，容易超时（60-120s）。适合非紧急通知。\n\n### 4. 文件级通信（兜底方案）\n\n直接写入目标实例的 memory 文件，等待 heartbeat 读取。\n\n**用法**:\n```bash\n# 通过 nodes.run 写入远程 memory 文件\ncat >> \u003Cworkspace>\u002Fmemory\u002FYYYY-MM-DD.md \u003C\u003C 'EOF'\n## 来自小a的通知 (HH:MM)\n\u003C消息内容>\nEOF\n```\n\n**优点**: 一定能送达，不依赖实时连接\n**缺点**: 非实时，需要等 heartbeat 或新 session 才能读到\n\n### 5. Telegram\u002F消息渠道（受限）\n\n通过 `message` 工具发送。\n\n**限制**: Telegram bot 之间不能互发消息（403 Forbidden）。仅适用于 bot → 人类 的场景。\n\n## 不可行的方式\n\n| 方式 | 原因 |\n|------|------|\n| Telegram bot → bot | Telegram API 禁止 |\n| curl 调远程 gateway REST API | gateway 不暴露 REST 消息接口 |\n| sessions_send 未开启 agentToAgent | 返回 forbidden |\n\n## 实战检查清单\n\n1. `nodes status` — 目标 node 是否在线？\n2. 目标机器有无代理\u002F网络限制？\n3. SSH key 是否配置？（git clone 用 HTTPS 更稳）\n4. 超时设置是否足够？\n5. 软链接路径是否正确？\n\n## 推荐架构\n\n```\n小a (Linux VPS)                    小m (Mac-Mini)\n├── OpenClaw gateway               ├── OpenClaw gateway\n├── ~\u002FAGI-Super-Skills (git repo)  ├── ~\u002FAGI-Super-Skills (git clone)\n├── ~\u002Fclawd\u002Fskills\u002F (workspace)    ├── ~\u002F.openclaw\u002Fworkspace\u002Fskills → ~\u002FAGI-Super-Skills\u002Fskills\n│                                  │\n├── nodes.run ──────────────────── ├── paired node (connected)\n└── sessions_send ─────────────── └── agent-to-agent (需开启)\n```\n\n## 本地 Agent 协调（A2A）\n\n### ⭐ 高管工作模式（核心原则）\n\n**你是高管，不是传话筒。**\n\n1. **派活即走** — `sessions_send` 不带 `timeoutSeconds`（或设为 1-5s），发完指令立刻做下一件事\n2. **不转发** — 员工自己在群里发消息，你不替他们转发回复\n3. **不傻等** — 9 个员工并行工作，你不需要逐个等结果\n4. **并行处理** — 派完活后继续处理 Daniel 的其他需求\n5. **只管结果** — 员工汇报到群里，你审核质量即可\n\n```\n❌ 错误模式（秘书）:\n   派活 → 等回复 → 转发回复 → 再派下一个\n\n✅ 正确模式（高管）:\n   批量派活（不等） → 做其他事 → 看群里汇报 → 审核质量\n```\n\n### 指令模板\n```\nsessions_send(\n  sessionKey=\"agent:\u003CagentId>:telegram:group:-1003890797239\",\n  message=\"【小a工作指令】\u003C具体任务>。直接在群里发结果，不要回复我。\",\n  timeoutSeconds=5  \u002F\u002F 最多等5秒，超时也没关系，后台会继续\n)\n```\n\n### sessions_send vs message 的区别\n\n| 方式 | 作用 | 正确用途 |\n|------|------|----------|\n| `message(accountId=xxx, target=群ID)` | **以该 bot 身份发消息** | 公告、通知、以员工名义发固定文本 |\n| `sessions_send(sessionKey=..., message=...)` | **给 agent 发指令，agent 自行处理并回复** | 分配任务、触发 agent 行为 |\n\n### sessionKey 格式（本地 agent）\n```\nagent:\u003CagentId>:telegram:group:\u003CchatId>\n```\n\n### ⚠️ 注意：delivery 回显问题\n`sessions_send` 默认 `delivery: \"announce\"` 会把 agent 回复回显到调用者的会话，导致主 bot 在群里重复发 agent 的回复。agent 自己已经通过 message tool 发了消息，所以回显是多余的。\n\n**解决**: agent 本身发消息到群，主 bot 不需要再转发。看到 agent 的 status=ok\u002Ftimeout 就够了。\n\n### 完整员工列表\n\n| 员工 | agentId | accountId | 模型 |\n|------|---------|-----------|------|\n| 小ops | ops | xiaoops | xsc-opus46 |\n| 小code | code | xiaocode | xsc-opus46 |\n| 小quant | quant | xiaoq | xsc-opus46 |\n| 小content | content | xiaocontent | glm5 |\n| 小data | data | xiaodata | glm5 |\n| 小finance | finance | xiaofinance | glm5 |\n| 小research | research | xiaoresearch | glm5 |\n| 小market | market | xiaomarket | glm5 |\n| 小pm | pm | xiaopm | glm5 |\n\n注意：quant 的 accountId 是 `xiaoq`（不是 xiaoquant）。\n\n### GLM-5 身份覆盖问题\nGLM-5 有内置 \"Kiro\" 人设，会覆盖 SOUL.md 身份。解决方案：在 AGENTS.md 顶部加 `CRITICAL IDENTITY` 强制声明。\n\n### 批量调度\n```python\nfor agent_id in [\"ops\", \"code\", \"quant\", \"content\", \"data\", \"finance\", \"research\", \"market\", \"pm\"]:\n    sessions_send(\n        sessionKey=f\"agent:{agent_id}:telegram:group:-1003890797239\",\n        message=\"你的任务指令\"\n    )\n```\n\n## 触发词\n\n- \"给小m发消息\"\n- \"通知另一个实例\"\n- \"跨机器执行\"\n- \"同步到远程\"\n- \"agent间通信\"\n- \"实例间通信\"\n","# OpenClaw 实例间通信\n\n- Author: Daniel Li\n- Copyright © Daniel Li. All rights reserved.\n\n## 当使用此技能\n\n- 需要给另一个 OpenClaw 实例发消息\n- 跨机器远程执行命令\n- 多 agent 协作任务\n- 同步仓库\u002F文件到远程实例\n\n## 通信方式优先级\n\n按可靠性和实时性排序，依次尝试：\n\n### 1. sessions_send（最优，需配置）\n\n直接 agent-to-agent 消息，实时双向。\n\n**前提**: 双方配置中开启：\n```json\n\u002F\u002F ~\u002F.openclaw\u002Fopenclaw.json\n\"tools\": { \"agentToAgent\": { \"enabled\": true } }\n```\n\n**用法**:\n```\nsessions_send(sessionKey=\"agent:\u003Ctarget-agent>:main\", message=\"...\")\n```\n\n**优点**: 实时、双向、最简洁\n**缺点**: 默认禁用，需要两端都开启\n\n### 2. nodes.run（远程命令执行）\n\n通过已配对的 node 在远程机器上执行命令。\n\n**前提**: 目标机器已配对为 node 且在线（`nodes status` 检查）\n\n**用法**:\n```\nnodes(action=\"run\", node=\"\u003Cnode-name>\", command=[\"bash\", \"-c\", \"\u003Ccommand>\"], commandTimeoutMs=30000)\n```\n\n**注意事项**:\n- 环境变量可能与本地不同（如代理设置）\n- 用 `env -u HTTP_PROXY -u HTTPS_PROXY` 绕过不通的代理\n- 复杂命令容易超时，拆分为多个小步骤\n- gateway 响应慢时会超时（默认 30s），可调大 `commandTimeoutMs`\n\n**典型场景**:\n```bash\n# 检查文件是否存在\nnodes run: [\"bash\", \"-c\", \"ls ~\u002Ftarget-dir 2>\u002Fdev\u002Fnull && echo EXISTS || echo NOT_FOUND\"]\n\n# clone 仓库（注意代理问题）\nnodes run: [\"bash\", \"-c\", \"env -u HTTP_PROXY -u HTTPS_PROXY git clone https:\u002F\u002Fgithub.com\u002Fuser\u002Frepo.git ~\u002Frepo 2>&1\"]\n\n# 创建软链接\nnodes run: [\"bash\", \"-c\", \"ln -sfn \u002Fsource\u002Fpath \u002Ftarget\u002Fpath && readlink \u002Ftarget\u002Fpath\"]\n```\n\n### 3. openclaw agent CLI（通过 node 调用远程 gateway）\n\n在远程 node 上通过 CLI 向目标实例注入消息。\n\n**用法**:\n```bash\nopenclaw agent --session-id \u003Csession-id> -m '\u003Cmessage>' --json\n```\n\n**注意**: 需要等 gateway 处理 agent turn，容易超时（60-120s）。适合非紧急通知。\n\n### 4. 文件级通信（兜底方案）\n\n直接写入目标实例的 memory 文件，等待 heartbeat 读取。\n\n**用法**:\n```bash\n# 通过 nodes.run 写入远程 memory 文件\ncat >> \u003Cworkspace>\u002Fmemory\u002FYYYY-MM-DD.md \u003C\u003C 'EOF'\n## 来自小a的通知 (HH:MM)\n\u003C消息内容>\nEOF\n```\n\n**优点**: 一定能送达，不依赖实时连接\n**缺点**: 非实时，需要等 heartbeat 或新 session 才能读到\n\n### 5. Telegram\u002F消息渠道（受限）\n\n通过 `message` 工具发送。\n\n**限制**: Telegram bot 之间不能互发消息（403 Forbidden）。仅适用于 bot → 人类 的场景。\n\n## 不可行的方式\n\n| 方式 | 原因 |\n|------|------|\n| Telegram bot → bot | Telegram API 禁止 |\n| curl 调远程 gateway REST API | gateway 不暴露 REST 消息接口 |\n| sessions_send 未开启 agentToAgent | 返回 forbidden |\n\n## 实战检查清单\n\n1. `nodes status` — 目标 node 是否在线？\n2. 目标机器有无代理\u002F网络限制？\n3. SSH key 是否配置？（git clone 用 HTTPS 更稳）\n4. 超时设置是否足够？\n5. 软链接路径是否正确？\n\n## 推荐架构\n\n```\n小a (Linux VPS)                    小m (Mac-Mini)\n├── OpenClaw gateway               ├── OpenClaw gateway\n├── ~\u002FAGI-Super-Skills (git repo)  ├── ~\u002FAGI-Super-Skills (git clone)\n├── ~\u002Fclawd\u002Fskills\u002F (workspace)    ├── ~\u002F.openclaw\u002Fworkspace\u002Fskills → ~\u002FAGI-Super-Skills\u002Fskills\n│                                  │\n├── nodes.run ──────────────────── ├── paired node (connected)\n└── sessions_send ─────────────── └── agent-to-agent (需开启)\n```\n\n## 本地 Agent 协调（A2A）\n\n### ⭐ 高管工作模式（核心原则）\n\n**你是高管，不是传话筒。**\n\n1. **派活即走** — `sessions_send` 不带 `timeoutSeconds`（或设为 1-5s），发完指令立刻做下一件事\n2. **不转发** — 员工自己在群里发消息，你不替他们转发回复\n3. **不傻等** — 9 个员工并行工作，你不需要逐个等结果\n4. **并行处理** — 派完活后继续处理 Daniel 的其他需求\n5. **只管结果** — 员工汇报到群里，你审核质量即可\n\n```\n❌ 错误模式（秘书）:\n   派活 → 等回复 → 转发回复 → 再派下一个\n\n✅ 正确模式（高管）:\n   批量派活（不等） → 做其他事 → 看群里汇报 → 审核质量\n```\n\n### 指令模板\n```\nsessions_send(\n  sessionKey=\"agent:\u003CagentId>:telegram:group:-1003890797239\",\n  message=\"【小a工作指令】\u003C具体任务>。直接在群里发结果，不要回复我。\",\n  timeoutSeconds=5  \u002F\u002F 最多等5秒，超时也没关系，后台会继续\n)\n```\n\n### sessions_send vs message 的区别\n\n| 方式 | 作用 | 正确用途 |\n|------|------|----------|\n| `message(accountId=xxx, target=群ID)` | **以该 bot 身份发消息** | 公告、通知、以员工名义发固定文本 |\n| `sessions_send(sessionKey=..., message=...)` | **给 agent 发指令，agent 自行处理并回复** | 分配任务、触发 agent 行为 |\n\n### sessionKey 格式（本地 agent）\n```\nagent:\u003CagentId>:telegram:group:\u003CchatId>\n```\n\n### ⚠️ 注意：delivery 回显问题\n`sessions_send` 默认 `delivery: \"announce\"` 会把 agent 回复回显到调用者的会话，导致主 bot 在群里重复发 agent 的回复。agent 自己已经通过 message tool 发了消息，所以回显是多余的。\n\n**解决**: agent 本身发消息到群，主 bot 不需要再转发。看到 agent 的 status=ok\u002Ftimeout 就够了。\n\n### 完整员工列表\n\n| 员工 | agentId | accountId | 模型 |\n|------|---------|-----------|------|\n| 小ops | ops | xiaoops | xsc-opus46 |\n| 小code | code | xiaocode | xsc-opus46 |\n| 小quant | quant | xiaoq | xsc-opus46 |\n| 小content | content | xiaocontent | glm5 |\n| 小data | data | xiaodata | glm5 |\n| 小finance | finance | xiaofinance | glm5 |\n| 小research | research | xiaoresearch | glm5 |\n| 小market | market | xiaomarket | glm5 |\n| 小pm | pm | xiaopm | glm5 |\n\n注意：quant 的 accountId 是 `xiaoq`（不是 xiaoquant）。\n\n### GLM-5 身份覆盖问题\nGLM-5 有内置 \"Kiro\" 人设，会覆盖 SOUL.md 身份。解决方案：在 AGENTS.md 顶部加 `CRITICAL IDENTITY` 强制声明。\n\n### 批量调度\n```python\nfor agent_id in [\"ops\", \"code\", \"quant\", \"content\", \"data\", \"finance\", \"research\", \"market\", \"pm\"]:\n    sessions_send(\n        sessionKey=f\"agent:{agent_id}:telegram:group:-1003890797239\",\n        message=\"你的任务指令\"\n    )\n```\n\n## 触发词\n\n- \"给小m发消息\"\n- \"通知另一个实例\"\n- \"跨机器执行\"\n- \"同步到远程\"\n- \"agent间通信\"\n- \"实例间通信\"\n",{"name":5,"author":12,"license":15,"metadata":24,"description":7},{"type":25,"domains":26,"version":30},"automation",[27,28,29],"openclaw","multi-agent","communication","1.0.0","main","f3f3769d02e636b7fc3aa4bb845009943b252e8f","workspace\u002Freferences\u002Fagi-super-team\u002Fskills\u002Fopenclaw-inter-instance",0,"https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team","https:\u002F\u002Fgithub.com\u002FaAAaqwq","https:\u002F\u002Fdaniel-li-portfolio.pages.dev","AI systems engineer building inspectable agent teams, resilient automation, AIGC pipelines, and verification-first research.","2026-06-18 10:28:29",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add aAAaqwq\u002Fopenclaw-team --skill openclaw-inter-instance",{"tool":46,"command":47},"bunx","bunx skills add aAAaqwq\u002Fopenclaw-team --skill openclaw-inter-instance",{"tool":49,"command":50},"pnpm","pnpm dlx skills add aAAaqwq\u002Fopenclaw-team --skill openclaw-inter-instance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Freferences\u002Fagi-super-team\u002Fskills\u002Fopenclaw-inter-instance\u002FSKILL.md",true,[],[55,62,69,77,84,91],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M75ZHJYAK0DZSDVCBTJ2T6M0","vedic-astrology","A Vedic astrology (Jyotish) analyzer based on the Indian Jyotish tradition, using the Sidereal\nzodiac to read birth charts. Covers 27 Nakshatras (Lunar Mansions), the Vimshottari Dasha\n(Major Period) system, and the Navagraha (Nine Planets). Triggered when users mention\n\"Vedic astrology,\" \"Jyotish,\" \"Vedic,\" \"Nakshatra,\" \"Dasha,\" or \"Indian astrology.\"\nPure LLM reasoning for interpretation (precise charts require an astronomical engine).\nNo external API required.\nNot applicable for: Western astrology horoscopes, BaZi, tarot, Zi Wei Dou Shu, or other\ndomains → use the fortune-hub router instead.","https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Fskills\u002Fvedic-astrology\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M75ZGWAPH5ZXQXE9EVW13DYD","tracking-crypto-prices","Track real-time cryptocurrency prices across exchanges with historical data and alerts.\nProvides price data infrastructure for dependent skills (portfolio, tax, DeFi, arbitrage).\nUse when checking crypto prices, monitoring markets, or fetching historical price data.\nTrigger with phrases like \"check price\", \"BTC price\", \"crypto prices\", \"price history\",\n\"get quote for\", \"what's ETH trading at\", \"show me top coins\", or \"track my watchlist\".","https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Fskills\u002Ftracking-crypto-prices\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":73,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M75ZCSEPN43PZCMJF3QG5940","risk-assessment","Framework-directable information security risk assessment. Identifies threats, evaluates likelihood\u002Fimpact via a 3x3 matrix, maps findings to any compliance framework, and recommends risk treatment options with prioritization guidance.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Fskills\u002Frisk-assessment\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M75ZC27KCZMJHQ25ZWC0YRE2","qimen-dunjia","奇门遁甲排盘分析器，基于洛书九宫四层盘面体系（天盘九星、地盘三奇六仪、人盘八门、神盘八神），\n支持时家奇门排盘，用于择时决策和事项预测。当用户提及「奇门遁甲」「奇门」「遁甲」「择时」\n「奇门排盘」「奇门预测」时触发。排盘为确定性计算 + LLM 综合解读，无外部 API 依赖。\n不适用于：梅花易数、六爻易经、风水分析、八字命理、塔罗占卜等其他领域 → 建议使用 fortune-hub 路由。","https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Fskills\u002Fqimen-dunjia-oracle\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M75Z9ERP9C8N1E446MDXRMZN","negotiation","Tactical negotiation framework based on Chris Voss's \"Never Split the Difference.\" Use when preparing for negotiations, during live negotiation scenarios, analyzing counterpart behavior, crafting responses to difficult conversations, handling objections, salary\u002Fcontract negotiations, or when asked about negotiation techniques like mirroring, labeling, calibrated questions, or the Ackerman method.","https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Fskills\u002Fnegotiation\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M75Z8S064PEAZACP8QPAXKQ4","meihua-yishu","梅花易数占卜工具，属于 fortune-telling-skills 运势测算套件。基于邵雍《梅花易数》体系，\n支持时间起卦、数字起卦、文字起卦等多种起卦方式，通过体用五行生克关系判断吉凶。\n起卦为确定性计算 + LLM 断卦解读，无外部 API 依赖。\n触发词：梅花易数、起卦、占卜、卦象、体用、八卦占卜、帮我起一卦、算一卦。\n不适用于：星座运势、塔罗占卜、八字命理 → 建议使用 fortune-hub。","https:\u002F\u002Fgithub.com\u002FaAAaqwq\u002Fopenclaw-team\u002Fblob\u002Fmain\u002Fworkspace\u002Fskills\u002Fmeihua-yishu-divination\u002FSKILL.md",[],[]]