Skip to content
Report library
Purpose / Documents

Lark Doc Skill Security Audit

What the author says it does (original text)

飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。

Independent security check

Do not install or run it yet

Files checked
44
Risks found
4
Could it run dangerous commands?Looks for programs run straight after downloading, remote control of your computer, and hidden commands.No risks found
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: 3
Medium risk

A clipboard image can be read directly and uploaded into a Lark document or cover

Source references: 4
What we found

When the user mentions a screenshot, a recently copied image, or the clipboard, the workflow directs use of --from-clipboard, which reads the system clipboard and uploads the image. The clipboard may have been replaced by another copy operation, and no preview-before-upload step is specified.

Why this matters

The wrong or sensitive clipboard image could be placed in a shared document or used as its cover, exposing screen content, personal data, token screenshots, or internal material.

The source directs the agent to read and upload clipboard image data when the user explicitly refers to a screenshot, recently copied content, or the clipboard. It is an in-memory upload without an intermediate file to inspect, so a replaced clipboard could put the wrong image into the document. This is not silent or arbitrary collection: the source requires an explicit source choice and confirmation before writing. A user can require preview/confirmation of the current clipboard, recopy the image, and name the target document.

references/lark-doc-media-insert.md:10In the instructions
> **最高优先级:用户明确指定了来源,就严格按用户的来。** 下面的启发式只在用户没表态时生效。>> - 用户说"把这张截图插进去"、"用剪切板里的图"、"我刚复制的" → 无条件走 `--from-clipboard`。> - 用户说"用 `~/Downloads/foo.png`"、"插本地这个文件"、给了具体路径 → 无条件走 `--file`。> - 用户两者都没说清 → 按下表的启发式推断。>> 即使推断看起来更"优"(比如用户说了路径但你觉得走剪切板更省事),也**不要自作主张**换来源。要换,先问。
Show 3 other places
references/lark-doc-media-insert.md:26In the instructions
`--from-clipboard` 走进程内存直传,不产生临时文件;macOS / Windows 内置支持,Linux 需要 `xclip` 或 `wl-paste` 或 `xsel` 任一。
references/lark-doc-resource-cover.md:20In the instructions
# 使用本地文件更新封面图。lark-cli docs +resource-update --doc doxcnXXX --type cover --file ./cover.png# 使用剪切板图片更新封面图。lark-cli docs +resource-update --doc doxcnXXX --type cover --from-clipboard
references/lark-doc-media-insert.md:108In the instructions
> [!CAUTION]> 这是**写入操作**(会修改文档内容)—— 执行前必须确认用户意图。
Medium risk

The complex-whiteboard workflow passes document tokens and source content to an additional SubAgent

Source references: 4
What we found

For complex diagrams or updates to an existing whiteboard, the instructions require a SubAgent and provide it with the board token and relevant source paragraphs or data; the SVG insertion path also calls for a document token. This expands where sensitive identifiers and document excerpts are processed.

Why this matters

If the document contains internal strategy, personal information, or unpublished data, an additional agent context, log, or provider boundary may receive it. A leaked token may also assist resource access, depending on backend authorization checks.

The source explicitly delegates complex diagrams or existing-board updates to a SubAgent and supplies the board token, audience, and relevant source passages or data; SVG insertion also includes the document token. Sensitive identifiers or text therefore reach an additional processor. The evidence does not establish that the SubAgent is an external service or that disclosure occurs, and simple diagrams may stay with the main agent. A user can prohibit delegation, provide only a redacted minimum excerpt, or ask how SubAgent data is isolated and retained.

