dsh-crwu-workbench 0.0.10

package/skills/dws/LICENSE

@@ -0,0 +1,178 @@
+   Copyright 2026 Alibaba Group
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf
+   of any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS

package/skills/dws/NOTICE

@@ -0,0 +1,17 @@
+DingTalk Workspace CLI (dws)
+Copyright 2026 Alibaba Group
+
+This product includes software developed at
+DingTalk (https://www.dingtalk.com/).
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

package/skills/dws/dingtalk-aisearch/SKILL.md

@@ -0,0 +1,83 @@
+---
+name: dingtalk-aisearch
+description: AI搜问：人员语义搜索与跨源定位。Use when 按姓名/工号/部门/职责/上下级或手机号线索找人，跨文档/消息/邮件/听记检索，或回溯“我发过/收到过”。完整手机号反查走 dingtalk-contact；找到 userId 后由 contact 补详情。命令前缀：dws aisearch。
+metadata:
+  cli_version: ">=0.2.14"
+  category: product
+  requires:
+    bins:
+      - dws
+---
+
+# 钉钉 AI 搜问 Skill
+
+## 前置条件 — 执行操作前必读
+
+> **CRITICAL — 执行任何 `dws` 操作前，MUST 先用 Read 工具完整读取 [`dingtalk-shared`](../dingtalk-shared/SKILL.md)。**该轻量文件包含全局执行契约、安全底线及 shared references 的按需加载导航；不要预加载其全部 references。
+
+> 命令参考：[aisearch.md](references/aisearch.md)。
+
+## 意图表
+
+| 用户说 | 命令 |
+|--------|------|
+| "找张三 / 张三是谁" | `dws aisearch person --query "张三" --dimension name` |
+| "谁负责 XX / XX 负责人是谁" | `dws aisearch person --query "<XX>" --dimension duty` |
+| "张三的上级 / 下级" | `dws aisearch person --query "张三" --dimension supervisor`（或 `subordinate`） |
+| "X 部门有哪些人" | `dws aisearch person --query "<部门>" --dimension department` |
+| "工号 12345 是谁" | `dws aisearch person --query "<工号>" --dimension jobNumber` |
+| "按手机号线索语义搜人" | `dws aisearch person --query "<手机号线索>" --dimension phone` |
+| "完整手机号精确反查" | `dws contact user search-mobile --mobile "<完整手机号>"` |
+| "最近 OKR 相关邮件 / 项目相关文档" | `dws aisearch enterprise --queries "<主题>" --types mail/document --time-range "<时间>"` |
+| "我发过/创建过/分享过/收到过什么" | `dws aisearch behavior --queries "<主题>" --behavior-type <动作> --direction <方向>` |
+
+## 标准 SOP（必遵流程）
+
+> 命中以下意图**必须**按对应 SOP 顺序执行；**禁止**跳步、替换命令、编造 flag/ID。每条命令必须带 `--format json`，执行后必须按"解析"步取真实字段，不得凭返回结构猜测。
+
+### SOP-1 搜人 → 拿 userId（search-person）
+
+**触发**：姓名模糊找人/谁负责/查上下级/部门成员/工号反查/手机号线索语义搜人。
+
+1. **定维度（必须）**：姓名→`name`、"谁负责 XX"→`duty`、部门成员→`department`、上级/下级→`supervisor`/`subordinate`、工号→`jobNumber`、手机号语义线索→`phone`；完整手机号精确反查切到 `dingtalk-contact` 的 `user search-mobile`；不确定→`all`。`--query` 必须按用户原文**完整保真**，切勿截断、改昵称、扩同音字。
+2. **执行（必须）**：`dws aisearch person --query "<完整值>" --dimension <维度> --format json`。
+3. **解析（必须）**：从 JSON 取 `userId` / `openDingTalkId`；**多候选必须输出让用户选，禁止默认取第一个、禁止编造**未返回的人员字段。
+4. **衔接（必须）**：要邮箱/部门/职位/主管等详情 → 切 `dingtalk-contact` 执行 `dws contact user get --ids <userId> --format json`；发消息 → `dingtalk-chat`；发 DING → `dingtalk-misc`（`references/ding.md`）。
+5. **失败（必须）**：未命中最多换 1 个维度重试一次（如 `name`→`department`/`jobNumber`/`phone`），仍保留完整目标值；仍无果**必须如实告知**。
+
+**禁止**：用半截姓名扩大搜索、跳过 `--format json`、取首个候选、凭空补全人员信息。
+
+### SOP-2 跨源搜内容（search-content）
+
+**触发**：跨文档/邮件/消息按主题找内容。
+
+1. **执行（必须）**：`dws aisearch enterprise --queries "<主题>" --types <document,mail,...> --time-range "<时间>" --format json`；多主题逗号分隔。
+2. **衔接（必须）**：按命中来源切到对应产品 skill 读写。**aisearch 只负责"找到"，不做读写。**
+
+**禁止**：把 aisearch 当作读写入口、跳过下游 skill 直接改数据。
+
+### SOP-3 行为回溯（search-behavior）
+
+**触发**："我发过/收到过/创建过/分享过什么"。
+
+1. **执行（必须）**：`dws aisearch behavior --queries "<主题>" --behavior-type <动作> --direction <方向> --format json`。
+2. **衔接（必须）**：按记录类型切对应 skill 操作；aisearch 不做读写。
+
+**禁止**：编造行为结果、跳过 `--format json`。
+
+## 高频硬约束
+
+- 搜索目标必须完整保真：姓名、工号、手机号、部门名按用户原文完整传入 `--query`，严禁自行截断、拆字、改昵称或扩展同音字。
+- 首次未命中时最多换维度重试一次（如 name → department/jobNumber/phone），仍必须保留完整目标值；不要用半截姓名扩大搜索。
+- 找到候选后，如用户要邮箱、部门、职位、主管等详情，必须切到 `dingtalk-contact` 执行 `contact user get --ids <userId> --format json` 补全。
+- 多候选且无法唯一判断时输出候选并询问；不要默认取第一个，也不要编造未返回的人员信息。
+- 所有 `dws aisearch` 命令加 `--format json`。
+
+## 跨产品协作
+
+- 拿到 userId 后查详情 / 部门 → 切到 `dingtalk-contact`
+- 拿到 userId 发消息 → 切到 `dingtalk-chat`
+- 拿到 userId 发 DING → 切到 `dingtalk-misc`（`references/ding.md`）
+## 局部意图与短流程
+
+- [局部意图消歧](references/intent-guide.md)；[短流程](references/lite-recipes.md)。

package/skills/dws/dingtalk-aisearch/references/aisearch.md

@@ -0,0 +1,249 @@
+# aisearch - AI 搜问
+
+> `aisearch` 模块当前有三个规范子命令：`person`（搜人）、`enterprise`（搜企业内部知识内容）和 `behavior`（搜企业内部行为记录）。
+>
+>  **搜人容错说明**（无需主动使用）：CLI 兼容下列 alias 兜底，模型偶尔写 `search` / `find` / `query` / `contact` / `people` 等也能跑通——但**搜人输出和文档以 `person` 为准**。
+>
+> 搜人的规范参数是 `--query`；旧 `--keyword`（含 `-w`）及历史隐藏参数 `--name` / `--q` / `--text` 继续兼容，新的示例统一使用 `--query`。
+
+## 企业人员搜索
+
+通过关键词搜索企业内人员信息，支持按维度筛选。
+
+```
+Usage:
+  dws aisearch person [flags]
+Example:
+  dws aisearch person --query "张三" --dimension name --format json
+  dws aisearch person --query "产品部" --dimension department --format json
+  dws aisearch person --query "五道" --dimension supervisor --format json
+  dws aisearch person --query "AI搜问" --dimension duty --format json
+  dws aisearch person --query "李四" --dimension name,department --format json
+  dws aisearch person --query "<手机号线索>" --dimension phone --format json
+  dws aisearch person --query "W12345" --dimension jobNumber --format json
+Flags:
+      --query string       搜索关键词 (必填，如人名、技能关键词等)
+      --dimension string   查询维度，多个用逗号分隔 (默认 "all")
+```
+
+### dimension 可选值
+
+| 值 | 含义 | 触发词 |
+|----|------|--------|
+| `all` | 全部维度（默认） | — |
+| `name` | 姓名 | "叫什么"、"是谁" |
+| `department` | 部门 | "部门"、"团队"、"哪个部门" |
+| `position` | 职位 | "职位"、"岗位"、"职级" |
+| `duty` | 职责/技能 | "负责什么"、"职责"、"技能"、"负责人" |
+| `supervisor` | 上级 | "上级"、"领导"、"主管" |
+| `subordinate` | 下级 | "下级"、"下属"、"团队成员" |
+| `phone` | 手机号语义线索 | "电话线索"、"联系方式相关"；完整手机号精确反查走 `contact user search-mobile` |
+| `jobNumber` | 工号 | "工号"、"工号是多少"、"员工编号" |
+
+### keyword 提取规则
+
+仅填入实际的搜索目标（人名、技能关键词等），不包含查询维度词。维度词必须映射到 `--dimension`：
+
+| 用户说 | keyword | dimension |
+|--------|---------|-----------|
+| "五道的上级是谁" | 五道 | supervisor |
+| "张三负责什么" | 张三 | duty |
+| "AI搜问的负责人是谁" | AI搜问 | duty |
+| "产品部有谁" | 产品部 | department |
+| "李四是哪个部门的" | 李四 | department |
+| "按手机号线索找人" | 用户提供的手机号线索 | phone |
+| "工号W12345是谁" | W12345 | jobNumber |
+
+---
+
+## 意图判断
+
+- 用户说"搜人/找人/谁负责/上级是谁/哪个部门的人" → `aisearch person`
+- 用户提供完整手机号精确反查 → `contact user search-mobile`
+- 用户说"搜资料/找方案/查文档/搜企业知识/项目相关内容/工作总结/周报总结" → `aisearch enterprise`
+- 用户说"最近/本周/今天 + XX相关消息/文档/邮件有哪些" → `aisearch enterprise`，时间词进 `--time-range`，类型词进 `--types`
+- 用户说"我发过/谁发给我/创建过/分享过/收到过/今天我干了什么" → `aisearch behavior`
+- 用户说"搜同事" → `aisearch person`；查部门详情/部门成员/通讯录精确信息 → `contact`
+
+**关键区分**：`aisearch person`（姓名模糊、工号、职责、手机号线索、上下级等搜索）vs `aisearch enterprise`（按内容找企业内部知识）vs `aisearch behavior`（按动作找发送/创建/分享/编辑/接收记录）vs `contact`（完整手机号反查、已知 userId 详情、部门成员列表）
+
+### 高优先级抽取规则
+
+- `enterprise` 抽槽顺序固定为：先抽时间词到 `--time-range`，再抽类型词到 `--types`，最后把剩余主题词放进 `--queries`。
+- 所有类型词都必须从 `queries` 中剥离，不能写进 `--query/--queries`。例如“最近 OKR 相关邮件”中，`queries=OKR`、`types=mail`、`time-range=最近`。
+- 错误示例：不要生成 `--query "搜索问题"`、`--query "OKR 邮件"`、`--query "AI 搜问 日程"`、`--query "项目 待办"` 这类丢失或混入类型词的命令。
+- 也不要把完整自然语言原句塞进 `--query`；`enterprise` 不做自然语言解析，必须显式拆出 `--queries`、`--types`、`--time-range`。
+- “相关消息/相关文档/相关邮件有哪些”默认是按内容找企业知识，走 `aisearch enterprise`；只有出现“我发过/某人发给我/我收到/我创建/我分享/我编辑”等行为动作时，才走 `aisearch behavior`。
+- `queries` 只放主题词，不放“最近/本周/消息/文档/邮件/日程/待办/纪要/图片/链接/有哪些/相关”等时间、类型、语气词。
+- 只要用户显式说“最近/本周/今天/昨天/本月/过去一周/Q3”等时间词，就必须填写 `--time-range`。
+- 只要用户显式说出任一类型词，就必须填写对应 `--types`；多个类型同时出现时用逗号分隔，如 `--types im,mail`。
+
+### enterprise 类型词映射
+
+| 用户类型词 | types |
+|------------|-------|
+| 全部、所有、工作总结、日报总结、周报总结、月报总结 | `all` |
+| 文档、资料、方案、模板 | `document` |
+| 消息、聊天记录、群消息、群里说了什么 | `im` |
+| 邮件、邮箱、mail、email | `mail` |
+| 日程、会议邀请、会议安排 | `calendar` |
+| 待办、任务、TODO | `todo` |
+| 会议纪要、纪要、听记、闪记、录音摘要 | `minute` |
+| 日志 | `report` |
+| 图片、截图 | `image` |
+| 链接、URL、网址 | `link` |
+| AI 表格、多维表、notable | `notable` |
+| 企业百科、百科 | `baike` |
+
+## 上下文传递表
+
+| 操作 | 从返回中提取 | 用于 |
+|------|-------------|------|
+| `aisearch person` | `userId`（用户ID）、`title`（姓名） | 展示搜索结果、后续操作（发消息/建待办等） |
+
+## 重名消歧
+
+> **CAUTION:** 多人同名时禁止默认选第一个 — 须追加 `contact user get --ids userId1,userId2,...` 获取部门/职位后请用户确认。详见 [08-directory.md](../../dingtalk-contact/references/08-directory.md)「多命中」。
+
+---
+
+## 企业内部知识搜索
+
+用于检索企业内部知识内容，例如文档、消息、日程、待办、听记、日志、图片、链接、AI 表格、企业百科、邮件等。它关注内容本身，适合查找某个主题的资料、搜索包含特定关键词的内容、了解项目/产品相关信息、准备汇报材料等场景。
+
+```
+Usage:
+  dws aisearch enterprise [flags]
+Example:
+  dws aisearch enterprise --queries "智能化方案" --types document --format json
+  dws aisearch enterprise --queries "搜索问题" --types im --time-range "最近" --format json
+  dws aisearch enterprise --queries "搜问" --types im --time-range "最近" --format json
+  dws aisearch enterprise --queries "OKR" --types mail --time-range "最近" --format json
+  dws aisearch enterprise --queries "AI搜问" --types calendar --time-range "本周" --format json
+  dws aisearch enterprise --queries "项目" --types todo,minute --time-range "最近" --format json
+  dws aisearch enterprise --queries "发版" --types im --time-range "本周" --format json
+  dws aisearch enterprise --types all --time-range "本周" --format json
+  dws aisearch enterprise --queries "OKR" --types document,im,mail --format json
+Flags:
+      --queries string      内容关键词，多个用逗号分隔；汇总类场景可留空
+      --types string        搜索类型，多个用逗号分隔 (默认 "all")
+      --time-range string   时间范围，仅当用户显式给出时间词时填写
+```
+
+### enterprise types 可选值
+
+| 值 | 含义 | 触发词 |
+|----|------|--------|
+| `all` | 全部类型（默认） | 全部、所有、工作总结、日报总结、周报总结、月报总结 |
+| `document` | 文档 | 文档、资料、方案、模板 |
+| `im` | 消息 | 消息、聊天记录、群消息、群里发了什么 |
+| `calendar` | 日程 | 日程、会议邀请、会议安排 |
+| `todo` | 待办 | 待办、任务、TODO |
+| `minute` | 会议纪要/闪记/听记 | 会议纪要、纪要、听记、闪记、录音摘要 |
+| `report` | 日志 | 仅显式出现“日志”时使用 |
+| `image` | 图片 | 图片、截图 |
+| `link` | 链接 | 链接、URL、网址 |
+| `notable` | 多维表 / AI 表格 | AI表格、多维表、notable |
+| `baike` | 企业百科 | 企业百科、百科 |
+| `mail` | 邮件 | 邮件、邮箱、mail、email |
+
+### enterprise 参数提取规则
+
+- `queries` 只放内容关键词，不放时间、类型词。比如“本周的 OKR 文档”中，`queries=OKR`；“最近 OKR 相关邮件”中，`queries=OKR`，不要写成 `queries=OKR 邮件`。
+- 时间信息放到 `--time-range`，仅当用户显式给出“今天/本周/最近/9月/Q3/过去一周”等时间词时填写。
+- 类型词放到 `--types`，所有类型词都不能留在 `--query/--queries`；多类型用逗号分隔。文档/资料/方案类型使用底层枚举 `document`（注意不是 `doc`）。`report` 仅在用户显式说“日志”时触发；“周报/日报/月报/工作汇报”不要自动映射为 `report`。
+- `mail` 仅在用户显式说“邮件/邮箱/mail/email”时触发；一旦触发，必须进入 `--types mail`，不能留在 `--query/--queries`。
+- “工作总结/日报总结/周报总结/月报总结”这类汇总场景，用 `--types all`，`--queries` 可留空。
+
+| 用户说 | queries | types | time-range |
+|--------|---------|-------|------------|
+| “智能化方案相关文档” | 智能化方案 | document | 空 |
+| “最近搜索问题相关的消息都有哪些” | 搜索问题 | im | 最近 |
+| “最近搜问相关的消息都有哪些” | 搜问 | im | 最近 |
+| “最近 OKR 相关邮件” | OKR | mail | 最近 |
+| “本周 AI 搜问相关日程” | AI 搜问 | calendar | 本周 |
+| “最近项目相关待办和纪要” | 项目 | todo,minute | 最近 |
+| “本周的 OKR 文档” | OKR | document | 本周 |
+| “最近发版相关消息” | 发版 | im | 最近 |
+| “AI 搜问相关图片和链接” | AI 搜问 | image,link | 空 |
+| “OKR 相关 AI 表格和百科” | OKR | notable,baike | 空 |
+| “2025-12-06 到 2025-12-19 工作总结” | 空 | all | 2025-12-06 到 2025-12-19 |
+| “本周的日志” | 空 | report | 本周 |
+| “我收到的邮件” | 空 | mail | 空 |
+
+---
+
+## 企业内部行为记录搜索
+
+用于检索“谁对什么做了什么”的企业内部行为记录，例如发过、创建过、分享过、编辑过、收到过的文档、消息、日程、待办、听记、日志、图片、链接、AI 表格、企业百科、邮件等。它关注行为流向和动作，不是按内容本身找知识。
+
+```
+Usage:
+  dws aisearch behavior [flags]
+Example:
+  dws aisearch behavior --queries "智能化方案" --types document --format json
+  dws aisearch behavior --types mail --behavior-type send --direction "我->汐峰" --format json
+  dws aisearch behavior --types all --behavior-type create --time-range "本周" --format json
+  dws aisearch behavior --types im --chat-scope "scrum群" --behavior-type send --time-range "今天" --format json
+Flags:
+      --queries string          内容关键词，多个用逗号分隔；汇总类场景可留空
+      --types string            搜索类型，多个用逗号分隔 (默认 "all")
+      --chat-scope string       消息所在会话/群范围，仅 IM 类型且用户明确指定群名时填写
+      --behavior-type string    行为类型 (默认 "all")
+      --time-range string       时间范围，仅当用户显式给出时间词时填写
+      --direction string        交互方向，如 "我->汐峰"、"汐峰->我"、"我<->汐峰"
+```
+
+### behavior types 可选值
+
+| 值 | 含义 | 触发词 |
+|----|------|--------|
+| `all` | 全部类型（默认） | 今天我干了什么、我最近做过什么 |
+| `document` | 文档 | 文档、资料、方案、模板 |
+| `im` | 消息 | 消息、聊天记录、群消息、群里发了什么 |
+| `calendar` | 日程 | 日程、会议邀请、会议安排 |
+| `todo` | 待办 | 待办、任务、TODO |
+| `minute` | 会议纪要/闪记/听记 | 会议纪要、纪要、听记、闪记、录音摘要 |
+| `report` | 日志 | 仅显式出现“日志”时使用 |
+| `image` | 图片 | 图片、截图 |
+| `link` | 链接 | 链接、URL、网址 |
+| `notable` | 多维表 / AI 表格 | AI表格、多维表、notable |
+| `baike` | 企业百科 | 企业百科、百科 |
+| `mail` | 邮件 | 邮件、邮箱、mail、email |
+
+### behavior-type 可选值
+
+| 值 | 含义 | 示例 |
+|----|------|------|
+| `all` | 全部行为（默认） | “智能化方案相关内容” |
+| `send` | 发送 | “我发给汐峰的消息/邮件” |
+| `create` | 创建 | “我创建过哪些文档” |
+| `share` | 分享 | “我分享过的资料” |
+| `edit` | 编辑 | “我编辑过的文档” |
+| `receive` | 接收 | “汐峰发给我的文档”、“我收到的邮件” |
+
+### 参数提取规则
+
+- `queries` 只放内容关键词，不放时间、类型词、行为词。比如“本周我创建的智能化方案文档”中，`queries=智能化方案`。
+- `types` 放内容类型，映射规则与 enterprise 相同；所有类型词都不能留在 `--query/--queries`，多类型用逗号分隔。
+- 文档/资料/方案类型使用底层枚举 `document`（注意不是 `doc`）。`report` 仅在用户显式说“日志”时触发；“周报/日报/月报/工作汇报”不要自动映射为 `report`。
+- `mail` 仅在用户显式说“邮件/邮箱/mail/email”时触发；一旦触发，必须进入 `--types mail`。
+- `time-range` 仅当用户显式给出时间词时填写，不要根据语义猜时间。
+- `direction` 仅当用户明确指定交互对象时填写，格式为 `发起者->接收者` 或 `我<->某人`；无具体对象时留空。
+- “今天我干了什么/我最近做过什么”这类行为汇总场景，用 `--types all`，`--queries` 可留空。
+
+| 用户说 | queries | types | behavior-type | time-range | direction | chat-scope |
+|--------|---------|-------|---------------|------------|-----------|------------|
+| “我发给汐峰的邮件” | 空 | mail | send | 空 | 我->汐峰 | 空 |
+| “我发给汐峰的消息和邮件” | 空 | im,mail | send | 空 | 我->汐峰 | 空 |
+| “汐峰发给我的文档” | 空 | document | receive | 空 | 汐峰->我 | 空 |
+| “我创建过哪些文档” | 空 | document | create | 空 | 空 | 空 |
+| “本周我创建的智能化方案文档” | 智能化方案 | document | create | 本周 | 空 | 空 |
+| “我分享过的项目链接和图片” | 项目 | link,image | share | 空 | 空 | 空 |
+| “我在 scrum 群里发了什么” | 空 | im | send | 空 | 空 | scrum群 |
+| “帮我总结今天干了什么” | 空 | all | all | 今天 | 空 | 空 |
+
+## 行为搜索 vs 知识搜索
+
+- `aisearch behavior`：用户问“我/某人做过什么动作”，有发送、创建、分享、编辑、接收、收到、发给等行为词。
+- `aisearch enterprise`：用户问“是什么/怎么做/在哪里/模板/方案/总结”，目标是内容本身或跨类型知识内容汇总。

package/skills/dws/dingtalk-aisearch/references/intent-guide.md

@@ -0,0 +1,15 @@
+# aisearch 局部意图消歧
+
+本文件从单 Skill `intent-guide.md` 拆分而来，仅保留与本产品相关的跨产品消歧规则。
+
+| 用户说... | 真实意图 | 应该用 | 不要用 | 理由 |
+|---|---|---|---|---|
+| "张三在哪个部门/张三的工号是多少" | 搜人后查通讯录详情 | `aisearch person` → `contact user get` | 直接 `contact user search` | 姓名或工号先由 aisearch 获取 userId，再由 contact 补部门、工号等详情 |
+| "找一下张三/搜同事/找人" | 人员语义搜索 | `aisearch person` | `contact user search` | 姓名模糊搜索、工号、部门、职责和上下级走 aisearch；contact 在拿到 userId 后补详情 |
+| "五道的上级是谁/谁负责XX/XX的下属有谁" | AI语义搜人 | `aisearch person` | `contact` | 涉及上下级、职责、负责人等语义维度搜索，用 aisearch |
+| "222020这个工号是谁/查工号" | 按工号搜人 | `aisearch person --dimension jobNumber` | `contact` | 工号查人走 aisearch，dimension=jobNumber |
+| "13800138000是谁/完整手机号反查" | 精确手机号反查 | `contact user search-mobile` | `contact user search` | 完整手机号精确匹配使用 search-mobile |
+| "按手机号线索找人" | 手机号语义搜人 | `aisearch person --dimension phone` | `contact user search` | 非精确手机号匹配走 aisearch 的 phone 维度 |
+| "搜一下智能化方案/最近 OKR 相关邮件/最近发版相关消息" | 搜企业知识内容 | `aisearch enterprise` | `doc search` / `mail search` / `chat message search` | 跨文档、消息、日程、听记、邮件等企业内容语义检索走 enterprise；具体 `queries/types/time-range` 抽槽见 `aisearch.md` |
+| "我发给某人的消息/邮件/文档/今天我干了什么" | 搜行为记录 | `aisearch behavior` | `chat` / `mail` / `doc` / `report` | 关注“谁对什么做过什么”，走 behavior；具体 `behavior-type/direction/chat-scope` 抽槽见 `aisearch.md` |
+| "把这段文字翻译成英文/translate this" | 通用文本翻译 | `chat text translate` | `doc` / `aisearch` | 纯文本翻译，不是文档编辑或语义搜索 |

package/skills/dws/dingtalk-aisearch/references/lite-recipes.md

@@ -0,0 +1,31 @@
+# aisearch Lite Recipe
+
+本文件从单 Skill `lite-recipes.md` 拆分而来，仅保留与本产品相关的轻量流程。
+
+## #8 通讯录
+
+### get-contact-self
+
+`contact user get-self` → 当前用户 userId、部门、主管等
+
+### search-person
+
+**搜人首选入口**。凡是“找人/搜人/找同事/谁负责/上级/下级/负责人/团队成员”均优先用 `aisearch person`：
+
+1. 从用户问题中提取 keyword（人名/业务关键词）和 dimension（维度），规则见 [aisearch.md](./aisearch.md)。
+2. `aisearch person --query "<关键词>" --dimension <维度>`
+3. 结果中提取 `userId` 和 `title`（姓名）展示给用户。
+4. 若需要 userId 做后续操作（发消息/建待办），可直接使用结果中的 `userId`。
+5. **重名消歧**：多人同名时禁止默认选第一个，须追加 `contact user get --ids` 获取部门/职位后请用户确认，详见 [08-directory.md](../../dingtalk-contact/references/08-directory.md)「多命中」。
+
+### search-user
+
+仅在以下**精确查询**场景使用，搜人请优先用 `search-person`：
+
+- 需要获取 userId 给其他产品使用（发消息/建待办/约日程）
+- 已有 userId 需查完整详情（`contact user get --ids`）
+- 完整手机号精确反查（`contact user search-mobile --mobile`）
+
+1. 完整手机号精确反查：`contact user search-mobile --mobile "<手机号>"`；其他搜人：`aisearch person --query "<关键词>" --dimension <维度>`。
+2. **重名消歧**：多人同名时禁止默认选第一个，须追加 `contact user get --ids` 获取部门/职位后请用户确认，详见 [08-directory.md](../../dingtalk-contact/references/08-directory.md)「多命中」。
+3. 需详情时：`contact user get --ids <userId>`（多人可 `--ids id1,id2,...`）。