@wagemule/daemon 0.1.0 → 0.1.3

package/dist/skills/larksuite/lark-task/references/lark-task-reminder.md

@@ -0,0 +1,36 @@
+# task +reminder
+
+> **Prerequisites:** Please read `../lark-shared/SKILL.md` to understand authentication, global parameters, and security rules.
+> **Priority:** For creating or modifying task reminder times, prioritize using this `+reminder` shortcut over other task update methods. It provides a more reliable and direct way to manage reminders.
+
+Manage task reminders. Set new reminders or remove existing ones. Note that setting a task reminder requires a due date.
+
+## Recommended Commands
+
+```bash
+# Set a reminder (e.g., 30 minutes before due)
+lark-cli task +reminder --task-id "<task_guid>" --set "30"
+
+# Set a reminder (e.g., 1 hour before due)
+lark-cli task +reminder --task-id "<task_guid>" --set "1h"
+
+# Remove all reminders
+lark-cli task +reminder --task-id "<task_guid>" --remove "true"
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `--task-id <guid>` | Yes | The task GUID to modify. For Feishu task applinks, use the `guid` query parameter, not the `suite_entity_num` / display task ID like `t104121`. |
+| `--set <val>` | No | Relative fire minutes before the due time. Supports numbers (e.g., `30`) or units (e.g., `15m`, `1h`, `1d`). |
+| `--remove <bool>` | No | If set to `true`, removes all existing reminders from the task. |
+
+## Workflow
+
+1. Confirm the task and reminder action.
+2. Execute the command.
+3. Report success.
+
+> [!CAUTION]
+> This is a **Write Operation** -- You must confirm the user's intent before executing.

package/dist/skills/larksuite/lark-task/references/lark-task-reopen.md

@@ -0,0 +1,27 @@
+# task +reopen
+
+> **Prerequisites:** Please read `../lark-shared/SKILL.md` to understand authentication, global parameters, and security rules.
+
+Reopen a previously completed task.
+
+## Recommended Commands
+
+```bash
+# Reopen a task
+lark-cli task +reopen --task-id "<task_guid>"
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `--task-id <guid>` | Yes | The task GUID to reopen. For Feishu task applinks, use the `guid` query parameter, not the `suite_entity_num` / display task ID like `t104121`. |
+
+## Workflow
+
+1. Confirm the task to reopen.
+2. Execute the command.
+3. Report success.
+
+> [!CAUTION]
+> This is a **Write Operation** -- You must confirm the user's intent before executing.

package/dist/skills/larksuite/lark-task/references/lark-task-search.md

@@ -0,0 +1,41 @@
+# task +search
+
+> **Prerequisites:** Please read `../lark-shared/SKILL.md` to understand authentication, global parameters, and security rules.
+>
+> **⚠️ Note:** This API must be called with a user identity. **Do NOT use an app identity, otherwise the call will fail.**
+
+Search tasks by keyword and optional filters.
+
+## Recommended Commands
+
+```bash
+# Search by keyword
+lark-cli task +search --query "test"
+
+# Search incomplete tasks assigned to specific users
+lark-cli task +search --assignee "ou_xxx,ou_yyy" --completed=false
+
+# Search by due time range
+lark-cli task +search --query "release" --due "-1d,+7d"
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `--query <string>` | No | Search keyword. If omitted, at least one filter must be provided. |
+| `--creator <ids>` | No | Creator open_ids, comma-separated. |
+| `--assignee <ids>` | No | Assignee open_ids, comma-separated. |
+| `--follower <ids>` | No | Follower open_ids, comma-separated. |
+| `--completed=<bool>` | No | Filter by completion state. |
+| `--due <range>` | No | Due time range in `start,end` form. Each side supports ISO/date/relative/ms input. |
+| `--page-token <string>` | No | Page token for pagination. |
+| `--page-all` | No | Automatically paginate through all pages (max 40). |
+| `--page-limit <int>` | No | Max page limit (default 20). |
+
+## Workflow
+
+1. Build the keyword and filters from the user's request.
+2. Execute `lark-cli task +search ...`
+3. Report the matched tasks and include the next `page_token` if more results exist.
+

package/dist/skills/larksuite/lark-task/references/lark-task-set-ancestor.md

@@ -0,0 +1,32 @@
+# task +set-ancestor
+
+> **Prerequisites:** Please read `../lark-shared/SKILL.md` to understand authentication, global parameters, and security rules.
+
+Set a parent task for a task, or clear the parent to make it independent.
+
+## Recommended Commands
+
+```bash
+# Set a parent task
+lark-cli task +set-ancestor --task-id "guid_1" --ancestor-id "guid_2"
+
+# Clear the parent task
+lark-cli task +set-ancestor --task-id "guid_1"
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `--task-id <guid>` | Yes | The task GUID to update. |
+| `--ancestor-id <guid>` | No | The parent task GUID. Omit it to clear the ancestor. |
+
+## Workflow
+
+1. Confirm the child task and, if applicable, the ancestor task.
+2. Execute `lark-cli task +set-ancestor ...`
+3. Report the updated task GUID and whether the ancestor was set or cleared.
+
+> [!CAUTION]
+> This is a **Write Operation** -- You must confirm the user's intent before executing.
+