references/lark-doc-whiteboard.md:45In the instructions
### 步骤 2B: SubAgent 使用 SVG 插入图表主 Agent 启动 SubAgent,让它用 `docs +create` / `docs +update` 插入:```xml<whiteboard type="svg">    <svg...>...    </svg></whiteboard>```如果 SVG 已在本地文件中,可写成 `<whiteboard type="svg" path="@./diagram.svg"></whiteboard>`;PlantUML 文件同理使用 `<whiteboard type="plantuml" path="@./sequence.puml"></whiteboard>`。Sub Agent 需要携带以下的最小上下文,以及后续的 [SVG 设计 Workflow] 章节指南:- doc token、插入位置(标题 / block_id / command)- 图表目标、受众、源段落或数据- 要求读取 `lark-doc-xml.md`;不需要读取 `lark-whiteboard`- SVG 必须完整自包含:包含 `<svg>` 根节点和 `viewBox`,不引用外部图片、脚本、远程资源
Show 3 other places
references/lark-doc-whiteboard.md:130In the instructions
### 步骤 3B:编辑已有画板 — 启动 lark-whiteboard SubAgent复杂图和已有画板更新必须启动 SubAgent。主 Agent 只传最小上下文,不直接执行 `lark-whiteboard` 的渲染和写入流程。复杂图 SubAgent 的最小上下文:- board_token- 图表目标、推荐画板类型、受众- 与图表直接相关的源段落或数据- 要求读取 [`../../lark-whiteboard/SKILL.md`](../../lark-whiteboard/SKILL.md),按其完整流程写入该 board_token多个画板互不依赖时,可并行启动多个 SubAgent;每个 SubAgent 只负责一个画板或一个 SVG 插入点,不要互相复用上下文。
references/lark-doc-whiteboard.md:30In the instructions
如果有多个位置需要插入图表,你需要根据每个图表的内容**分别决定**采用步骤 2A 还是 2B。思维导图、时序图、类图、饼图、甘特图可插入 mermaid 块;其他类型图表使用 SVG,简单图由主 Agent 直接写入,复杂图再启动 SubAgent。简单 Mermaid / SVG 图可由主 Agent 直接写入本地 XML;需要专门视觉设计、信息密度较高或容易布局翻车的 SVG,再启动 SubAgent 产出完整片段。
references/lark-doc-whiteboard.md:59In the instructions
Sub Agent 需要携带以下的最小上下文,以及后续的 [SVG 设计 Workflow] 章节指南:- doc token、插入位置(标题 / block_id / command)- 图表目标、受众、源段落或数据- 要求读取 `lark-doc-xml.md`;不需要读取 `lark-whiteboard`- SVG 必须完整自包含:包含 `<svg>` 根节点和 `viewBox`,不引用外部图片、脚本、远程资源
Low risk

Preview and download operations save protected Lark attachments into the local workspace

Source references: 6
What we found

Preview is not memory-only: the command explicitly writes the asset to a local --output path. The download operation likewise saves images, attachments, or whiteboard thumbnails.

Why this matters

Other users of a shared machine, persistent workspace backups, or later agent tasks may access the downloaded copy. Personal information or trade secrets in the file therefore gain another storage location.

The candidate is accurate: “preview” writes the attachment to a user-specified local path, and download also persists content, leaving a local copy of potentially protected material. This occurs only when preview/download is requested with a resource token and output path and is normal functionality, not evidence of unauthorized access. A user can select a controlled directory, restrict local sync/backups, verify file permissions, and remove the copy afterward according to retention rules.

references/lark-doc-media-preview.md:6In the instructions
优先用于查看、预览文档中的图片或文件素材(`file_token`)。命令会把素材保存到本地路径,便于后续打开查看内容。
Show 5 other places
references/lark-doc-media-preview.md:16In the instructions
```bash# 预览图片/文件素材lark-cli docs +media-preview --token "Z1Fjxxxxxxxx" --output ./asset# 指定输出文件名(带扩展名则不会自动补全)lark-cli docs +media-preview --token "Z1Fjxxxxxxxx" --output ./asset.png```
references/lark-doc-media-download.md:16In the instructions
```bash# 下载图片/文件素材(默认 type=media)lark-cli docs +media-download --token "Z1Fjxxxxxxxx" --output ./asset# 指定输出文件名(带扩展名则不会自动补全)lark-cli docs +media-download --token "Z1Fjxxxxxxxx" --output ./asset.png# 下载画板缩略图(whiteboard token)lark-cli docs +media-download --type whiteboard --token "wbcnxxxxxxxx" --output ./whiteboard```
references/lark-doc-media-preview.md:17In the instructions
```bash# 预览图片/文件素材lark-cli docs +media-preview --token "Z1Fjxxxxxxxx" --output ./asset# 指定输出文件名(带扩展名则不会自动补全)lark-cli docs +media-preview --token "Z1Fjxxxxxxxx" --output ./asset.png```
references/lark-doc-media-download.md:6In the instructions
下载文档中的图片/文件素材(`file_token`),或下载画板缩略图(`whiteboard_id`)。当 `--output` 不带扩展名时,会根据响应的 `Content-Type` 自动补全扩展名。
references/lark-doc-media-download.md:17In the instructions
```bash# 下载图片/文件素材(默认 type=media)lark-cli docs +media-download --token "Z1Fjxxxxxxxx" --output ./asset# 指定输出文件名(带扩展名则不会自动补全)lark-cli docs +media-download --token "Z1Fjxxxxxxxx" --output ./asset.png# 下载画板缩略图(whiteboard token)lark-cli docs +media-download --type whiteboard --token "wbcnxxxxxxxx" --output ./whiteboard```
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

