Skip to content
skillsafebeta
← Report library
Purpose / Other

Lark Calendar Skill Security Audit

What the author says it does (original text)

飞书日历：管理日历日程和会议室。查看/搜索日程、创建/更新日程、管理参会人、查询忙闲和推荐时段、预定会议室。当用户需要查看日程安排、创建/修改会议、查询/预定会议室时使用。不负责：查询过去的视频会议记录（走 lark-meeting）、待办任务（走 lark-task）。

Independent security check

Do not install or run it yet

This check is incomplete. Only available results are shown below.

Files checked
215
Risks found
13
Could it run dangerous commands?Looks for programs run straight after downloading, remote control of your computer, and hidden commands.Risks found: 3
Medium risk

Whiteboard workflows download and execute an npm version range without asking

Source references: 4
What we found

The whiteboard entry requires an unattended `npx -y` check, and its workflows repeatedly execute `@larksuite/whiteboard-cli@^0.2.13`. `-y` accepts installation automatically and `^` permits later compatible releases, with no visible hash or artifact pinning.

Why this matters

When whiteboard functionality is used, the downloaded package and install scripts can execute in the agent environment and access workspace files. A compromised package or distribution path would increase the impact.

The whiteboard entry requires running `npx -y @larksuite/whiteboard-cli@^0.2.13` without asking, and later workflows actually invoke it for rendering and conversion. `-y` accepts temporary installation automatically, while `^0.2.13` is not an exact version, so an uncached run may fetch and execute a later compatible npm release. No integrity check is visible. The dependency serves the stated whiteboard purpose, but creates supply-chain and local-code-execution risk; users can restrict network access and require an exact, verified version.