package/dist/skills/larksuite/lark-task/references/lark-task-subscribe-event.md

@@ -0,0 +1,86 @@
+# task +subscribe-event
+
+> **Prerequisites:** Please read `../lark-shared/SKILL.md` to understand authentication, global parameters, and security rules.
+>
+> **⚠️ Note:** This API supports both `user` and `bot` identities. Use `user` to subscribe the current user's accessible tasks; use `bot` to subscribe tasks the **application is responsible for**.
+
+Subscribe task update events with the current identity.
+
+This shortcut is different from `event +subscribe`:
+- `task +subscribe-event` registers task-event access for the **current identity**
+- with `--as user`, it subscribes the **current user** to task events for tasks they created, are responsible for, or follow
+- with `--as bot`, it subscribes using the **application identity** for tasks the application is responsible for
+
+The task event type is:
+
+```text
+task.task.update_user_access_v2
+```
+
+Within this event, task changes are represented by commit types (string values). Deduped list:
+
+```text
+task_assignees_update
+task_completed_update
+task_create
+task_deleted
+task_desc_update
+task_followers_update
+task_reminders_update
+task_start_due_update
+task_summary_update
+```
+
+Event payload shape (example):
+
+```json
+{
+  "event_id": "evt_xxx",
+  "event_types": ["task_summary_update"],
+  "task_guid": "task_guid_xxx",
+  "timestamp": "1775793266152",
+  "type": "task.task.update_user_access_v2"
+}
+```
+
+- `type`: event type, should be `task.task.update_user_access_v2`
+- `event_id`: unique event id (useful for dedup)
+- `event_types`: list of commit types (see the deduped list above)
+- `task_guid`: the task GUID that changed
+- `timestamp`: event timestamp (ms)
+
+In practice, this means:
+- with `--as user`, the subscribed user can receive updates for tasks visible to them through authorship, assignment, or following
+- with `--as bot`, the subscription covers tasks the application is responsible for
+
+To actually receive the subscribed events, use the standard event WebSocket receiver:
+
+```bash
+lark-cli event +subscribe --event-types task.task.update_user_access_v2 --compact --quiet
+```
+
+The full flow is:
+1. Register the subscription with `lark-cli task +subscribe-event [--as user|bot]`
+2. Receive those events with `lark-cli event +subscribe --event-types task.task.update_user_access_v2 ...`
+
+## Recommended Commands
+
+```bash
+lark-cli task +subscribe-event
+```
+# Subscribe with app identity
+lark-cli task +subscribe-event --as bot
+
+
+## Parameters
+
+This shortcut has no additional parameters.
+
+## Workflow
+
+1. Confirm whether the user wants to subscribe with `user` identity or `bot` identity.
+2. Execute `lark-cli task +subscribe-event`
+3. Report whether the subscription succeeded, and clarify which identity the subscription applies to.
+
+> [!CAUTION]
+> This is a **Write Operation** -- You must confirm the user's intent before executing.