Fallback history restoration clears and rewrites the cloud document and may permanently lose comments or unsupported resources

Source references: 3
What we found

When a requested revision_id is absent from history entries, the workflow permits fetching the old body and executing one overwrite against the current document. The instructions say this rebuilds the body and block IDs and cannot guarantee preservation of comments or other non-body objects.

Why this matters

If the target is wrong or the old revision/reference replay is incomplete, the current cloud body, comment associations, and resource structure may be replaced. Existing block links will also become invalid.

The risk is supported, but only when a user requests rollback by revision_id, no history entry is found, and the target revision remains readable. The fallback performs one overwrite of the current cloud document, rebuilding content and block IDs; comments and other non-body objects may not survive. The workflow requires version checks, a single overwrite, and stopping on warnings, conflicts, or failed verification. A user can require confirmation of comment/resource preservation and a recoverable copy first.

references/lark-doc-history.md:9In the instructions
- `overwrite` 会重建正文和 block ID,且无法保证保留评论等非正文对象。用户要求保留这些对象时,应先说明限制并确认。- `overwrite` 返回 warning 或 `partial_success` 时,先核验最新内容。核验失败或发生 revision conflict 时停止,不要再次覆盖。- 权限、网络或临时系统错误应保留原错误分类,不得解释为目标版本不存在。
Show 2 other places
references/lark-doc-history.md:19In the instructions
2. 找到目标记录后,使用该记录的 `history_version_id` 调用 `+history-revert`。不要将 `revision_id` 传给回滚接口。返回 `running` 时使用 `+history-revert-status` 查询;只有 `done` 表示成功,其他终态均停止并报告。3. 没有目标记录但用户指定了 `revision_id` 时,可读取目标版本并恢复正文:   - 使用 `docs +fetch --doc "<doc>" --revision-id <revision_id> --scope full --detail full --format json` 读取目标版本。确认文档一致、返回的 `revision_id` 与目标一致,且 `content` 不是 `<fragment>`。   - 使用 `docs +fetch --doc "<doc>" --scope full --detail full --format json` 读取当前完整文档,其 `content` 同样不得是 `<fragment>`。目标与当前响应的 `revision_id` 相同时直接结束,不执行 `overwrite`。否则移除目标 `content` 中旧的 block ID,将正文写入任务目录下的相对路径,然后仅执行一次 `docs +update --doc "<doc>" --command overwrite --revision-id <current_revision_id> --content @target.xml`,其中 `current_revision_id` 来自当前文档响应。目标响应包含非空 JSON object 形式的 `reference_map` 时,将其写入相对路径并追加 `--reference-map @target-reference-map.json`;否则省略该参数。`+update` 不支持 `--yes`。   - 使用 `docs +fetch --doc "<doc>" --scope full --detail full --format json` 读取最新完整文档并核验。忽略重新生成的 block ID,正文结构、文本、链接和引用资源应与目标版本一致。4. 目标版本明确不可读时停止并报告。
references/lark-doc-update.md:74In the instructions
|`append`|仅在文末追加,等价于 `block_insert_after --block-id -1`|`--content`||`overwrite`|清空后重写全文,丢失图片、评论等内容,非必要不使用|`--content`|
Could it bypass safety checks?Looks for skipped website security checks, excessive file access, or actions that skip your approval.No risks found
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.No risks found
Could it change links or payment recipients without asking?Looks for forced referral or payment changes combined with instructions to hide the change.No risks found

Inside this skill

2 instruction sections

The Skill uses lark-cli to read, create, and precisely modify Lark documents, and recommends explicitly acting as the user. Its editing workflow calls for reading current content, applying the smallest suitable patch, and fetching again for verification.