lark-whiteboard/SKILL.md:13In the instructionsOpen original file
> [!IMPORTANT]> - 运行 `lark-cli --version`，确认可用，无需询问用户。> - 运行 `npx -y @larksuite/whiteboard-cli@^0.2.13 -v`，确认可用，无需询问用户。**CRITICAL — 开始前 MUST 先用 Read 工具读取 [`../lark-shared/SKILL.md`](../lark-shared/SKILL.md)，其中包含认证、权限处理**
Show 3 other places
lark-whiteboard/routes/dsl.md:26In the instructionsOpen original file
Step 3: 渲染 & 审查 → 交付  - 渲染前自查（见下方检查清单）  - 渲染 PNG（仅用于预览验证，不是最终产物）：npx -y @larksuite/whiteboard-cli@^0.2.13 -i diagram.json -o diagram.png  - 检查：信息完整？布局合理？配色协调？文字无截断？连线无交叉？  - 有问题 → 按症状表修复 → 重新渲染（最多 2 轮）  - 2 轮后仍有严重问题 → 考虑走 Mermaid 路径兜底  - 写入画板：用 whiteboard-cli 将 diagram.json 转换为 OpenAPI 格式并 pipe 给 +update：      npx -y @larksuite/whiteboard-cli@^0.2.13 -i diagram.json --to openapi --format json \        | lark-cli whiteboard +update --whiteboard-token <board_token> \            --source - --input_format raw --idempotent-token <时间戳+标识> --as user      → 完整 dry-run / 确认流程见 [§ 写入画板](../references/lark-whiteboard-workflow.md#写入画板)
lark-whiteboard/routes/svg.md:33In the instructionsOpen original file
```建目录   ./diagrams/YYYY-MM-DDTHHMMSS/         (例：./diagrams/2026-04-15T143022/)写文件   <dir>/diagram.svg渲染     npx -y @larksuite/whiteboard-cli@^0.2.13 -i <dir>/diagram.svg -o <dir>/diagram.png -f svg检查     npx -y @larksuite/whiteboard-cli@^0.2.13 -i <dir>/diagram.svg -f svg --check导出     npx -y @larksuite/whiteboard-cli@^0.2.13 -i <dir>/diagram.svg -f svg --to openapi --format json > <dir>/diagram.json```
lark-whiteboard/routes/dsl.md:32In the instructionsOpen original file
  - 2 轮后仍有严重问题 → 考虑走 Mermaid 路径兜底  - 写入画板：用 whiteboard-cli 将 diagram.json 转换为 OpenAPI 格式并 pipe 给 +update：      npx -y @larksuite/whiteboard-cli@^0.2.13 -i diagram.json --to openapi --format json \        | lark-cli whiteboard +update --whiteboard-token <board_token> \            --source - --input_format raw --idempotent-token <时间戳+标识> --as user      → 完整 dry-run / 确认流程见 [§ 写入画板](../references/lark-whiteboard-workflow.md#写入画板)
Medium risk

Whiteboard conversion downloads and executes a third-party package through `npx -y` with a version range

Source references: 2
What we found

The workflow runs `npx -y @larksuite/whiteboard-cli@^0.2.13`. The `-y` flag accepts installation automatically, and the caret range can select a later compatible release rather than one reviewed build.

Why this matters

If the package, publisher account, or dependency chain is compromised, conversion executes supply-chain code with the agent’s local permissions and could access workspace files or alter writable content.

The active whiteboard workflow requires `npx -y @larksuite/whiteboard-cli@^0.2.13` for DSL/OpenAPI conversion. If absent locally, npm may automatically fetch and execute a package matching the caret range rather than a pinned build or hash. A compromised registry artifact or later compatible release would run with the caller's permissions and could access diagram data in the working directory. The evidence does not show that compromise occurred. Users can require an exact version, lockfile/checksum, trusted registry, and an isolated credential-free workspace.

lark-whiteboard/references/lark-whiteboard-workflow.md:84In the instructionsOpen original file
写入画板时按最终产物类型选择 `+update --input_format`：- Mermaid / PlantUML / SVG 产物直接写入时，`--input_format` 取单值 `mermaid` / `plantuml` / `svg`；写入非空已有画板并需要 overwrite 时，先确认会整板重建；SVG 修改已有画板时先走 [`../routes/svg-edit.md`](../routes/svg-edit.md) 的确认 workflow。- 只有 DSL 产物或已明确需要 OpenAPI 原生节点格式时，才先用 `npx -y @larksuite/whiteboard-cli@^0.2.13 --to openapi --format json` 转换，再用 `raw` 写入。具体命令示例、`--overwrite`、`--idempotent-token` 和 `--as user/bot` 的使用方式，统一参考 [`whiteboard +update`](./lark-whiteboard-update.md)。
Show 1 other places
lark-whiteboard/references/lark-whiteboard-update.md:90In the instructionsOpen original file
```bash# 生成 OpenAPI 格式到文件npx -y @larksuite/whiteboard-cli@^0.2.13 -i <DSL 文件> --to openapi --format json -o ./temp.json# 从文件读取并更新lark-cli whiteboard +update \  --whiteboard-token <画板Token> \  --idempotent-token <10+字符唯一串> \  --input_format raw \  --source @./temp.json \  --overwrite --as user```
Low risk

Creating an event adds several effects that were not individually requested

Source references: 3
What we found

`+create` automatically marks the event busy, adds a five-minute reminder, and creates a Lark video meeting by default.

Why this matters

A request for a basic calendar entry may also create a video-meeting entry, occupy free/busy time, and generate a reminder, changing calendar state beyond the minimal request.

These are active defaults of +create, not illustrative examples: the event blocks time as busy, adds a five-minute reminder, and includes a Lark video meeting. They are related to meeting creation, but a user requesting a simple calendar event may not expect the availability change, notification, or meeting entry. The source says changing these defaults requires the full API; users can specify different settings or no video meeting before creation.

references/lark-calendar-create.md:45In the instructionsOpen original file
> 自动设置 `attendee_ability: "can_modify_event"`，参会人可查看彼此并编辑日程。> 自动设置 `free_busy_status: "busy"`，默认日程忙闲状态为忙碌。> 自动设置 `reminders: [{"minutes": 5}]`，默认日程开始前 5 分钟提醒。> 自动设置 `vchat: {"vc_type": "vc"}`，默认日程包含飞书视频会议。如需其他视频会议类型或不含视频会议，请使用完整 API 命令。> 失败保护：若添加参会人失败（如 open_id 错误），CLI 会自动删除刚创建的空日程（回滚，不通知参会人）。
Show 2 other places
references/lark-calendar-create.md:46In the instructionsOpen original file
> 自动设置 `free_busy_status: "busy"`，默认日程忙闲状态为忙碌。> 自动设置 `reminders: [{"minutes": 5}]`，默认日程开始前 5 分钟提醒。> 自动设置 `vchat: {"vc_type": "vc"}`，默认日程包含飞书视频会议。如需其他视频会议类型或不含视频会议，请使用完整 API 命令。
references/lark-calendar-create.md:47In the instructionsOpen original file
> 自动设置 `reminders: [{"minutes": 5}]`，默认日程开始前 5 分钟提醒。> 自动设置 `vchat: {"vc_type": "vc"}`，默认日程包含飞书视频会议。如需其他视频会议类型或不含视频会议，请使用完整 API 命令。> 失败保护：若添加参会人失败（如 open_id 错误），CLI 会自动删除刚创建的空日程（回滚，不通知参会人）。
Could it expose your files or keys?Looks for uploads of files containing passwords or keys, and keys written directly in the code.Risks found: 4
Medium risk

Local images in event descriptions are automatically uploaded to cloud storage

Source references: 2
What we found

For event creation and updates, a relative image path in the description triggers an upload from the current working directory instead of remaining plain path text.

Why this matters

A screenshot or image containing sensitive information can leave the local workspace, be stored in Lark, and potentially become visible to event participants.

The source explicitly says that, during event creation or update, a relative local image path inside the current working directory is automatically uploaded to cloud storage and embedded. This is conditional and tied to inserting an image, not arbitrary file scanning; however, a referenced sensitive image would leave the device for Lark's cloud. A user can restrict descriptions to remote URLs/plain text or require confirmation of each local path before upload.

references/lark-calendar-create.md:35In the instructionsOpen original file
| `--end <time>` | 是 | 结束时间（ISO 8601，**必须带时区偏移**） || `--description <markdown>` | 否 | 日程描述，统一使用此字段，格式为 **Markdown**。提供会议议程、活动内容、注意事项或链接等。支持加粗、斜体、下划线（`<u>...</u>`）、删除线、链接 `[文本](url)`、标题（`# ` 到 `### `，最多三级）、引用（`> `）、有序/无序列表、GFM 表格（`\| 列1 \| 列2 \|` + 分隔行 `\| --- \| --- \|`）、以及图片 `![图片名](图片URL)`（标准 Markdown 图片语法：远程 URL 原样使用；**本地图片路径**（相对路径、且位于当前工作目录内）会自动上传到云盘并在端上内联渲染——绝对路径或工作目录之外的路径会报错；端上已有图片读回为 Markdown 图片）。飞书文档 URL（直接粘贴裸链接，或写成 `[文本](url)`）会自动解析为内联文档，端上展示文档标题而非裸链接。支持 `@文件路径` 或 `-`（stdin）读取。**禁止**用 `***文本***` 同时表示加粗+斜体（端上会残留 `*`）；应嵌套书写，如 `**<u>*~~文本~~*</u>**` 或 `*<u>**~~文本~~**</u>*`。|| `--attendee-ids <id_list>` | 否 | 参与人 ID 列表（逗号分隔）。支持用户（`ou_`）、群组（`oc_`）和会议室（`omm_`）。AI 提取时请务必保留对应前缀。bot 可作为合法参会人，无需剔除 |
Show 1 other places
references/lark-calendar-update.md:46In the instructionsOpen original file
| `--summary <text>` | 否 | 新日程标题。仅在显式传入 `--summary` 时更新；若传空字符串，会把标题清空 || `--description <markdown>` | 否 | 新日程描述，统一使用此字段，格式为 **Markdown**（加粗、斜体、下划线 `<u>...</u>`、删除线、链接 `[文本](url)`、标题 `# `~`### `（最多三级）、引用 `> `、有序/无序列表、GFM 表格 `\| 列1 \| 列2 \|` + 分隔行 `\| --- \| --- \|`、以及图片 `![图片名](图片URL)`（标准 Markdown 图片语法：远程 URL 原样使用；**本地图片路径**（相对路径、且位于当前工作目录内）会自动上传到云盘并在端上内联渲染——绝对路径或工作目录之外的路径会报错；端上已有图片读回为 Markdown 图片）。飞书文档 URL（裸链接或 `[文本](url)`）会自动解析为内联文档，端上展示文档标题。支持 `@文件路径` 或 `-`（stdin）读取。仅在显式传入时更新；传空字符串 `""` 会清空描述。**禁止**用 `***文本***` 同时表示加粗+斜体（端上会残留 `*`）；应嵌套书写，如 `**<u>*~~文本~~*</u>**` 或 `*<u>**~~文本~~**</u>*`。 || `--start <time>` | 否 | 新开始时间（ISO 8601，**必须带时区偏移**，如 `2026-03-12T14:00+08:00`；不带偏移会按进程时区解析致偏移）。更新日程时间时必须同时传 `--end` |
Medium risk

Attendee disambiguation is required to be stored in long-term memory

Source references: 2
What we found

After the user resolves multiple attendee matches, the scheduling workflow instructs the agent to “record long-term memory,” although persistent identity mapping is not necessary for calendar management.

Why this matters

If the environment supports persistent memory, names, identity choices, or contact relationships may be retained beyond the booking and influence future automatic selections. The evidence gives no storage location, retention period, or deletion mechanism.

This is an active scheduling instruction: when attendee search has multiple results, the agent must ask the user and also record “long-term memory.” The supplied material does not define storage location, retention, visibility, deletion, or prior consent. It could persist an association between a name and a specific account and influence future invitations. A user can require persistence to be disabled and keep disambiguation session-only.

references/lark-calendar-schedule-meeting.md:71In the instructionsOpen original file
搜索参与人出现多个结果无法唯一确定时，必须询问用户并记录长期记忆。
Show 1 other places
lark-contact/references/lark-contact-search-user.md:76In the instructionsOpen original file
搜常见姓名常返回多条同名结果。后续操作若有副作用(发消息、邀请会议等),把候选列给用户挑;**不要擅自选**。
Medium risk

Changing a recurring series time deletes existing exceptions

Source references: 3
What we found

When start or end time is changed for the whole recurring series, the workflow explicitly deletes exceptions before patching the master event. Those exceptions may contain date-specific adjustments.

Why this matters

Special arrangements for individual occurrences may be permanently lost or reset.

The source explicitly says that changing start/end with `--apply-to all` deletes existing exceptions before patching the master event. This may be consistent with “edit all” semantics, but exceptions can contain individual adjustments that would be lost. Users can require a list of affected exceptions and separate confirmation, or choose `single`/`this-and-following` scope.

references/lark-calendar-recurring.md:72In the instructionsOpen original file
# 编辑全部（主日程 id 或任意 例外/instance id）lark-cli calendar +update --event-id <uid_originalTime> --apply-to all --summary <summary># 编辑全部：改时间lark-cli calendar +update --event-id <uid_originalTime> --apply-to all --start <start> --end <end>
Show 2 other places
references/lark-calendar-recurring.md:84In the instructionsOpen original file
- **`--apply-to=all` 时的字段传播**：只把用户本次显式传的 flag 应用到每个例外和主日程。例外原本自定义过的其他字段（例如自己的描述）保持不变。- **`--apply-to=this-and-following` 的字段继承**：新创建的日程从原主日程继承 summary、description、rrule、start/end（用起始实例的时间）、vchat/reminders/location/visibility；用户任何显式传的 flag 优先。- **`--start/--end` 变更**：`all` 场景下，例外会被删除（原始占位已无意义），主日程再 PATCH；`this-and-following` 场景下，`--start/--end` 传了会作为新序列的时间，否则用起始实例的时间。- **参会人**：`this-and-following` 创建新序列时，若传了 `--add-attendee-ids`，会额外 添加attendees 到新序列；`--remove-attendee-ids` 会从新序列的参与人列表移除。
references/lark-calendar-update.md:68In the instructionsOpen original file
- 会议室是 resource attendee，必须使用 `omm_` ID 添加到参会人列表，不能脱离日程单独预定。- 更新重复性日程时，必须先确定操作范围（仅此次/全部/此次及后续），然后按 [重复性日程操作规范](lark-calendar-recurring.md) 执行。- 当同一次命令组合多个动作时，执行顺序为“日程字段 -> 移除参会人 -> 添加参会人”。若中途失败，不会自动回滚已成功步骤；错误信息会说明已完成的步骤。
Medium risk

Message reads collect reaction records and operator identities by default

Source references: 4
What we found

Four message-reading shortcuts automatically attach reactions unless `--no-reactions` is explicitly supplied. Reaction records contain operator IDs and types, so a request for message bodies can also retrieve who reacted and how.

Why this matters

When reaction-read permission is granted, the agent processes additional interpersonal activity and identity data, increasing access scope, output exposure, and audit burden.

Four message-reading shortcuts fetch and attach reactions by default unless `--no-reactions` is supplied. Reaction records can include the operator ID/type, timestamp, and emoji, so a request for message bodies alone may also process other people's interaction identity data and requires an additional read scope. Users can require `--no-reactions` whenever reaction analysis is unnecessary and withhold the `im:message.reactions:read` scope.

lark-im/SKILL.md:57In the instructionsOpen original file
### Default message enrichment (reactions / update_time)The four message-pulling shortcuts (`+messages-mget`, `+chat-messages-list`, `+messages-search`, `+threads-messages-list`) automatically attach a `reactions` block and (for edited messages) `update_time` to each returned message — no separate `im.reactions.batch_query` call is needed. Pass `--no-reactions` to opt out. For the full contract (output shape, the `im:message.reactions:read` scope requirement, and the "missing field ≠ fetch failure" data rules), read [`references/lark-im-message-enrichment.md`](references/lark-im-message-enrichment.md).
Show 3 other places
lark-im/references/lark-im-reactions.md:141In the instructionsOpen original file
|---|---|---|| `reaction_id` | `string` | Unique ID of this reaction record || `operator` | `object` | Identity of the user or app that added the reaction || `action_time` | `string` | Unix timestamp in milliseconds || `reaction_type` | `object` | Reaction payload. The key field is `emoji_type` |### `operator` Fields| Field | Type | Meaning ||---|---|---|| `operator.operator_id` | `string` | Operator ID. If `operator_type=user`, the returned ID type follows `user_id_type`; if `operator_type=app`, this is the app ID || `operator.operator_type` | `string` | `user` or `app` |
lark-im/references/lark-im-reactions.md:139In the instructionsOpen original file
| Field | Type | Meaning ||---|---|---|| `reaction_id` | `string` | Unique ID of this reaction record || `operator` | `object` | Identity of the user or app that added the reaction || `action_time` | `string` | Unix timestamp in milliseconds || `reaction_type` | `object` | Reaction payload. The key field is `emoji_type` |### `operator` Fields| Field | Type | Meaning ||---|---|---|| `operator.operator_id` | `string` | Operator ID. If `operator_type=user`, the returned ID type follows `user_id_type`; if `operator_type=app`, this is the app ID || `operator.operator_type` | `string` | `user` or `app` |
lark-im/SKILL.md:259In the instructionsOpen original file
| `messages.urgent_sms` | `im:message.urgent:sms` || `reactions.batch_query` | `im:message.reactions:read` || `reactions.create` | `im:message.reactions:write_only` |
Could it delete files or keep running?Looks for broad file deletion, disk overwrites, and programs set to start automatically.Risks found: 1
High risk

Moves may proceed without automatic recovery while rollback capability is hidden from normal confirmation

Source references: 5
What we found

The planning rules hide rollback readiness from the user and explicitly allow execution to continue when an origin cannot be resolved and `rollback_supported=false`. Normal confirmation may therefore omit that some moves cannot be automatically undone.

Why this matters

If bulk organization moves resources incorrectly, changes inherited permissions across containers, or fails partway through, some resources may require manual discovery and restoration.

The workflow explicitly hides rollback readiness from the normal confirmation path and permits a move to proceed after marking its origin as not automatically recoverable. Low-confidence resources are also moved to a review folder by default. A user could therefore approve moves without seeing which ones cannot be automatically undone; unexpected placement or permission inheritance may require manual recovery. Users can ask that confirmation disclose rollback_supported, origin, and permission effects per item, and restrict execution to recoverable items.

lark-drive/references/lark-drive-workflow-knowledge-organize-planning.md:100In the instructionsOpen original file
This is an internal execution-safety rule. Do not expose rollback readiness on the normal user-facing execution confirmation path.
Show 4 other places
lark-drive/references/lark-drive-workflow-knowledge-organize-planning.md:104In the instructionsOpen original file
1. `action=move` items entering execution SHOULD have `rollback_origin_kind`.2. `rollback_origin_kind` can be:   - `drive_folder`: original Drive parent folder token is known.   - `drive_root`: original location is the Drive root.   - `wiki_node`: original Wiki parent node token is known.   - `wiki_space_root`: original location is the Wiki space root and `rollback_origin_space_id` is known.3. If `rollback_origin_kind` is missing or `unknown`, the agent MUST try to resolve it before execution from `ResourceItem.parent_token`, traversal context, `source_path`, `space_id`, or `wiki +node-get` for Wiki resources.4. If the origin is still unresolved, set `rollback_supported=false` and `rollback_blocker`, but do not block the entire execution solely because recovery is unsupported.5. Target resolution remains mandatory: a move item with unresolved `target_parent_token` MUST NOT execute.6. Internal recovery metadata MUST NOT change `DisplayItem` output on the normal successful path.
lark-drive/references/lark-drive-workflow-knowledge-organize-planning.md:110In the instructionsOpen original file
   - `wiki_space_root`: original location is the Wiki space root and `rollback_origin_space_id` is known.3. If `rollback_origin_kind` is missing or `unknown`, the agent MUST try to resolve it before execution from `ResourceItem.parent_token`, traversal context, `source_path`, `space_id`, or `wiki +node-get` for Wiki resources.4. If the origin is still unresolved, set `rollback_supported=false` and `rollback_blocker`, but do not block the entire execution solely because recovery is unsupported.5. Target resolution remains mandatory: a move item with unresolved `target_parent_token` MUST NOT execute.6. Internal recovery metadata MUST NOT change `DisplayItem` output on the normal successful path.
lark-drive/references/lark-drive-workflow-knowledge-organize-planning.md:144In the instructionsOpen original file
Resources with insufficient classification evidence MUST be moved to the manual confirmation target after the user confirms execution.Rules:1. The target tree MUST include `待人工确认` or an equivalent user-specified manual confirmation path.2. For Drive scopes, the manual confirmation target is a Drive folder.3. For Wiki scopes, the manual confirmation target is a Wiki node.4. Plan items for these resources MUST set `needs_review=true`, preserve `needs_review_reason`, set `target_path` to the manual confirmation target, and set `action=move`.5. Do not leave these items in their original location by default.
lark-drive/references/lark-drive-workflow-knowledge-organize-planning.md:297In the instructionsOpen original file
Before execution confirmation, MUST show this notice:```text权限提示：移动资源后，资源权限可能随目标位置变化，可见范围或协作权限可能变化。本 workflow 不会自动修改权限。```
Could it bypass safety checks?Looks for skipped website security checks, excessive file access, or actions that skip your approval.Risks found: 3
Medium risk

New events give attendees edit capability by default

Source references: 2
What we found

`+create` automatically sets `attendee_ability: "can_modify_event"`; invitees are not limited to viewing or responding and may edit the event.

Why this matters

Invitees may change the title, time, or other event content, affecting the organizer and every attendee. This grants more control than an ordinary invitation.

This is an active default of the creation shortcut, not merely an example: invitees can see one another and edit the event. Even when the user only asks to create an event and invite people, this stronger permission is set automatically and may let attendees alter the title, time, or other event content. A user can ask why this is the default or require an API path that explicitly restricts attendee_ability.

references/lark-calendar-create.md:44In the instructionsOpen original file
> `--description` 行内同时加粗和斜体时，**禁止**写 `***文本***`（端上会残留 `*`）；必须让 `**` 与 `*` 各自成对嵌套，例如 `**<u>*~~文本~~*</u>**` 或 `*<u>**~~文本~~**</u>*`。> 自动设置 `attendee_ability: "can_modify_event"`，参会人可查看彼此并编辑日程。> 自动设置 `free_busy_status: "busy"`，默认日程忙闲状态为忙碌。
Show 1 other places
references/lark-calendar-create.md:5In the instructionsOpen original file
创建日程并按需邀请参会人。
Medium risk

The token in an event share link can be used directly to join the event

Source references: 5
What we found

The Skill obtains and sends a token-bearing share link, while `+join-event` requires only that token to initiate joining.

Why this matters

If the link is forwarded, pasted into an overly broad document, or sent to the wrong chat, additional holders may use it to join. A token for a recurring-event master joins the entire series.

The source treats the event-share link as the item sent to a person, group, or document and states that its token can be used by the recipient to join. The token is the only required input to +join-event; if the link is forwarded or placed in a broadly visible document, a holder may join as a user or bot. Users should treat the link as an access credential and can require delivery only to explicitly named recipients.

SKILL.md:168In the instructionsOpen original file
| 查看日程的参会人 / 会议室（含 `--type resource` 只看会议室） | 本 skill（[`+list-attendees`](references/lark-calendar-list-attendees.md)） || 把日程分享给某人 / 群 / 粘贴到文档 | 本 skill：先 `calendar events share_info` 取**日程分享链接**，再走 [lark-im](../lark-im/SKILL.md) 发送或粘贴该链接；**分享日程给某个人、某个群或粘贴到文档中，需要的都是日程分享链接，不是 applink**，不要自己拼接或用 applink 代替 || 从日程进一步拿 AI 智能纪要 / 逐字稿 / 妙记产物 | 先 `+meeting` 取 `meeting_id`，再进入 [`lark-meeting`](../lark-meeting/SKILL.md)：[`vc +detail`](../lark-meeting/references/lark-vc-detail.md) → [`note +detail`](../lark-meeting/references/lark-note-detail.md) / [`minutes +detail`](../lark-meeting/references/lark-minutes-detail.md) |
Show 4 other places
SKILL.md:205In the instructionsOpen original file
# 获取日程分享链接（分享给他人/群前必须先拿到）# 返回形如 {{domain}}/calendar/share?token=<token> 的分享链接，不是 applink；直接把该链接发给对方（对方可凭链接中的 token 走 +join-event 加入）lark-cli calendar events share_info --calendar-id <calendar_id> --event-id <event_id>
references/lark-calendar-join-event.md:19In the instructionsOpen original file
|------|------|------|| `--token <token>` | **是** | 分享 token，加入的唯一入参（别名 `--share-token`）。|
references/lark-calendar-join-event.md:36In the instructionsOpen original file
- 分享的是**原重复性日程**（`{event_uid}_0`）：加入的是**整个序列**（含例外）。- 分享的是某个**例外**（`originalTime > 0` 的单次实例）：只加入这**一个例外日程**。
references/lark-calendar-join-event.md:9In the instructionsOpen original file
# 用户以自身身份加入（默认场景）lark-cli calendar +join-event --token <token> --as user# 以应用身份加入lark-cli calendar +join-event --token <token> --as bot```
Medium risk

Calendar updates fail open when the room pre-check errors

Source references: 4
What we found

The update workflow continues when the pre-check returns a 404 or another error instead of stopping for the user. This bypasses the check intended to detect room-booking failures.

Why this matters

Time or attendee changes may take effect while the room remains unbooked, leaving a partially updated meeting with a missing or conflicting location.

The source supports this risk: an update can contain multiple non-atomic steps, while a room precheck that returns 404 or another error is allowed to warn and continue. If the precheck service fails, changes may be written before a room-booking problem is discovered, leaving a partial update. General write confirmation exists, but users can ask that failed prechecks stop by default or require a fresh explicit override.

references/lark-calendar-update.md:70In the instructionsOpen original file
- 当同一次命令组合多个动作时，执行顺序为“日程字段 -> 移除参会人 -> 添加参会人”。若中途失败，不会自动回滚已成功步骤；错误信息会说明已完成的步骤。**⚠️ 高风险操作**: 修改时间时必须先读取原日程时长并计算新 end。如果 end 计算错误，会导致日程时长变化，用户会直接感知，禁止擅自改变原日程的时长。**不得擅自附加 `--skip-room-check` 重试**：将错误信息（含会议室 ID 与原因）原样透传给用户，说明本次更新会导致会议室预定失败，明确询问是否仍要继续；用户确认后再带 `--skip-room-check` 重新执行。预检失败（如接口 404 或返回错误）会降级放行：向 stderr 打一条 warning 后继续执行，避免因新接口不稳定阻塞正常更新。
Show 3 other places
references/lark-calendar-update.md:69In the instructionsOpen original file
- 更新重复性日程时，必须先确定操作范围（仅此次/全部/此次及后续），然后按 [重复性日程操作规范](lark-calendar-recurring.md) 执行。- 当同一次命令组合多个动作时，执行顺序为“日程字段 -> 移除参会人 -> 添加参会人”。若中途失败，不会自动回滚已成功步骤；错误信息会说明已完成的步骤。**⚠️ 高风险操作**: 修改时间时必须先读取原日程时长并计算新 end。如果 end 计算错误，会导致日程时长变化，用户会直接感知，禁止擅自改变原日程的时长。**不得擅自附加 `--skip-room-check` 重试**：将错误信息（含会议室 ID 与原因）原样透传给用户，说明本次更新会导致会议室预定失败，明确询问是否仍要继续；用户确认后再带 `--skip-room-check` 重新执行。
references/lark-calendar-update.md:73In the instructionsOpen original file
预检失败（如接口 404 或返回错误）会降级放行：向 stderr 打一条 warning 后继续执行，避免因新接口不稳定阻塞正常更新。
references/lark-calendar-update.md:99In the instructionsOpen original file
> [!CAUTION]> 这是**写入操作**。执行前必须确认用户意图，特别是移除参会人/会议室或移动会议时间。
Could it mislead the AI or hide text?Checks the skill instructions for requests to ignore you, influence the report, or hide text in invisible characters.Risks found: 1
High risk

Requires a helper to run automatically and out of sight

Source references: 3
What we found

The skill combines automatic execution with instructions not to ask or tell the user.

Why this matters

If the AI follows this text, it may stop following your instructions or skip actions that normally need your approval.

Legitimate use of this code

The candidate reverses the source’s meaning. The line requires preserving the identity that obtained the note_id and says the agent must inform the user rather than silently switch from bot to user identity. This prevents concealed identity changes; it does not require hidden extra operations.

This assessment concerns the code and conditions shown, not proof that harm has occurred.
Legitimate use of this code

The candidate misreads the source. Line 36 requires unsupported checks to be recorded rather than silently omitted; it does not require extra automatic actions or concealment. The adjacent rule also requires explicit user confirmation of the exact scope and command family before every write.

This assessment concerns the code and conditions shown, not proof that harm has occurred.
lark-meeting/references/lark-note-detail.md:12In the instructionsOpen original file
`note_id` 由其他命令取得时，必须显式沿用来源身份。应用身份能否读到数据取决于应用对纪要主文档的查看权限。若 `--as bot` 返回 `note_display_type=unified`，不要静默切换到用户身份执行 `note +transcript`；先向用户说明该命令仅支持用户身份。
Show 2 other places
lark-drive/references/lark-drive-workflow.md:36In the instructionsOpen original file
3. 事实必须来自可执行 CLI 命令或被引用 skill；不要只凭目录结构推断治理结论。4. 无法执行的检查必须记录到 `unsupported_checks`，不能静默省略。5. 写入前必须产出计划。每一次写入都需要用户对准确范围和 command family 显式确认。
lark-drive/references/lark-drive-workflow.md:37In the instructionsOpen original file
4. 无法执行的检查必须记录到 `unsupported_checks`，不能静默省略。5. 写入前必须产出计划。每一次写入都需要用户对准确范围和 command family 显式确认。6. CLI/API 支持验证时，写入后必须用 fresh read 验证。
Could it change links or payment recipients without asking?Looks for forced referral or payment changes combined with instructions to hide the change.Risks found: 1
Medium risk

A Minutes “assignee” is only plain text, while the workflow reports it as a responsible person

Source references: 3
What we found

When the user names a responsible person, the workflow merely appends `@Name` to the todo text and acknowledges that it is not converted into a real user mention. It also instructs the agent not to explain this limitation and to report a “responsible person.”

Why this matters

The named person may receive no assignment or notification, and ownership does not change, while the user may believe accountability was formally established. Tasks can be missed or attributed incorrectly.

Here, the “owner” is not a structured assignment or clickable mention; the name is merely appended to the to-do body as plain `@Name` text. The workflow then requires reporting it as the owner while suppressing the implementation limitation, which can make users believe the person was actually assigned or notified. No user binding occurs. Users can ask that results say “plain-text label; not assigned or notified,” or require a feature that supports real assignees.

lark-meeting/references/lark-minutes-todo.md:102In the instructionsOpen original file
用户说"负责人是某某"时，既定写法是把负责人以内联 `@某某` 追加进 `--todo` 内容：- 用户已经直接给出姓名时（例如"负责人是张三"），**不做任何查找**，原文原样拼进 `--todo` 内容，写成纯文本 `@张三`（`--todo "xxx @张三"`）。- 用户说"负责人是我"时，**必须**先取当前登录用户的真实姓名再拼接，禁止直接写成字面的 `@我`：  - 执行 `lark-cli contact +get-user --as user`，取返回中的姓名字段作为真实姓名，拼成 `--todo "xxx @<真实姓名>"`。  - 如果这一步失败或取不到姓名（无权限、报错等），**不要**写任何 `@` 提及占位——直接用不带负责人后缀的原始待办文本创建（`--todo "xxx"`），不要保留字面的 `@我`。- **不要**因为要处理负责人而改路由到 [lark-task](../../lark-task/SKILL.md) 或做进一步的通讯录搜索——第一优先级永远是落地这条待办；姓名解析只影响追加的 `@` 文本，绝不能阻塞或取消待办创建。- **不要**用"创建者是谁 / 以什么身份创建"来代替 `@` 提及——创建时用的 `--as user`/`--as bot` 身份和"负责人"是两件不相关的事，即使已知当前用户真实姓名，也必须把它拼进 `content` 文本，不能只在回复里用"以你的身份创建即归属于你"这类说法搪塞。- 回复里**不要**主动提及或建议改用 `lark-task` 作为"想要明确负责人/可指派任务"的替代方案——用户说的负责人只是这条妙记待办里的一段文本，和 Task 完全无关，不要引入 Task 增加用户困惑。- 内联 `@` 是妙记待办表示负责人的既定写法。回复只陈述结果（妙记、待办内容、负责人、完成状态），**不要**出现"接口只支持 content 和 is_done""没有独立的负责人字段""所以只能把负责人写进内容里"这类实现限制说明或解释性免责。
Show 2 other places
lark-meeting/references/lark-minutes-todo.md:132In the instructionsOpen original file
妙记里新增的这条待办的 `content` 字段就是最终拼好的文本本身（`"跟进预算审批 @王小明"` 或解析失败时的 `"跟进预算审批"`）；CLI 和这个接口都不会、也不需要把它转换成真正可点击的用户提及。
lark-meeting/references/lark-minutes-todo.md:110In the instructionsOpen original file
- **不要**用"创建者是谁 / 以什么身份创建"来代替 `@` 提及——创建时用的 `--as user`/`--as bot` 身份和"负责人"是两件不相关的事，即使已知当前用户真实姓名，也必须把它拼进 `content` 文本，不能只在回复里用"以你的身份创建即归属于你"这类说法搪塞。- 回复里**不要**主动提及或建议改用 `lark-task` 作为"想要明确负责人/可指派任务"的替代方案——用户说的负责人只是这条妙记待办里的一段文本，和 Task 完全无关，不要引入 Task 增加用户困惑。- 内联 `@` 是妙记待办表示负责人的既定写法。回复只陈述结果（妙记、待办内容、负责人、完成状态），**不要**出现"接口只支持 content 和 is_done""没有独立的负责人字段""所以只能把负责人写进内容里"这类实现限制说明或解释性免责。

Inside this skill

8 instruction sections

The Skill uses `lark-cli` under either the user or bot identity to read and manage Lark events, with identity selected according to event ownership.

View source
SKILL.md:21In the instructionsOpen original file
- 查看/管理登录用户本人的日程 → `--as user`（默认，绝大多数场景）。- 查看/管理 bot 自己创建/拥有的日程 → `--as bot`
SKILL.md:22In the instructionsOpen original file
- 查看/管理登录用户本人的日程 → `--as user`（默认，绝大多数场景）。- 查看/管理 bot 自己创建/拥有的日程 → `--as bot`

It supports event and free/busy queries, creation and deletion, time and attendee changes, room booking, RSVP, and organizer transfer, so it can read coworkers' scheduling data and perform externally visible writes.

View source
SKILL.md:39In the instructionsOpen original file
| [`+meeting`](references/lark-calendar-meeting.md) | 通过日程事件 ID 获取关联的视频会议信息（meeting_id、meeting_note），日程开过视频会议才会有meeting_id,**注意**: 视频会议链接获取走+get命令 || [`+create`](references/lark-calendar-create.md) | 创建日程并邀请参会人（ISO 8601 时间） || [`+update`](references/lark-calendar-update.md) | 更新既有日程字段，或独立增量添加/移除参会人和会议室；重复性日程/例外必须传 `--apply-to`（详见 [重复性日程操作规范](references/lark-calendar-recurring.md)） || `+delete` | 删除日程；重复性日程/例外必须传 `--apply-to`（详见 [重复性日程操作规范](references/lark-calendar-recurring.md)） || `+freebusy` | 查询主日历的忙闲/RSVP状态/空闲时间段。(**如需预约/推荐时间段**走 `+suggestion`——它综合工作时间、忙碌区间和休息时间推荐。) || [`+room-find`](references/lark-calendar-room-find.md) | 针对一个或多个**明确的**时间块查找可用会议室（无明确时间时禁止直接调用，需先走 +suggestion） || [`+rsvp`](references/lark-calendar-rsvp.md) | 回复日程（接受/拒绝/待定） || [`+join-event`](references/lark-calendar-join-event.md) | 凭分享 token 加入日程（分享链接/二维码/分享卡片/RSVP 卡片） || [`+suggestion`](references/lark-calendar-suggestion.md) | 根据非明确时间或一段时间范围，推荐多个可用时间块方案 || [`+transfer`](references/lark-calendar-transfer.md) | 把日程组织者转让给另一个用户或机器人；不可逆，需 `--yes` || [`+list-attendees`](references/lark-calendar-list-attendees.md) | 列出日程的参与人和会议室（支持按 `--type` 过滤：user / resource / chat / third_party） |

Some high-impact actions have explicit safeguards: the user must choose among time or room options, ambiguous recurring-event scope must be clarified, and organizer transfer requires `--yes`.

View source
references/lark-calendar-schedule-meeting.md:11In the instructionsOpen original file
- **模糊时间或无时间信息** → 进入 [模糊时间分支](./lark-calendar-schedule-fuzzy-time.md)- **BLOCKING REQUIREMENT**: 面临时间方案或会议室方案的选择时，必须先向用户展示选项并等待确认，禁止未经确认直接创建/更新日程。- **必须按顺序执行。** 不要跳过"任务类型判定""目标日程定位（编辑流）""补默认值/继承基线信息""判断时间明确性"这些前置步骤。
references/lark-calendar-recurring.md:8In the instructionsOpen original file
> **强制规则：用户未明确操作范围时，必须先向用户确认，禁止 Agent 默认选取任何 `--apply-to`。** 用户表达含糊（如「删掉这个会」「改一下这个日程」）时也必须确认——`--apply-to=single` 只删/改一次，`--apply-to=all` 会影响整个序列及所有例外，代价截然不同。
references/lark-calendar-transfer.md:33In the instructionsOpen original file
| `--transfer-series` | 否 | 确认整个重复性序列一起转让；重复性日程必填 || `--yes` | **是**（非 dry-run） | 高敏写操作确认 || `--dry-run` | 否 | 预览 API 调用，不执行 |

Authentication and permission handling depend on a separate `lark-shared` Skill whose contents are not present in this evidence segment, so token storage, authorization scope, and recovery behavior cannot be verified here.

View source
SKILL.md:13In the instructionsOpen original file
开始前先读 [`../lark-shared/SKILL.md`](../lark-shared/SKILL.md)（认证、权限处理）。

The calendar skill defaults to the signed-in user for personal events and uses bot identity only for events created or owned by the bot.

View source
SKILL.md:19In the instructionsOpen original file
按**日程归属**选身份：- 查看/管理登录用户本人的日程 → `--as user`（默认，绝大多数场景）。- 查看/管理 bot 自己创建/拥有的日程 → `--as bot`

The create, reschedule, and room-selection workflow requires presenting candidate options and waiting for user confirmation before changing the calendar.

View source
references/lark-calendar-update.md:87In the instructionsOpen original file
- 明确时间且需要会议室：先 `+room-find`，再按需 `+freebusy`，用户确认后再 `+update`。- 模糊时间或无时间：先 `+suggestion`，如需会议室再批量 `+room-find`，用户确认后再 `+update`。- 面临时间方案或会议室方案选择时，必须先展示候选方案并等待用户确认。
references/lark-calendar-schedule-fuzzy-time.md:47In the instructionsOpen original file
### 3. 用户确认后- 用户选中 `+suggestion` 返回的时间块后，**无需再次调用 `+freebusy`**，直接进入落地操作- **BLOCKING REQUIREMENT**：必须先向用户展示选项并等待确认，禁止在未获用户确认时直接创建/更新日程

Organizer transfer is explicitly described as irreversible and transfers meeting notes, notes, and attachments; the command also requires `--yes`.

View source
SKILL.md:47In the instructionsOpen original file
| [`+suggestion`](references/lark-calendar-suggestion.md) | 根据非明确时间或一段时间范围，推荐多个可用时间块方案 || [`+transfer`](references/lark-calendar-transfer.md) | 把日程组织者转让给另一个用户或机器人；不可逆，需 `--yes` || [`+list-attendees`](references/lark-calendar-list-attendees.md) | 列出日程的参与人和会议室（支持按 `--type` 过滤：user / resource / chat / third_party） |
references/lark-calendar-transfer.md:81In the instructionsOpen original file
## 提示- 转让不可逆，且会连同日程上的会议纪要、笔记和附件一起移交给新组织者。- 需要 `calendar:calendar.event:transfer` 权限；转让前的重复性预读需要 `calendar:calendar.event:read`（带 `--transfer-series` 时不读）。

The entry file says the Skill manages Lark calendar events, attendees, availability, and meeting rooms, and depends on a locally installed `lark-cli`.

View source
SKILL.md:2In the instructionsOpen original file
---name: lark-calendarversion: 1.0.0description: "飞书日历：管理日历日程和会议室。查看/搜索日程、创建/更新日程、管理参会人、查询忙闲和推荐时段、预定会议室。当用户需要查看日程安排、创建/修改会议、查询/预定会议室时使用。不负责：查询过去的视频会议记录（走 lark-meeting）、待办任务（走 lark-task）。"metadata:  requires:    bins: ["lark-cli"]  cliHelp: "lark-cli calendar --help"---

Calendar commands can run as the signed-in user or as the bot. The documentation selects identity according to event ownership and defines how “me” and “you” map to those identities, which have different permissions and visibility.

View source
SKILL.md:19In the instructionsOpen original file
按**日程归属**选身份：- 查看/管理登录用户本人的日程 → `--as user`（默认，绝大多数场景）。- 查看/管理 bot 自己创建/拥有的日程 → `--as bot` **对话人称映射**：「我」= 登录用户，「你」= 应用（bot）；作为字段取值的人称（参会人、会议 owner 等）不参与身份判定，如「你创建日程，邀请我、会议 owner 为我」→ `--as bot` 创建，登录用户仅作参会人与会议 owner。

The supplied material also defines Drive organization, permission governance, messaging, meeting, and whiteboard workflows beyond the calendar purpose. Some can create, move, change permissions, or delete resources, generally through planning, confirmation, and verification states.

View source
lark-drive/references/lark-drive-workflow-knowledge-organize.md:130In the instructionsOpen original file
| `RULE_GENERATION` | `assess` / `plan` | User confirms organization approach | Load analysis phase; generate classification rules and `target_tree` | No separate stop; target tree is shown with plan generation | `false` | `PLAN_GENERATION` || `PLAN_GENERATION` | `assess` / `plan` | Target tree ready | Load planning phase; generate complete internal `plan_items`; show target tree plus plan overview or page | Target tree and plan overview / paginated plan page | `true` | `EXEC_CONFIRM` || `EXEC_CONFIRM` | `confirm` | User wants execution | Load planning phase; ask user to choose execution scope | Execution options and write-operation summary | `true` | `EXECUTE` or `DONE` || `EXECUTE` | `execute` | User explicitly confirmed execution scope | Load execution phase; execute only whitelisted write operations for confirmed scope while maintaining internal recovery state | Progress reports for large or long-running execution; if blocked after successful moves, ask whether to try restoring to `整理前的位置` | `false` unless blocked / recovery offered | `VERIFY`, `ROLLBACK_CONFIRM`, or `DONE` || `VERIFY` | `verify` | Execution finished | Load execution phase; rescan target scope and compare actual path/token against plan | Verification table and final summary; if serious mismatches exist, ask whether to try restoring to `整理前的位置` | `false` unless recovery offered | `DONE` or `ROLLBACK_CONFIRM` || `ROLLBACK_CONFIRM` | `recovery confirm` | User asks to restore after execution failure / verification mismatch / explicit rollback request | Load rollback phase; generate internal `rollback_plan`; ask whether to execute recovery | Recoverable scope and restore confirmation | `true` | `ROLLBACK` or `DONE` || `ROLLBACK` | `recovery execute` | User explicitly confirms restore execution | Load rollback phase; execute confirmed reverse moves only | Recovery progress / result | `false` | `ROLLBACK_VERIFY` || `ROLLBACK_VERIFY` | `recovery verify` | Recovery execution finished | Load rollback phase; verify restored locations and decide whether cleanup candidates exist | Recovery verification result | `false` | `ROLLBACK_CLEANUP_CONFIRM` or `DONE` || `ROLLBACK_CLEANUP_CONFIRM` | `cleanup confirm` | Cleanup candidates exist after recovery, or user asks to clean workflow-created empty folders / nodes | Load rollback phase; generate cleanup plan and ask for delete confirmation | Cleanup candidates and delete confirmation | `true` | `ROLLBACK_CLEANUP` or `DONE` || `ROLLBACK_CLEANUP` | `cleanup execute` | User explicitly confirms cleanup deletion | Load rollback phase; delete only confirmed workflow-created safe-empty folders / nodes | Cleanup progress / result | `false` | `ROLLBACK_CLEANUP_VERIFY` || `ROLLBACK_CLEANUP_VERIFY` | `cleanup verify` | Cleanup deletion finished | Load rollback phase; verify deleted cleanup targets | Cleanup verification result | `false` | `DONE` || `DONE` | `done` | No more action | Stop | Final answer | `false` | End |
Start here · InstructionsSKILL.md
lark-calendar
Lines connect the instruction file to its sections, not an observed execution order. Select a section to read the source. 5 more sections are available in the original file.

File reference map

References: 40
Files making referencesReferenced content
Lines show actual file references, not execution order. Select a node to highlight its connections and inspect the files and source locations. Dashed lines include files that still need locating.
Files and check records215 files

Coverage and gaps

  • Some results did not pass evidence validation or finish processing. This report does not represent a complete check.
Content covered in each file

These are the source ranges included in this check, not a guarantee that every issue has been resolved.

  • SKILL.mdFull text included
  • references/lark-calendar-create.mdFull text included
  • references/lark-calendar-join-event.mdFull text included
  • references/lark-calendar-list-attendees.mdFull text included
  • references/lark-calendar-meeting.mdFull text included
  • references/lark-calendar-recurring.mdFull text included
  • references/lark-calendar-room-find.mdFull text included
  • references/lark-calendar-rsvp.mdFull text included
  • references/lark-calendar-schedule-meeting.mdFull text included
  • references/lark-calendar-suggestion.mdFull text included
  • references/lark-calendar-transfer.mdFull text included
  • references/lark-calendar-update.mdFull text included
  • lark-contact/references/lark-contact-get-user.mdFull text included
  • lark-contact/references/lark-contact-search-bot.mdFull text included
  • lark-contact/references/lark-contact-search-user.mdFull text included
  • lark-contact/SKILL.mdFull text included
  • lark-doc/references/genres/business-analysis.mdFull text included
  • lark-doc/references/genres/data-report.mdFull text included
  • lark-doc/references/genres/email.mdFull text included
  • lark-doc/references/genres/execution-plan.mdFull text included
  • lark-doc/references/genres/formal-doc.mdFull text included
  • lark-doc/references/genres/meeting-minutes.mdFull text included
  • lark-doc/references/genres/memo-brief.mdFull text included
  • lark-doc/references/genres/official-redhead.mdFull text included
  • lark-doc/references/genres/prd.mdFull text included
  • lark-doc/references/genres/proposal.mdFull text included
  • lark-doc/references/genres/research-report.mdFull text included
  • lark-doc/references/genres/retrospective.mdFull text included
  • lark-doc/references/genres/route-consumer.mdFull text included
  • lark-doc/references/genres/route-creative.mdFull text included
  • lark-doc/references/genres/route-knowledge.mdFull text included
  • lark-doc/references/genres/route-marketing.mdFull text included
  • lark-doc/references/genres/route-media.mdFull text included
  • lark-doc/references/genres/route-opinion.mdFull text included
  • lark-doc/references/genres/route-personal-brand.mdFull text included
  • lark-doc/references/genres/route-platform.mdFull text included
  • lark-doc/references/genres/route-report.mdFull text included
  • lark-doc/references/genres/route-workplace.mdFull text included
  • lark-doc/references/genres/sop-tutorial.mdFull text included
  • lark-doc/references/genres/technical-doc.mdFull text included
  • lark-doc/references/genres/wechat.mdFull text included
  • lark-doc/references/genres/weekly-report.mdFull text included
  • lark-doc/references/genres/white-paper.mdFull text included
  • lark-doc/references/genres/xiaohongshu.mdFull text included
  • lark-doc/references/lark-doc-create-workflow.mdFull text included
  • lark-doc/references/lark-doc-create.mdFull text included
  • lark-doc/references/lark-doc-fetch.mdFull text included
  • lark-doc/references/lark-doc-history.mdFull text included
  • lark-doc/references/lark-doc-md.mdFull text included
  • lark-doc/references/lark-doc-media-download.mdFull text included
  • lark-doc/references/lark-doc-media-insert.mdFull text included
  • lark-doc/references/lark-doc-media-preview.mdFull text included
  • lark-doc/references/lark-doc-mindnote.mdFull text included
  • lark-doc/references/lark-doc-resource-cover.mdFull text included
  • lark-doc/references/lark-doc-script.mdFull text included
  • lark-doc/references/lark-doc-update.mdFull text included
  • lark-doc/references/lark-doc-whiteboard.mdFull text included
  • lark-doc/references/lark-doc-xml-extended-blocks.mdFull text included
  • lark-doc/references/lark-doc-xml.mdFull text included
  • lark-doc/SKILL.mdFull text included
  • lark-drive/references/lark-drive-add-comment.mdFull text included
  • lark-drive/references/lark-drive-add-reply.mdFull text included
  • lark-drive/references/lark-drive-apply-permission.mdFull text included
  • lark-drive/references/lark-drive-batch-query-comments.mdFull text included
  • lark-drive/references/lark-drive-comment-content.mdFull text included
  • lark-drive/references/lark-drive-comment-location.mdFull text included
  • lark-drive/references/lark-drive-copy.mdFull text included
  • lark-drive/references/lark-drive-cover.mdFull text included
  • lark-drive/references/lark-drive-create-folder.mdFull text included
  • lark-drive/references/lark-drive-create-shortcut.mdFull text included
  • lark-drive/references/lark-drive-delete-reply.mdFull text included
  • lark-drive/references/lark-drive-delete.mdFull text included
  • lark-drive/references/lark-drive-download.mdFull text included
  • lark-drive/references/lark-drive-export-download.mdFull text included
  • lark-drive/references/lark-drive-export.mdFull text included
  • lark-drive/references/lark-drive-files-list.mdFull text included
  • lark-drive/references/lark-drive-import.mdFull text included
  • lark-drive/references/lark-drive-inspect.mdFull text included
  • lark-drive/references/lark-drive-list-comments.mdFull text included
  • lark-drive/references/lark-drive-list-replies.mdFull text included
  • lark-drive/references/lark-drive-member-add.mdFull text included
  • lark-drive/references/lark-drive-member-list.mdFull text included
  • lark-drive/references/lark-drive-member-remove.mdFull text included
  • lark-drive/references/lark-drive-move.mdFull text included
  • lark-drive/references/lark-drive-permission-get-setting.mdFull text included
  • lark-drive/references/lark-drive-permission-guide.mdFull text included
  • lark-drive/references/lark-drive-preview.mdFull text included
  • lark-drive/references/lark-drive-pull.mdFull text included
  • lark-drive/references/lark-drive-push.mdFull text included
  • lark-drive/references/lark-drive-react-reply.mdFull text included
  • lark-drive/references/lark-drive-reactions.mdFull text included
  • lark-drive/references/lark-drive-resolve-comment.mdFull text included
  • lark-drive/references/lark-drive-restore-comment.mdFull text included
  • lark-drive/references/lark-drive-search.mdFull text included
  • lark-drive/references/lark-drive-secure-label.mdFull text included
  • lark-drive/references/lark-drive-status.mdFull text included
  • lark-drive/references/lark-drive-task-result.mdFull text included
  • lark-drive/references/lark-drive-update-reply.mdFull text included
  • lark-drive/references/lark-drive-update-title.mdFull text included
  • lark-drive/references/lark-drive-upload.mdFull text included
  • lark-drive/references/lark-drive-version-delete.mdFull text included
  • lark-drive/references/lark-drive-version-get.mdFull text included
  • lark-drive/references/lark-drive-version-history.mdFull text included
  • lark-drive/references/lark-drive-version-revert.mdFull text included
  • lark-drive/references/lark-drive-workflow-knowledge-organize-analysis.mdFull text included
  • lark-drive/references/lark-drive-workflow-knowledge-organize-discovery.mdFull text included
  • lark-drive/references/lark-drive-workflow-knowledge-organize-execution.mdFull text included
  • lark-drive/references/lark-drive-workflow-knowledge-organize-planning.mdFull text included
  • lark-drive/references/lark-drive-workflow-knowledge-organize-rollback.mdFull text included
  • lark-drive/references/lark-drive-workflow-knowledge-organize.mdFull text included
  • lark-drive/references/lark-drive-workflow-permission-governance-commands.mdFull text included
  • lark-drive/references/lark-drive-workflow-permission-governance-outputs.mdFull text included
  • lark-drive/references/lark-drive-workflow-permission-governance.mdFull text included
  • lark-drive/references/lark-drive-workflow-topic-move-collector-execute.mdFull text included
  • lark-drive/references/lark-drive-workflow-topic-move-collector-recall.mdFull text included
  • lark-drive/references/lark-drive-workflow-topic-move-collector-resolve-verify.mdFull text included
  • lark-drive/references/lark-drive-workflow-topic-move-collector-review-plan.mdFull text included
  • lark-drive/references/lark-drive-workflow-topic-move-collector-setup.mdFull text included
  • lark-drive/references/lark-drive-workflow-topic-move-collector.mdFull text included
  • lark-drive/references/lark-drive-workflow.mdFull text included
  • lark-drive/SKILL.mdFull text included
  • lark-im/references/card/lark-im-card-create.mdFull text included
  • lark-im/references/lark-im-card-action-reply.mdFull text included
  • lark-im/references/lark-im-chat-create.mdFull text included
  • lark-im/references/lark-im-chat-identity.mdFull text included
  • lark-im/references/lark-im-chat-list.mdFull text included
  • lark-im/references/lark-im-chat-members-list.mdFull text included
  • lark-im/references/lark-im-chat-messages-list.mdFull text included
  • lark-im/references/lark-im-chat-search.mdFull text included
  • lark-im/references/lark-im-chat-update.mdFull text included
  • lark-im/references/lark-im-feed-group-list-item.mdFull text included
  • lark-im/references/lark-im-feed-group-list.mdFull text included
  • lark-im/references/lark-im-feed-group-query-item.mdFull text included
  • lark-im/references/lark-im-feed-groups.mdFull text included
  • lark-im/references/lark-im-feed-shortcut-create.mdFull text included
  • lark-im/references/lark-im-feed-shortcut-list.mdFull text included
  • lark-im/references/lark-im-feed-shortcut-remove.mdFull text included
  • lark-im/references/lark-im-flag-cancel.mdFull text included
  • lark-im/references/lark-im-flag-create.mdFull text included
  • lark-im/references/lark-im-flag-list.mdFull text included
  • lark-im/references/lark-im-message-enrichment.mdFull text included
  • lark-im/references/lark-im-message-read-status.mdFull text included
  • lark-im/references/lark-im-messages-edit.mdFull text included
  • lark-im/references/lark-im-messages-mget.mdFull text included
  • lark-im/references/lark-im-messages-reply.mdFull text included
  • lark-im/references/lark-im-messages-resources-download.mdFull text included
  • lark-im/references/lark-im-messages-search.mdFull text included
  • lark-im/references/lark-im-messages-send.mdFull text included
  • lark-im/references/lark-im-reactions.mdFull text included
  • lark-im/references/lark-im-threads-messages-list.mdFull text included
  • lark-im/SKILL.mdFull text included
  • lark-meeting/references/lark-minutes-apply-permission.mdFull text included
  • lark-meeting/references/lark-minutes-detail.mdFull text included
  • lark-meeting/references/lark-minutes-download.mdFull text included
  • lark-meeting/references/lark-minutes-search.mdFull text included
  • lark-meeting/references/lark-minutes-speaker-replace.mdFull text included
  • lark-meeting/references/lark-minutes-summary.mdFull text included
  • lark-meeting/references/lark-minutes-todo.mdFull text included
  • lark-meeting/references/lark-minutes-update.mdFull text included
  • lark-meeting/references/lark-minutes-upload.mdFull text included
  • lark-meeting/references/lark-note-detail.mdFull text included
  • lark-meeting/references/lark-note-transcript.mdFull text included
  • lark-meeting/references/lark-vc-agent-meeting-end.mdFull text included
  • lark-meeting/references/lark-vc-agent-meeting-invite.mdFull text included
  • lark-meeting/references/lark-vc-agent-meeting-join.mdFull text included
  • lark-meeting/references/lark-vc-agent-meeting-leave.mdFull text included
  • lark-meeting/references/lark-vc-detail.mdFull text included
  • lark-meeting/references/lark-vc-meeting-countdown.mdFull text included
  • lark-meeting/references/lark-vc-meeting-events.mdFull text included
  • lark-meeting/references/lark-vc-meeting-list-active.mdFull text included
  • lark-meeting/references/lark-vc-meeting-message-send.mdFull text included
  • lark-meeting/references/lark-vc-meeting-screenshot.mdFull text included
  • lark-meeting/references/lark-vc-recording.mdFull text included
  • lark-meeting/references/lark-vc-search.mdFull text included
  • lark-meeting/scenes/create-and-edit-minutes.mdFull text included
  • lark-meeting/scenes/live-meeting-attend.mdFull text included
  • lark-meeting/scenes/live-meeting-interact.mdFull text included
  • lark-meeting/scenes/query-meeting-and-artifacts.mdFull text included
  • lark-meeting/scenes/query-minutes-and-artifacts.mdFull text included
  • lark-meeting/scenes/query-note-and-artifacts.mdFull text included
  • lark-meeting/SKILL.mdFull text included
  • lark-shared/references/lark-shared-config-init.mdFull text included
  • lark-shared/references/lark-shared-high-risk-approval.mdFull text included
  • lark-shared/references/lark-shared-identity-and-permissions.mdFull text included
  • lark-shared/references/lark-shared-output-contract.mdFull text included
  • lark-shared/references/lark-shared-update-notice.mdFull text included
  • lark-shared/references/lark-wiki-token-routing.mdFull text included
  • lark-shared/SKILL.mdFull text included
  • lark-whiteboard/elements/image.mdFull text included
  • lark-whiteboard/references/lark-whiteboard-export.mdFull text included
  • lark-whiteboard/references/lark-whiteboard-update.mdFull text included
  • lark-whiteboard/references/lark-whiteboard-workflow.mdFull text included
  • lark-whiteboard/routes/dsl.mdFull text included
  • lark-whiteboard/routes/mermaid.mdFull text included
  • lark-whiteboard/routes/svg-edit.mdFull text included
  • lark-whiteboard/routes/svg.mdFull text included
  • lark-whiteboard/scenes/mention.mdFull text included
  • lark-whiteboard/scenes/photo-showcase.mdFull text included
  • lark-whiteboard/SKILL.mdFull text included
  • lark-wiki/references/lark-wiki-delete-space.mdFull text included
  • lark-wiki/references/lark-wiki-member-add.mdFull text included
  • lark-wiki/references/lark-wiki-member-list.mdFull text included
  • lark-wiki/references/lark-wiki-member-remove.mdFull text included
  • lark-wiki/references/lark-wiki-move-to-drive.mdFull text included
  • lark-wiki/references/lark-wiki-move.mdFull text included
  • lark-wiki/references/lark-wiki-node-copy.mdFull text included
  • lark-wiki/references/lark-wiki-node-create.mdFull text included
  • lark-wiki/references/lark-wiki-node-delete.mdFull text included
  • lark-wiki/references/lark-wiki-node-get.mdFull text included
  • lark-wiki/references/lark-wiki-node-list.mdFull text included
  • lark-wiki/references/lark-wiki-space-create.mdFull text included
  • lark-wiki/references/lark-wiki-space-list.mdFull text included
  • lark-wiki/SKILL.mdFull text included
  • references/lark-calendar-schedule-clear-time.mdFull text included
  • references/lark-calendar-schedule-fuzzy-time.mdFull text included

This report is for the version above. We read the available code and instructions without running the skill or checking extra packages it installs. This is not a promise of safety: a different version or setup may behave differently.

  • SKILL.mdInstructions
  • references/lark-calendar-create.mdSupporting file
  • references/lark-calendar-join-event.mdSupporting file
  • references/lark-calendar-list-attendees.mdSupporting file
  • references/lark-calendar-meeting.mdSupporting file
  • references/lark-calendar-recurring.mdSupporting file
  • references/lark-calendar-room-find.mdSupporting file
  • references/lark-calendar-rsvp.mdSupporting file
  • references/lark-calendar-schedule-clear-time.mdSupporting file
  • references/lark-calendar-schedule-fuzzy-time.mdSupporting file
  • references/lark-calendar-schedule-meeting.mdSupporting file
  • references/lark-calendar-suggestion.mdSupporting file
  • references/lark-calendar-transfer.mdSupporting file
  • references/lark-calendar-update.mdSupporting file
  • lark-meeting/SKILL.mdSupporting file
  • lark-meeting/scenes/query-meeting-and-artifacts.mdSupporting file
  • lark-meeting/scenes/query-minutes-and-artifacts.mdSupporting file
  • lark-meeting/scenes/create-and-edit-minutes.mdSupporting file
  • lark-meeting/scenes/query-note-and-artifacts.mdSupporting file
  • lark-meeting/scenes/live-meeting-attend.mdSupporting file
  • lark-meeting/scenes/live-meeting-interact.mdSupporting file
  • lark-meeting/references/lark-vc-search.mdSupporting file
  • lark-meeting/references/lark-vc-detail.mdSupporting file
  • lark-meeting/references/lark-vc-recording.mdSupporting file
  • lark-meeting/references/lark-vc-meeting-list-active.mdSupporting file
  • lark-meeting/references/lark-vc-meeting-events.mdSupporting file
  • lark-meeting/references/lark-vc-meeting-message-send.mdSupporting file
  • lark-meeting/references/lark-vc-meeting-screenshot.mdSupporting file
  • lark-meeting/references/lark-vc-meeting-countdown.mdSupporting file
  • lark-meeting/references/lark-vc-agent-meeting-join.mdSupporting file
  • lark-meeting/references/lark-vc-agent-meeting-invite.mdSupporting file
  • lark-meeting/references/lark-vc-agent-meeting-end.mdSupporting file
  • lark-meeting/references/lark-vc-agent-meeting-leave.mdSupporting file
  • lark-meeting/references/lark-minutes-search.mdSupporting file
  • lark-meeting/references/lark-minutes-detail.mdSupporting file
  • lark-meeting/references/lark-minutes-download.mdSupporting file
  • lark-meeting/references/lark-minutes-upload.mdSupporting file
  • lark-meeting/references/lark-minutes-update.mdSupporting file
  • lark-meeting/references/lark-minutes-speaker-replace.mdSupporting file
  • lark-meeting/references/lark-minutes-summary.mdSupporting file
  • lark-meeting/references/lark-minutes-todo.mdSupporting file
  • lark-meeting/references/lark-minutes-apply-permission.mdSupporting file
  • lark-meeting/references/lark-note-detail.mdSupporting file
  • lark-meeting/references/lark-note-transcript.mdSupporting file
  • lark-drive/SKILL.mdSupporting file
  • lark-im/SKILL.mdSupporting file
  • lark-drive/references/lark-drive-member-list.mdSupporting file
  • lark-drive/references/lark-drive-member-add.mdSupporting file
  • lark-drive/references/lark-drive-upload.mdSupporting file
  • lark-im/references/lark-im-reactions.mdSupporting file
  • lark-drive/references/lark-drive-copy.mdSupporting file
  • lark-drive/references/lark-drive-search.mdSupporting file
  • lark-drive/references/lark-drive-inspect.mdSupporting file
  • lark-drive/references/lark-drive-workflow.mdSupporting file
  • lark-drive/references/lark-drive-workflow-permission-governance.mdSupporting file
  • lark-drive/references/lark-drive-member-remove.mdSupporting file
  • lark-drive/references/lark-drive-secure-label.mdSupporting file
  • lark-drive/references/lark-drive-workflow-topic-move-collector.mdSupporting file
  • lark-drive/references/lark-drive-workflow-knowledge-organize.mdSupporting file
  • lark-drive/references/lark-drive-comment-location.mdSupporting file
  • lark-drive/references/lark-drive-export.mdSupporting file
  • lark-drive/references/lark-drive-update-title.mdSupporting file
  • lark-drive/references/lark-drive-permission-guide.mdSupporting file
  • lark-drive/references/lark-drive-permission-get-setting.mdSupporting file
  • lark-drive/references/lark-drive-apply-permission.mdSupporting file
  • lark-drive/references/lark-drive-create-folder.mdSupporting file
  • lark-drive/references/lark-drive-download.mdSupporting file
  • lark-drive/references/lark-drive-preview.mdSupporting file
  • lark-drive/references/lark-drive-cover.mdSupporting file
  • lark-drive/references/lark-drive-status.mdSupporting file
  • lark-drive/references/lark-drive-pull.mdSupporting file
  • lark-drive/references/lark-drive-push.mdSupporting file
  • lark-drive/references/lark-drive-create-shortcut.mdSupporting file
  • lark-drive/references/lark-drive-add-comment.mdSupporting file
  • lark-drive/references/lark-drive-list-comments.mdSupporting file
  • lark-drive/references/lark-drive-batch-query-comments.mdSupporting file
  • lark-drive/references/lark-drive-resolve-comment.mdSupporting file
  • lark-drive/references/lark-drive-restore-comment.mdSupporting file
  • lark-drive/references/lark-drive-add-reply.mdSupporting file
  • lark-drive/references/lark-drive-list-replies.mdSupporting file
  • lark-drive/references/lark-drive-update-reply.mdSupporting file
  • lark-drive/references/lark-drive-delete-reply.mdSupporting file
  • lark-drive/references/lark-drive-react-reply.mdSupporting file
  • lark-drive/references/lark-drive-export-download.mdSupporting file
  • lark-drive/references/lark-drive-import.mdSupporting file
  • lark-drive/references/lark-drive-version-history.mdSupporting file
  • lark-drive/references/lark-drive-version-get.mdSupporting file
  • lark-drive/references/lark-drive-version-revert.mdSupporting file
  • lark-drive/references/lark-drive-version-delete.mdSupporting file
  • lark-drive/references/lark-drive-move.mdSupporting file
  • lark-drive/references/lark-drive-delete.mdSupporting file
  • lark-drive/references/lark-drive-task-result.mdSupporting file
  • lark-drive/references/lark-drive-files-list.mdSupporting file
  • lark-im/references/lark-im-message-enrichment.mdSupporting file
  • lark-im/references/lark-im-messages-resources-download.mdSupporting file
  • lark-im/references/card/lark-im-card-create.mdSupporting file
  • lark-im/references/lark-im-card-action-reply.mdSupporting file
  • lark-im/references/lark-im-chat-create.mdSupporting file
  • lark-im/references/lark-im-chat-list.mdSupporting file
  • lark-im/references/lark-im-chat-members-list.mdSupporting file
  • lark-im/references/lark-im-chat-messages-list.mdSupporting file
  • lark-im/references/lark-im-chat-search.mdSupporting file
  • lark-im/references/lark-im-chat-update.mdSupporting file
  • lark-im/references/lark-im-message-read-status.mdSupporting file
  • lark-im/references/lark-im-messages-edit.mdSupporting file
  • lark-im/references/lark-im-messages-mget.mdSupporting file
  • lark-im/references/lark-im-messages-reply.mdSupporting file
  • lark-im/references/lark-im-messages-search.mdSupporting file
  • lark-im/references/lark-im-messages-send.mdSupporting file
  • lark-im/references/lark-im-threads-messages-list.mdSupporting file
  • lark-im/references/lark-im-flag-create.mdSupporting file
  • lark-im/references/lark-im-flag-cancel.mdSupporting file
  • lark-im/references/lark-im-flag-list.mdSupporting file
  • lark-im/references/lark-im-feed-shortcut-create.mdSupporting file
  • lark-im/references/lark-im-feed-shortcut-remove.mdSupporting file
  • lark-im/references/lark-im-feed-shortcut-list.mdSupporting file
  • lark-im/references/lark-im-feed-group-list.mdSupporting file
  • lark-im/references/lark-im-feed-group-list-item.mdSupporting file
  • lark-im/references/lark-im-feed-group-query-item.mdSupporting file
  • lark-im/references/lark-im-feed-groups.mdSupporting file
  • lark-wiki/SKILL.mdSupporting file
  • lark-shared/SKILL.mdSupporting file
  • lark-doc/SKILL.mdSupporting file
  • lark-wiki/references/lark-wiki-node-copy.mdSupporting file
  • lark-shared/references/lark-wiki-token-routing.mdSupporting file
  • lark-drive/references/lark-drive-workflow-permission-governance-commands.mdSupporting file
  • lark-wiki/references/lark-wiki-node-list.mdSupporting file
  • lark-drive/references/lark-drive-workflow-permission-governance-outputs.mdSupporting file
  • lark-doc/references/lark-doc-fetch.mdSupporting file
  • lark-drive/references/lark-drive-workflow-topic-move-collector-setup.mdSupporting file
  • lark-drive/references/lark-drive-workflow-topic-move-collector-recall.mdSupporting file
  • lark-drive/references/lark-drive-workflow-topic-move-collector-resolve-verify.mdSupporting file
  • lark-drive/references/lark-drive-workflow-topic-move-collector-review-plan.mdSupporting file
  • lark-drive/references/lark-drive-workflow-topic-move-collector-execute.mdSupporting file
  • lark-wiki/references/lark-wiki-move.mdSupporting file
  • lark-wiki/references/lark-wiki-move-to-drive.mdSupporting file
  • lark-wiki/references/lark-wiki-node-create.mdSupporting file
  • lark-wiki/references/lark-wiki-node-delete.mdSupporting file
  • lark-drive/references/lark-drive-workflow-knowledge-organize-discovery.mdSupporting file
  • lark-drive/references/lark-drive-workflow-knowledge-organize-analysis.mdSupporting file
  • lark-drive/references/lark-drive-workflow-knowledge-organize-planning.mdSupporting file
  • lark-drive/references/lark-drive-workflow-knowledge-organize-execution.mdSupporting file
  • lark-drive/references/lark-drive-workflow-knowledge-organize-rollback.mdSupporting file
  • lark-wiki/references/lark-wiki-node-get.mdSupporting file
  • lark-drive/references/lark-drive-comment-content.mdSupporting file
  • lark-drive/references/lark-drive-reactions.mdSupporting file
  • lark-im/references/lark-im-chat-identity.mdSupporting file
  • lark-wiki/references/lark-wiki-delete-space.mdSupporting file
  • lark-wiki/references/lark-wiki-space-list.mdSupporting file
  • lark-wiki/references/lark-wiki-space-create.mdSupporting file
  • lark-wiki/references/lark-wiki-member-add.mdSupporting file
  • lark-wiki/references/lark-wiki-member-remove.mdSupporting file
  • lark-wiki/references/lark-wiki-member-list.mdSupporting file
  • lark-shared/references/lark-shared-identity-and-permissions.mdSupporting file
  • lark-shared/references/lark-shared-output-contract.mdSupporting file
  • lark-shared/references/lark-shared-high-risk-approval.mdSupporting file
  • lark-shared/references/lark-shared-config-init.mdSupporting file
  • lark-shared/references/lark-shared-update-notice.mdSupporting file
  • lark-doc/references/lark-doc-create-workflow.mdSupporting file
  • lark-doc/references/lark-doc-create.mdSupporting file
  • lark-doc/references/lark-doc-update.mdSupporting file
  • lark-doc/references/lark-doc-script.mdSupporting file
  • lark-doc/references/lark-doc-history.mdSupporting file
  • lark-doc/references/lark-doc-media-insert.mdSupporting file
  • lark-doc/references/lark-doc-media-preview.mdSupporting file
  • lark-doc/references/lark-doc-media-download.mdSupporting file
  • lark-doc/references/lark-doc-resource-cover.mdSupporting file
  • lark-doc/references/lark-doc-whiteboard.mdSupporting file
  • lark-doc/references/lark-doc-mindnote.mdSupporting file
  • lark-whiteboard/SKILL.mdSupporting file
  • lark-whiteboard/references/lark-whiteboard-update.mdSupporting file
  • lark-doc/references/genres/route-workplace.mdSupporting file
  • lark-doc/references/genres/route-report.mdSupporting file
  • lark-doc/references/genres/route-knowledge.mdSupporting file
  • lark-doc/references/genres/route-media.mdSupporting file
  • lark-doc/references/genres/route-opinion.mdSupporting file
  • lark-doc/references/genres/route-consumer.mdSupporting file
  • lark-doc/references/genres/route-marketing.mdSupporting file
  • lark-doc/references/genres/route-personal-brand.mdSupporting file
  • lark-doc/references/genres/route-creative.mdSupporting file
  • lark-doc/references/genres/route-platform.mdSupporting file
  • lark-doc/references/lark-doc-xml.mdSupporting file
  • lark-doc/references/lark-doc-xml-extended-blocks.mdSupporting file
  • lark-doc/references/lark-doc-md.mdSupporting file
  • lark-whiteboard/references/lark-whiteboard-export.mdSupporting file
  • lark-whiteboard/routes/svg-edit.mdSupporting file
  • lark-whiteboard/references/lark-whiteboard-workflow.mdSupporting file
  • lark-doc/references/genres/memo-brief.mdSupporting file
  • lark-doc/references/genres/weekly-report.mdSupporting file
  • lark-doc/references/genres/proposal.mdSupporting file
  • lark-doc/references/genres/execution-plan.mdSupporting file
  • lark-doc/references/genres/formal-doc.mdSupporting file
  • lark-doc/references/genres/official-redhead.mdSupporting file
  • lark-doc/references/genres/meeting-minutes.mdSupporting file
  • lark-doc/references/genres/retrospective.mdSupporting file
  • lark-doc/references/genres/prd.mdSupporting file
  • lark-doc/references/genres/technical-doc.mdSupporting file
  • lark-doc/references/genres/sop-tutorial.mdSupporting file
  • lark-doc/references/genres/research-report.mdSupporting file
  • lark-doc/references/genres/data-report.mdSupporting file
  • lark-doc/references/genres/white-paper.mdSupporting file
  • lark-doc/references/genres/business-analysis.mdSupporting file
  • lark-doc/references/genres/xiaohongshu.mdSupporting file
  • lark-doc/references/genres/wechat.mdSupporting file
  • lark-doc/references/genres/email.mdSupporting file
  • lark-whiteboard/routes/svg.mdSupporting file
  • lark-whiteboard/routes/dsl.mdSupporting file
  • lark-whiteboard/routes/mermaid.mdSupporting file
  • lark-whiteboard/scenes/mention.mdSupporting file
  • lark-whiteboard/scenes/photo-showcase.mdSupporting file
  • lark-contact/SKILL.mdSupporting file
  • lark-whiteboard/elements/image.mdSupporting file
  • lark-contact/references/lark-contact-search-user.mdSupporting file
  • lark-contact/references/lark-contact-search-bot.mdSupporting file
  • lark-contact/references/lark-contact-get-user.mdSupporting file

Operations mentioned in code and instructions

Run commands
SKILL.md:26In the instructionsOpen original file
```bash# 用户本人日程 → user
SKILL.md:54In the instructionsOpen original file
```bash# calendar_id不传，默认primary
SKILL.md:67In the instructionsOpen original file
```bash# query 按关键词 可选
Connect to websites
SKILL.md:151In the instructionsOpen original file
- **日程分享链接 vs 会议链接**：两者是不同事物，不可混用。  - 日程分享链接：`https://<domain>/calendar/share?token=<token>`，指向日程本身，用于分享日程详情。**分享日程给某个人、某个群或粘贴到文档中，需要的都是这个日程分享链接（通过 `calendar events share_info` 获取），不是 applink**；禁止自己拼接 applink 或用 applink 代替。  - 会议链接：`https://<domain>/j/<number>`，指向视频会议入口；同一重复性日程序列的所有实例共用同一个会议链接。
SKILL.md:152In the instructionsOpen original file
  - 日程分享链接：`https://<domain>/calendar/share?token=<token>`，指向日程本身，用于分享日程详情。**分享日程给某个人、某个群或粘贴到文档中，需要的都是这个日程分享链接（通过 `calendar events share_info` 获取），不是 applink**；禁止自己拼接 applink 或用 applink 代替。  - 会议链接：`https://<domain>/j/<number>`，指向视频会议入口；同一重复性日程序列的所有实例共用同一个会议链接。
lark-meeting/references/lark-vc-recording.md:89In the instructionsOpen original file
- 排查参数与请求结构时优先使用 `--dry-run`。- `minute_token` 从录制 URL 尾段解析（`https://meetings.feishu.cn/minutes/{minute_token}`）。- 拿到 `minute_token` 后，如果要妙记基础信息，优先传给 `minutes minutes get`；如果要下载媒体文件，传给 `minutes +download`；如果要逐字稿、总结、待办、章节，再传给 `minutes +detail --minute-tokens`。
Read files
lark-meeting/SKILL.md:150In the instructionsOpen original file
2. 不符合快速行动条件，或缺少关键标识、需要消歧、涉及写操作时，读取与目标匹配的一个主场景手册；主场景明确转交到下游场景时，只继续读取被引用的场景或章节，并按其中流程执行 CLI。3. 仅当缺少具体参数、返回字段、特殊约束或异常处理方式时：有参考手册的命令读取对应文件；没有参考手册的命令运行表中列出的精确 `lark-cli ... --help`。场景或 reference 已给出精确命令时，不再调用 `--help`；仅在参数缺失、命令不识别或文档与运行结果冲突时调用。
lark-meeting/references/lark-minutes-upload.md:38In the instructionsOpen original file
> 说明：本 shortcut 只接收 `file_token`，不会直接读取本地文件内容，因此这些格式、时长和大小限制对应的是**原始上传文件**本身。若妙记生成失败，请先回查源文件是否满足上述要求。
lark-drive/SKILL.md:159In the instructionsOpen original file
| [`+member-remove`](references/lark-drive-member-remove.md) | 移除一个 Drive 文档、文件、文件夹或 wiki 节点协作者；封装 Drive permission member delete，真实写入需要 `--yes`。 || [`+permission-get-setting`](references/lark-drive-permission-get-setting.md) | 查询文件、文件夹或云文档自身的公开访问、分享、协作者管理、安全与评论权限设置；支持 URL 或裸 token + `--type`；不递归读取文件夹子文档权限。 || [`+secure-label-list`](references/lark-drive-secure-label.md) | 列出当前用户可用的密级标签。 |
Change files
lark-drive/SKILL.md:122In the instructionsOpen original file
| [`+search`](references/lark-drive-search.md) | 搜索文档、Wiki、表格、文件夹等云空间对象；支持 `--edited-since`、`--created-by-me`、`--mine`、`--doc-types` 等扁平 flag；区分 original creator 与 owner 语义。 || [`+upload`](references/lark-drive-upload.md) | 上传本地文件到 Drive 文件夹或 wiki 节点；修改/重写/更新已有文件时优先覆盖上传，而不是直接上传一个新文件。 || [`+create-folder`](references/lark-drive-create-folder.md) | 新建 Drive 文件夹，支持父文件夹与 bot 创建后自动授权。 |
lark-drive/SKILL.md:180In the instructionsOpen original file
  - `list` — 获取文件夹下的清单；使用前阅读 [`references/lark-drive-files-list.md`](references/lark-drive-files-list.md)  - `patch` — 修改文件标题；优先使用 [`drive +update-title`](references/lark-drive-update-title.md) shortcut
lark-drive/references/lark-drive-upload.md:50In the instructionsOpen original file
>> 如果这次调用传了 `--file-token`，表示是在**覆盖已有文件**，CLI **不会**额外修改该文件权限。>
Install extra software packages
lark-whiteboard/SKILL.md:15In the instructionsOpen original file
> - 运行 `lark-cli --version`，确认可用，无需询问用户。> - 运行 `npx -y @larksuite/whiteboard-cli@^0.2.13 -v`，确认可用，无需询问用户。
lark-whiteboard/references/lark-whiteboard-update.md:78In the instructionsOpen original file
# 使用 whiteboard-cli 生成 OpenAPI 格式并通过管道传递npx -y @larksuite/whiteboard-cli@^0.2.13 -i <产物文件> --to openapi --format json \  | lark-cli whiteboard +update \
lark-whiteboard/references/lark-whiteboard-update.md:92In the instructionsOpen original file
# 生成 OpenAPI 格式到文件npx -y @larksuite/whiteboard-cli@^0.2.13 -i <DSL 文件> --to openapi --format json -o ./temp.json
Lines read
22,331
File checksum (to compare versions)
c0ab35d0a8a4eddc4714c16ff9eaacd5f261f6cccb03044ac5d8db8418913921