package/dist/skills/larksuite/lark-task/references/lark-task-tasklist-create.md

@@ -0,0 +1,35 @@
+# task +tasklist-create
+
+> **Prerequisites:** Please read `../lark-shared/SKILL.md` to understand authentication, global parameters, and security rules.
+
+Create a new tasklist, and optionally batch create tasks within it.
+
+## Recommended Commands
+
+```bash
+# Create an empty tasklist
+lark-cli task +tasklist-create --name "Q1 Goals"
+
+# Create a tasklist and add members
+lark-cli task +tasklist-create --name "Project A" --member "ou_xxx,ou_yyy"
+
+# Create a tasklist and batch create tasks within it
+lark-cli task +tasklist-create --name "Launch Checklist" --data '[{"summary": "Code Review", "assignee": "ou_aaa"}, {"summary": "Deploy", "assignee": "ou_bbb"}]'
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `--name <text>` | Yes | The name of the tasklist. |
+| `--member <ids>` | No | Comma-separated list of user `open_id`s to add as editors. |
+| `--data <json>` | No | JSON array of task definitions to create and add to the tasklist automatically. |
+
+## Workflow
+
+1. Confirm the tasklist name, members, and tasks (if any).
+2. Execute the command `lark-cli task +tasklist-create ...`.
+3. Report success, including the new tasklist ID and the result of the batch task creation.
+
+> [!CAUTION]
+> This is a **Write Operation** -- You must confirm the user's intent before executing.

package/dist/skills/larksuite/lark-task/references/lark-task-tasklist-members.md

@@ -0,0 +1,36 @@
+# task +tasklist-members
+
+> **Prerequisites:** Please read `../lark-shared/SKILL.md` to understand authentication, global parameters, and security rules.
+
+Manage tasklist members (editors/owners).
+
+## Recommended Commands
+
+```bash
+# Add a member
+lark-cli task +tasklist-members --tasklist-id "tl_xxx" --add "ou_aaa"
+
+# Remove a member
+lark-cli task +tasklist-members --tasklist-id "tl_xxx" --remove "ou_aaa"
+
+# Replace all members exactly
+lark-cli task +tasklist-members --tasklist-id "tl_xxx" --set "ou_aaa,ou_bbb"
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `--tasklist-id <id>` | Yes | The GUID of the tasklist, or a full AppLink URL. |
+| `--add <ids>` | No | Comma-separated list of user `open_id`s to add as members. |
+| `--remove <ids>` | No | Comma-separated list of user `open_id`s to remove from members. |
+| `--set <ids>` | No | Comma-separated list of user `open_id`s to exactly set as members (replaces all existing). |
+
+## Workflow
+
+1. Confirm the tasklist and members to add/remove/set.
+2. Execute the command.
+3. Report success.
+
+> [!CAUTION]
+> This is a **Write Operation** -- You must confirm the user's intent before executing.

package/dist/skills/larksuite/lark-task/references/lark-task-tasklist-search.md