View source
SKILL.md:17In the instructions
**身份:文档操作推荐显式指定 `--as user`。**
references/lark-doc-update.md:29In the instructions
1. **Observe(读取现状)**:先 `docs +fetch` 读取当前文档状态,并按意图选择最小范围。   - 改某一节或大文档:先 `--scope outline --max-depth 2` 找章节,再 `--scope section --start-block-id <标题id> --detail with-ids`   - 精确跨节区间:用 `--scope range --start-block-id xxx --end-block-id yyy`   - 只有模糊关键词:用 `--scope keyword --keyword "key1|key2" --context-before 1 --context-after 1 --detail with-ids`   - 明确整篇重构才读 `--detail with-ids` 全文;只读摘要或确认事实时用更轻的 fetch2. **Diagnose(诊断问题)**:判断用户目标、当前结构、语气、重复、断流、事实口径和需要保留的资源;识别哪些 block 必须原样保留。3. **Patch Plan(制定局部计划)**:把修改拆成最小安全操作:简单行内文本替换用 `str_replace`,但它不支持资源替换;单个 block 用一个 `--block-id`,同一直接父节点下的连续 block 用 `--start-block-id`/`--end-block-id`。连续范围适用于 `block_replace` 和 `block_delete`。整段/整块重写用 `block_replace`;增补章节用 `block_insert_after`;删冗余用 `block_delete`;调整顺序用 `block_move_after`。4. **Patch(精确修改)**:按 block / section 执行局部命令。替换内容必须符合目标父容器的结构;例如替换列表项范围时使用 `<li>...</li>`。保护 `<cite>`、`<img>`、`<source>`、`<whiteboard>`、`<sheet>`、`<bitable>`、`<synced_reference>` 等 token 化内容,不要改成纯文本或占位符。同一 block 的多处修改合并成一次 `block_replace`。5. **Verify(fetch 验证)**:每轮写操作后按影响范围重新 fetch,检查用户要求、结构、语气、事实、资源块和 block ID 是否符合预期;不满足就基于最新 fetch 结果继续 Diagnose / Patch,不要沿用上一轮 block ID。

The authoring workflow creates an exclusive draft directory and decision baseline under the current working directory, retains the draft, and then submits the generated XML to Lark to create a document.

View source
references/lark-doc-create-workflow.md:90In the instructions
不预建临时目录、草稿或决策文件。将上述 JSON 原样替换命令中的占位符并实际执行:```bashlark-cli docs +script --command init-draft --presentation-decision '<上方完整 JSON>' --format json```成功后:- 保持当前工作目录不变;将 `data.workspace` 原样记为 `work_dir`,将 `data.draft_path` 原样记为 `draft_path`;遵循 `data.tip`,后续始终使用 `@./<draft_path>`。- CLI 会创建独占的 `work_dir` 并保存 `.presentation-decision.json` 作为固定基线,**但不会创建 `draft_path` 指向的 XML**。`draft_path` 是当前任务可直接写入的新文件路径;要求、资料或 contract 实质变化时,提交新决策并重新初始化,不得直接改基线。
references/lark-doc-create-workflow.md:114In the instructions
### Step 7:创建文档并处理局部失败。1. 只有最新 release candidate 完成 Draft Profile Check 和 XML 规则复查后,才读取 [`lark-doc-create.md`](lark-doc-create.md),使用同一个 `draft_path` 创建文档。2. 创建结果存在 warning、局部资源失败或回查发现局部问题时,不得再次新建文档;读取 [`lark-doc-update.md`](lark-doc-update.md),对已创建文档做最小范围修复,并按 update 流程 fetch 验证。### Step 8:交付。保留 Step 4 返回的 `work_dir` 及其中的创作草稿。最终只交付用户需要的结果,并说明必要来源、未关闭缺口、异常、失败或阻塞原因,以及文档 URL 或 token。

A document fetch can return the body, resource references, and unresolved comments visible to the current user; the instructions call for retaining the complete JSON response.

