What problem does it solve?
Provides a unified, reliable way to create, read, update, and manage Lark (Feishu) cloud documents and knowledge nodes so users do not need to manually handle tokens, media uploads/downloads, or wiki-node resolution. Begin by consulting the shared authentication and permission guidance before performing any operations to ensure correct scopes and identity handling.
Core Features & Use Cases
- Document lifecycle: create new documents from Lark-flavored Markdown, fetch document content as Markdown, and perform fine-grained updates (append, insert, replace, delete, overwrite) with selection strategies.
- Media orchestration: upload local images/files into documents, download embedded media or whiteboard thumbnails, and handle automatic extension resolution and rollback for multi-step insertions.
- Discovery & token resolution: search cloud space for docs/wiki/sheets to locate targets, and resolve wiki nodes to real obj_token/file_token to route operations to the correct API.
- Whiteboard handling: create blank whiteboards and surface generated board_tokens for downstream editing via the whiteboard skill; explicitly warn that existing whiteboards cannot be edited via docs +update.
- Operational safety: emphasizes permission checks, idempotency options, and guidance to avoid overwriting non-reproducible items like embedded media or comments.
Quick Start
Create a new Lark document titled "Project Plan", insert a blank whiteboard, and upload the architecture image to the document.