@@ -0,0 +1,38 @@
+# task +tasklist-search
+
+> **Prerequisites:** Please read `../lark-shared/SKILL.md` to understand authentication, global parameters, and security rules.
+>
+> **⚠️ Note:** This shortcut uses tasklist search followed by tasklist detail queries to render the final output.
+
+Search tasklists by keyword and optional filters.
+
+## Recommended Commands
+
+```bash
+# Search by keyword
+lark-cli task +tasklist-search --query "测试"
+
+# Search tasklists created by specific users
+lark-cli task +tasklist-search --creator "ou_xxx,ou_yyy"
+
+# Search by creation time range
+lark-cli task +tasklist-search --query "Q2" --create-time "-30d,+0d"
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `--query <string>` | No | Search keyword. If omitted, at least one filter must be provided. |
+| `--creator <ids>` | No | Creator open_ids, comma-separated. |
+| `--create-time <range>` | No | Creation time range in `start,end` form. Each side supports ISO/date/relative/ms input. |
+| `--page-token <string>` | No | Page token for pagination. |
+| `--page-all` | No | Automatically paginate through all pages (max 40). |
+| `--page-limit <int>` | No | Max page limit (default 20). |
+
+## Workflow
+
+1. Build the search keyword and filters from the user's request.
+2. Execute `lark-cli task +tasklist-search ...`
+3. Report the matched tasklists and the next `page_token` if more results exist.
+

package/dist/skills/larksuite/lark-task/references/lark-task-tasklist-task-add.md

@@ -0,0 +1,38 @@
+# task +tasklist-task-add
+
+> **Prerequisites:** Please read `../lark-shared/SKILL.md` to understand authentication, global parameters, and security rules.
+
+Add existing tasks to a tasklist.
+
+## Recommended Commands
+
+```bash
+# Add a single task to a tasklist
+lark-cli task +tasklist-task-add --tasklist-id "<tasklist_guid>" --task-id "<task_guid>"
+
+# Add multiple tasks to a tasklist
+lark-cli task +tasklist-task-add --tasklist-id "<tasklist_guid>" --task-id "<task_guid>,<another_task_guid>,<third_task_guid>"
+
+# Add a task to a specific section in the tasklist
+lark-cli task +tasklist-task-add \
+  --tasklist-id "<tasklist_guid>" \
+  --task-id "<task_guid>" \
+  --section-guid "<section_guid>"
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `--tasklist-id <guid>` | Yes | The GUID of the tasklist, or a full AppLink URL. |
+| `--task-id <guids>` | Yes | Comma-separated list of task GUIDs to add to the tasklist. For Feishu task applinks, use each task's `guid` query parameter, not the `suite_entity_num` / display task ID like `t104121`. |
+| `--section-guid <guid>` | No | The GUID of the custom section to add the tasks to. If omitted, tasks will be added to the default section. |
+
+## Workflow
+
+1. Confirm the tasklist and the tasks to add.
+2. Execute the command `lark-cli task +tasklist-task-add ...`.
+3. Report the result (successful vs failed tasks).
+
+> [!CAUTION]
+> This is a **Write Operation** -- You must confirm the user's intent before executing.

package/dist/skills/larksuite/lark-task/references/lark-task-update.md