View source
references/lark-doc-fetch.md:7In the instructions
```bash# 读取整篇文档,并附带当前用户可见的未解决评论;lark-cli docs +fetch --doc "文档URL或token"
references/lark-doc-fetch.md:104In the instructions
```- `content` 的格式由 `--doc-format` 决定。`reference_map` 是结构化 sidecar,一级键表示引用组:普通资源组通常以 `block_type` 命名,二级键 `ref` 对应正文中的临时引用,其值由真实属性组成;保留组 `comments` 使用 `<ref>.data` 保存评论。XML、Markdown 和 IM Markdown 在存在可见评论时都会返回该组;Markdown 正文没有与评论 key 对应的内联引用,这是有意的协议设计。没有提取数据时,`reference_map` 可能为空。`comments.tips.data` 表示评论因数量上限被截断,文档顶层 `tips` 则给出安全回放或依赖降级提示。`content` 和 `reference_map` 属于同一份响应,应保留完整 JSON 响应;`im-markdown` 仅用于获取内容后在 `lark-im` 场景下使用。设置 `--scope` 时会被 `<fragment>` 包裹,详见下文“局部读取的输出结构”。- 评论内容不保证全部返回,需要详细信息时使用  `drive +list-comments` 获取完整评论。

The Skill includes stateful capabilities for downloading and uploading local resources, reading the clipboard, setting or deleting covers, modifying Mindnote nodes, and reverting document history.

View source
SKILL.md:31In the instructions
- **草稿初始化、解析与统计 — [`+script`](references/lark-doc-script.md)**:支持解析文档 URL / token 与本地 XML,统计字数并返回字符诊断;不支持 Markdown 输入。- **历史版本 — [`+history-list` / `+history-revert` / `+history-revert-status`](references/lark-doc-history.md)**:查询、回滚文档历史版本或检查回滚任务状态。### 资源、画板与思维笔记- **插入本地素材 — [`+media-insert`](references/lark-doc-media-insert.md)**:在文末插入本地图片或文件。- **预览素材 — [`+media-preview`](references/lark-doc-media-preview.md)**:预览文档或评论中的图片、附件或素材。- **下载素材 — [`+media-download`](references/lark-doc-media-download.md)**:下载文档中的图片、附件、素材或画板缩略图。- **Docx 封面 — [`+resource-download` / `+resource-update` / `+resource-delete`](references/lark-doc-resource-cover.md)**:下载、更新或删除 Docx 封面。- **画板 — [`画板工作流`](references/lark-doc-whiteboard.md)**:创建或更新画板时先读取工作流;更新已有画板必须复用现有 token,禁止新建空白画板;使用 [`whiteboard +update`](../lark-whiteboard/references/lark-whiteboard-update.md) 写入。- **思维笔记 — `mindnotes`**:已有思维笔记走 [`思维笔记链路`](references/lark-doc-mindnote.md);新建思维笔记走 [`lark-doc-whiteboard`](references/lark-doc-whiteboard.md)。
Start here · InstructionsSKILL.md
lark-doc
Lines connect the instruction file to its sections, not an observed execution order. Select a section to read the source.

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 records44 files