@@ -0,0 +1,37 @@
+# task +update
+
+> **Prerequisites:** Please read `../lark-shared/SKILL.md` to understand authentication, global parameters, and security rules.
+
+Update an existing task in Lark.
+
+## Recommended Commands
+
+```bash
+# Update task summary
+lark-cli task +update --task-id "<task_guid>" --summary "New Summary"
+
+# Update multiple tasks' due dates
+lark-cli task +update --task-id "<task_guid>,<another_task_guid>" --due "+2d"
+
+# Update with JSON data
+lark-cli task +update --task-id "<task_guid>" --data '{"description": "New description"}'
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `--task-id <guid>` | Yes | The task GUID to update. Comma-separated task GUIDs are supported for multiple tasks. For Feishu task applinks, use the `guid` query parameter, not the `suite_entity_num` / display task ID like `t104121`. |
+| `--summary <text>` | No | New summary/title for the task. |
+| `--description <text>` | No | New description for the task. |
+| `--due <time>` | No | New due date (supports relative time). |
+| `--data <json>` | No | JSON payload for fields to update. |
+
+## Workflow
+
+1. Confirm with the user the tasks to update and the fields.
+2. Execute `lark-cli task +update --task-id "..." ...`
+3. Report the successful updates.
+
+> [!CAUTION]
+> This is a **Write Operation** -- You must confirm the user's intent before executing.

package/dist/skills/larksuite/lark-task/references/lark-task-upload-attachment.md

@@ -0,0 +1,59 @@
+# task +upload-attachment
+
+> **Prerequisites:** Please read `../lark-shared/SKILL.md` to understand authentication, global parameters, and security rules.
+
+Upload a single local file as an attachment to a task (or any resource type accepted by the Task attachment endpoint). Max file size per upload is **50 MB**. For task agents, use `--resource-type=task_delivery`.
+
+## Recommended Commands
+
+```bash
+# Upload a local file as a task attachment (relative path required)
+lark-cli task +upload-attachment \
+  --resource-id "<task_guid>" \
+  --file "./report.pdf"
+
+# Pass a Feishu task applink instead of a raw guid — the guid is extracted automatically
+lark-cli task +upload-attachment \
+  --resource-id "https://applink.feishu.cn/client/todo/task?guid=<task_guid>" \
+  --file "./note.md"
+
+# Explicit resource type / user id type
+lark-cli task +upload-attachment \
+  --resource-id "<task_guid>" \
+  --resource-type task \
+  --user-id-type open_id \
+  --file "./design.png"
+
+# Upload a local file to a task agent
+lark-cli task +upload-attachment \
+  --resource-id "4b113c53-a68b-419f-8bd0-c9c532a3285a" \
+  --file "./飞书.zip" \
+  --resource-type task_delivery
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `--resource-id <guid_or_applink>` | Yes | Target resource GUID. Accepts a raw task GUID or a Feishu task applink URL (`.../client/todo/task?guid=...`); the `guid` query parameter is extracted automatically. Do not use `suite_entity_num` / display IDs like `t104121`. |
+| `--file <path>` | Yes | Local file path to upload. Must be a relative path within the current working directory; absolute paths and paths escaping the cwd are rejected. Single file only, ≤ 50 MB. |
+| `--resource-type <type>` | No | Owning resource type. Defaults to `task`. Use `task_delivery` when uploading to task agents. |
+| `--user-id-type <type>` | No | User ID type for the request. Defaults to `open_id`. |
+
+## Workflow
+
+1. Confirm the target task GUID (or applink) and the local file path with the user.
+2. Ensure the file is within the current working directory and its size is ≤ 50 MB; otherwise ask the user to move/split the file.
+3. Determine if this is a task agent: if yes, add `--resource-type task_delivery`.
+4. Execute `lark-cli task +upload-attachment --resource-id "..." --file "..."`.
+5. Report the returned attachment record. The output exposes all fields returned by the API (e.g. `guid`, `name`, `size`, `url`, `uploader`, ...); always surface the attachment `guid` and, if present, the `url` so the user can jump to the attachment directly.
+
+## Output
+
+The command returns the single created attachment record as a flat JSON object — every field returned by the API (`guid`, `name`, `size`, `url`, `resource_type`, `resource_id`, `uploader`, ...) is preserved verbatim. Pretty mode also prints a human-readable summary with the resource, file name, size, and attachment GUID.
+
+> [!CAUTION]
+> This is a **Write Operation** -- You must confirm the user's intent before executing.
+
+> [!NOTE]
+> The Task attachment upload endpoint accepts exactly one file per call. To upload multiple files, invoke the shortcut once per file.

package/dist/skills/larksuite/lark-vc/SKILL.md