Coverage and gaps

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-doc-create-workflow.mdFull text included
  • references/lark-doc-create.mdFull text included
  • references/lark-doc-fetch.mdFull text included
  • references/lark-doc-history.mdFull text included
  • references/lark-doc-media-download.mdFull text included
  • references/lark-doc-media-insert.mdFull text included
  • references/lark-doc-media-preview.mdFull text included
  • references/lark-doc-mindnote.mdFull text included
  • references/lark-doc-resource-cover.mdFull text included
  • references/lark-doc-script.mdFull text included
  • references/lark-doc-update.mdFull text included
  • references/lark-doc-whiteboard.mdFull text included
  • references/genres/business-analysis.mdFull text included
  • references/genres/data-report.mdFull text included
  • references/genres/email.mdFull text included
  • references/genres/execution-plan.mdFull text included
  • references/genres/formal-doc.mdFull text included
  • references/genres/meeting-minutes.mdFull text included
  • references/genres/memo-brief.mdFull text included
  • references/genres/official-redhead.mdFull text included
  • references/genres/prd.mdFull text included
  • references/genres/proposal.mdFull text included
  • references/genres/research-report.mdFull text included
  • references/genres/retrospective.mdFull text included
  • references/genres/route-consumer.mdFull text included
  • references/genres/route-creative.mdFull text included
  • references/genres/route-knowledge.mdFull text included
  • references/genres/route-marketing.mdFull text included
  • references/genres/route-media.mdFull text included
  • references/genres/route-opinion.mdFull text included
  • references/genres/route-personal-brand.mdFull text included
  • references/genres/route-platform.mdFull text included
  • references/genres/route-report.mdFull text included
  • references/genres/route-workplace.mdFull text included
  • references/genres/sop-tutorial.mdFull text included
  • references/genres/technical-doc.mdFull text included
  • references/genres/wechat.mdFull text included
  • references/genres/weekly-report.mdFull text included
  • references/genres/white-paper.mdFull text included
  • references/genres/xiaohongshu.mdFull text included
  • references/lark-doc-md.mdFull text included
  • references/lark-doc-xml-extended-blocks.mdFull text included
  • references/lark-doc-xml.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/genres/business-analysis.mdSupporting file
  • references/genres/data-report.mdSupporting file
  • references/genres/email.mdSupporting file
  • references/genres/execution-plan.mdSupporting file
  • references/genres/formal-doc.mdSupporting file
  • references/genres/meeting-minutes.mdSupporting file
  • references/genres/memo-brief.mdSupporting file
  • references/genres/official-redhead.mdSupporting file
  • references/genres/prd.mdSupporting file
  • references/genres/proposal.mdSupporting file
  • references/genres/research-report.mdSupporting file
  • references/genres/retrospective.mdSupporting file
  • references/genres/route-consumer.mdSupporting file
  • references/genres/route-creative.mdSupporting file
  • references/genres/route-knowledge.mdSupporting file
  • references/genres/route-marketing.mdSupporting file
  • references/genres/route-media.mdSupporting file
  • references/genres/route-opinion.mdSupporting file
  • references/genres/route-personal-brand.mdSupporting file
  • references/genres/route-platform.mdSupporting file
  • references/genres/route-report.mdSupporting file
  • references/genres/route-workplace.mdSupporting file
  • references/genres/sop-tutorial.mdSupporting file
  • references/genres/technical-doc.mdSupporting file
  • references/genres/wechat.mdSupporting file
  • references/genres/weekly-report.mdSupporting file
  • references/genres/white-paper.mdSupporting file
  • references/genres/xiaohongshu.mdSupporting file
  • references/lark-doc-create-workflow.mdSupporting file
  • references/lark-doc-create.mdSupporting file
  • references/lark-doc-fetch.mdSupporting file
  • references/lark-doc-history.mdSupporting file
  • references/lark-doc-md.mdSupporting file
  • references/lark-doc-media-download.mdSupporting file
  • references/lark-doc-media-insert.mdSupporting file
  • references/lark-doc-media-preview.mdSupporting file
  • references/lark-doc-mindnote.mdSupporting file
  • references/lark-doc-resource-cover.mdSupporting file
  • references/lark-doc-script.mdSupporting file
  • references/lark-doc-update.mdSupporting file
  • references/lark-doc-whiteboard.mdSupporting file
  • references/lark-doc-xml-extended-blocks.mdSupporting file
  • references/lark-doc-xml.mdSupporting file

Operations mentioned in code and instructions

Read files
SKILL.md:15In the instructions
**CRITICAL:先判断场景,再读取该场景的参考文件;不要在任务开始时一次性读取全部参考文件。每个文件只在首次进入对应阶段时读取一次。**
references/lark-doc-whiteboard.md:43In the instructions
如果 Mermaid 已在本地文件中,可写成 `<whiteboard type="mermaid" path="@./diagram.mmd"></whiteboard>`;CLI 会在写入前读取文件并展开为内联内容。
Run commands
references/lark-doc-create-workflow.md:92In the instructions
```bashlark-cli docs +script --command init-draft --presentation-decision '<上方完整 JSON>' --format json
references/lark-doc-create.md:9In the instructions
```bash# 简单内容优先使用 `--content -`,文件导入如下:
references/lark-doc-fetch.md:7In the instructions
```bash# 读取整篇文档,并附带当前用户可见的未解决评论;
Connect to websites
references/lark-doc-create.md:25In the instructions
      "revision_id": 1,      "url": "https://xxx.feishu.cn/docx/docx_token",      "new_blocks": [
references/lark-doc-md.md:63In the instructions
```markdown![alt text](https://example.com/photo.png)```
references/lark-doc-md.md:66In the instructions
- `alt text` 为图片描述(可选,可留空)- URL 支持 `http://` 和 `https://` 协议- 对应的 XML 格式为:`<img href="https://example.com/photo.png"/>`
Lines read
2,378
File checksum (to compare versions)
85fe4664a9fed111b7461736fc8ad0ef6cb0c39a9ed78078c8e71d6c8b736171