@@ -0,0 +1,168 @@
+---
+name: lark-vc
+version: 1.0.0
+description: "飞书视频会议：搜索历史会议、查询会议纪要产物（总结、待办、章节、逐字稿）、查询会议参会人快照。1. 查询已经结束的会议数量或详情时使用本技能（如历史日期｜昨天｜上周｜今天已经开过的会议等场景），查询未开始的会议日程使用 lark-calendar 技能。2. 支持通过关键词、时间范围、组织者、参与者、会议室等筛选条件搜索会议。3. 获取或整理会议纪要、逐字稿、录制产物时使用本技能。4. 查询“谁参加过某会议”“参会人列表”等参会人快照信息用 vc meeting get --with-participants（任意时点可查，含已结束会议）。注意：**Agent 真实入会/离会、感知正在进行中会议的实时事件**请使用 lark-vc-agent 技能，本技能不覆盖写操作和会中事件流。"
+metadata:
+  requires:
+    bins: ["lark-cli"]
+  cliHelp: "lark-cli vc --help"
+---
+
+# vc (v1)
+
+**CRITICAL — 开始前 MUST 先用 Read 工具读取 [`../lark-shared/SKILL.md`](../lark-shared/SKILL.md)，其中包含认证、权限处理**
+
+## 核心概念
+
+- **视频会议（Meeting）**：飞书视频会议实例，通过 meeting\_id 标识。已结束的会议支持通过关键词、时间段、参会人、组织者、会议室等条件搜索（见 `+search`）。
+- **会议纪要（Note）**：视频会议结束后生成的结构化文档，包含纪要文档（包含总结、待办、章节）和逐字稿文档。
+- **妙记（Minutes）**：来源于飞书视频会议的录制产物或用户上传的音视频文件，支持视频/音频的转写和会议纪要，通过 minute\_token 标识。
+- **纪要文档（MainDoc）**：AI 智能纪要的主文档，包含 AI 生成的总结和待办，对应 `note_doc_token`。
+- **用户会议纪要（MeetingNotes）**：用户主动绑定到会议的纪要文档，对应 `meeting_notes`。仅通过 `--calendar-event-ids` 路径返回。
+- **逐字稿（VerbatimDoc）**：会议的逐句文字记录，包含说话人和时间戳。
+
+## 核心场景
+
+### 1. 搜索会议记录
+1. 仅支持搜索已结束的会议，对于还未开始的未来会议，需要使用 lark-calendar 技能。
+2. 仅支持使用关键词、时间段、参会人、组织者、会议室等筛选条件搜索会议记录，对于不支持的筛选条件，需要提示用户。
+3. 搜索结果存在多条数据时，务必注意分页数据获取，不要遗漏任何会议记录。
+
+### 2. 整理会议纪要
+1. 整理纪要文档时默认给出纪要文档和逐字稿链接即可，无需读取纪要文档或逐字稿内容。
+2. 用户明确需要获取纪要文档中的总结、待办、章节产物时，再读取文档获取具体内容。
+3. 读取智能纪要（`note_doc_token`）内容时，纪要文档的**第一个 `<whiteboard>`** 标签是封面图（AI 生成的总结可视化），应同时下载展示给用户：
+```bash
+# 1. 读取纪要内容
+lark-cli docs +fetch --api-version v2 --doc <note_doc_token> --doc-format markdown
+# 2. 从返回的 markdown 中提取第一个 <whiteboard token="xxx"/> 的 token
+# 3. 下载封面图到聚合目录（和逐字稿、录像同目录，保持产物归拢）
+#    并非所有纪要都有封面画板，没有 <whiteboard> 标签时跳过即可
+lark-cli docs +media-download --type whiteboard --token <whiteboard_token> --output ./minutes/<minute_token>/cover
+```
+> **产物目录规范**：同一会议的所有下载产物（录像、逐字稿、封面图等）统一放到 `./minutes/{minute_token}/` 目录下。这与 `minutes +download` 和 `vc +notes --minute-tokens` 的默认落点保持一致，便于 Agent 聚合。显式路径（如封面图）需手动对齐到同一目录。
+
+> **纪要相关文档 — 根据用户意图选择：**
+> - `note_doc_token` → **AI 智能纪要**（AI 总结 + 待办 + 章节）
+> - `meeting_notes` → **用户绑定的会议纪要**（用户主动关联到会议的文档，仅 `--calendar-event-ids` 路径返回）
+> - `verbatim_doc_token` → **逐字稿**（完整的逐句文字记录，含说话人和时间戳）— 用户说"逐字稿""完整记录""谁说了什么"时用这个
+> - 用户说"纪要""总结""纪要内容"时，应同时返回 `note_doc_token` 和 `meeting_notes`（如有）
+> - 用户意图不明确时，应展示所有文档链接让用户选择，而不是替用户决定
+> - 如果用户提供的是**本地音视频文件**并说"转纪要""转逐字稿"，不要直接从 `vc +notes` 开始；应先用 [minutes +upload](../lark-minutes/references/lark-minutes-upload.md) 生成 `minute_url`，再提取 `minute_token` 调用 `vc +notes --minute-tokens`
+
+### 3. 纪要文档与逐字稿链接
+1. 纪要文档、逐字稿文档与关联的共享文档默认使用文档 Token 返回。
+2. 仅需要获取文档名称和 URL 等基本信息时，使用 `lark-cli drive metas batch_query` 查询
+```bash
+# 学习命令使用方式
+lark-cli schema drive.metas.batch_query
+
+# 批量获取文档基本信息: 一次最多查询 10 个文档
+lark-cli drive metas batch_query --data '{"request_docs": [{"doc_type": "docx", "doc_token": "<doc_token>"}], "with_url": true}'
+```
+3. 需要获取文档内容时，使用 `lark-cli docs +fetch --api-version v2`。
+```bash
+# 获取文档内容
+lark-cli docs +fetch --api-version v2 --doc <doc_token> --doc-format markdown
+```
+
+### 4. 查询参会人快照（读操作）
+
+用户问"谁参加过这场会议""这个会议有哪些参会人""某某参会了吗"等**参会人快照**类问题时，使用 **`vc meeting get --with-participants`**：这是参会人服务端快照 API，不依赖 bot 身份参会，**已结束会议也可查**：
+
+```bash
+lark-cli vc meeting get --params '{"meeting_id":"<meeting_id>","with_participants":true}'
+```
+
+选型判断表：
+
+| 用户意图 | 推荐命令 | 所在 skill |
+|---------|---------|--------|
+| 参会人快照（谁参加过、何时入/离会，任意时点）| `vc meeting get --with-participants` | 本 skill |
+| 已结束会议的发言内容 | `vc +notes` 取 `verbatim_doc_token` 再 `docs +fetch --api-version v2` | 本 skill |
+| **进行中会议**的实时事件流（转写、聊天、共享、会中加入/离开）| `vc +meeting-events` | [`lark-vc-agent`](../lark-vc-agent/SKILL.md) |
+| **Agent 真实入会 / 离会** | `vc +meeting-join` / `vc +meeting-leave` | [`lark-vc-agent`](../lark-vc-agent/SKILL.md) |
+
+## 资源关系
+
+```
+Meeting (视频会议)
+├── Note (会议纪要)
+│   ├── MainDoc (AI 智能纪要文档, note_doc_token)
+│   ├── MeetingNotes (用户绑定的会议纪要文档, meeting_notes)
+│   ├── VerbatimDoc (逐字稿, verbatim_doc_token)
+│   └── SharedDoc (会中共享文档)
+└── Minutes (妙记) ← minute_token 标识，+recording 从 meeting_id 获取
+    ├── Transcript (文字记录)
+    ├── Summary (总结)
+    ├── Todos (待办)
+    └── Chapters (章节)
+```
+
+> **注意**：`+search` 只能查询已结束的历史会议。查询未来的日程安排请使用 [lark-calendar](../lark-calendar/SKILL.md)。
+>
+> **优先级**：当用户搜索历史会议时，应优先使用 `vc +search` 而非 `calendar events search`。calendar 的搜索面向日程，vc 的搜索面向已结束的会议记录，支持按参会人、组织者、会议室等维度过滤。
+>
+> **路由规则**：如果用户在问“开过的会”“今天开了哪些会”“最近参加过什么会”“已结束的会议”“历史会议记录”，优先使用 `vc +search`。只有在查询未来日程、待开的会、agenda 时才优先使用 [lark-calendar](../lark-calendar/SKILL.md)。
+>
+> **妙记边界**：`+notes` 负责纪要内容、逐字稿和 AI 产物；妙记基础信息请优先看 [`+recording`](references/lark-vc-recording.md) 与 [lark-minutes](../lark-minutes/SKILL.md)。
+>
+> **文件转纪要边界**：如果用户给的是本地音视频文件，并希望得到纪要、逐字稿、总结、待办或章节，入口应先走 [lark-minutes](../lark-minutes/SKILL.md) 的上传流程生成 `minute_url` / `minute_token`，再回到 `vc +notes --minute-tokens` 获取内容产物。
+>
+> **特殊情况**: 当用户查询“今天有哪些会议”时，通过 `vc +search` 查询今天开过的会议记录，同时使用 lark-calendar 技能查询今天还未开始的会议，统一整理后展示给用户。
+
+## Shortcuts（推荐优先使用）
+
+Shortcut 是对常用操作的高级封装（`lark-cli vc +<verb> [flags]`）。有 Shortcut 的操作优先使用。
+
+| Shortcut | 说明 |
+|----------|------|
+| [`+search`](references/lark-vc-search.md) | Search meeting records (requires at least one filter) |
+| [`+notes`](references/lark-vc-notes.md) | Query meeting notes (via meeting-ids, minute-tokens, or calendar-event-ids) |
+| [`+recording`](references/lark-vc-recording.md) | Query minute_token from meeting-ids or calendar-event-ids |
+
+- 使用 `+search` 命令时，必须阅读 [references/lark-vc-search.md](references/lark-vc-search.md)，了解搜索参数和返回值结构。
+- 使用 `+notes` 命令时，必须阅读 [references/lark-vc-notes.md](references/lark-vc-notes.md)，了解查询参数、产物类型和返回值结构。
+- 使用 `+recording` 命令时，必须阅读 [references/lark-vc-recording.md](references/lark-vc-recording.md)，了解查询参数和返回值结构。
+
+> **Agent 参会相关命令已独立**：`+meeting-join` / `+meeting-leave` / `+meeting-events` 请使用 [`lark-vc-agent`](../lark-vc-agent/SKILL.md) 技能。
+
+## API Resources
+
+```bash
+lark-cli schema vc.<resource>.<method>   # 调用 API 前必须先查看参数结构
+lark-cli vc <resource> <method> [flags] # 调用 API
+```
+
+> **重要**：使用原生 API 时，必须先运行 `schema` 查看 `--data` / `--params` 参数结构，不要猜测字段格式。
+
+### meeting
+
+  - `get` — 获取会议详情（主题、时间、参会人、note_id）
+
+```bash
+# 获取会议基础信息：不包含参会人列表
+lark-cli vc meeting get --params '{"meeting_id": "<meeting_id>"}'
+
+
+# 获取会议基础信息：包含参会人列表
+lark-cli vc meeting get --params '{"meeting_id": "<meeting_id>", "with_participants": true}'
+```
+
+### minutes（跨域，详见 [lark-minutes](../lark-minutes/SKILL.md)）
+
+  - `get` — 获取妙记基础信息（标题、时长、封面）；查询纪要**内容**请用 `+notes --minute-tokens <minute-token>`
+
+## 权限表
+
+| 方法 | 所需 scope |
+|------|-----------|
+| `+notes --meeting-ids` | `vc:meeting.meetingevent:read`、`vc:note:read` |
+| `+notes --minute-tokens` | `vc:note:read`、`minutes:minutes:readonly`、`minutes:minutes.artifacts:read`、`minutes:minutes.transcript:export` |
+| `+notes --calendar-event-ids` | `calendar:calendar:read`、`calendar:calendar.event:read`、`vc:meeting.meetingevent:read`、`vc:note:read` |
+| `+recording --meeting-ids` | `vc:record:readonly` |
+| `+recording --calendar-event-ids` | `vc:record:readonly`、`calendar:calendar:read`、`calendar:calendar.event:read` |
+| `+search` | `vc:meeting.search:read` |
+| `meeting.get` | `vc:meeting.meetingevent:read` |
+
+> Agent 参会相关 scope（`vc:meeting.bot.join:write` / `vc:meeting.meetingevent:read`）见 [`lark-vc-agent`](../lark-vc-agent/SKILL.md)。