Feishu Document Manager

Problem to solve

When generated content must land in Feishu/Lark documents or knowledge bases, manual copying, ad-hoc API calls, and permission checks can interrupt the workflow. This skill packages document creation, writing, appending, and listing into reusable flows, useful for archiving study notes, articles, and daily or weekly reports, while reducing rework caused by repeated auth, permission, and block-structure mismatches.

How it works

The skill expects a self-built Feishu app, usually configured with FEISHU_APP_ID and FEISHU_APP_SECRET, plus document and drive read/write scopes. It authenticates with a tenant_access_token, creates a document to obtain a document_id, and then writes content through the Add Block API as typed blocks such as text, heading1, todo, code, and quote. Appending to an existing document uses the document root and adds blocks at the end. Common reference scripts support create, append, list, and duplicate checks. For batch archiving, it is safer to check existing entries first and skip duplicates based on date and topic.

Scope and caveats

This fits structured publishing and semi-automated writing, not direct Markdown pasting, because Feishu block APIs require block-by-block construction. Also watch token expiration, default document visibility, API rate limits, and rich-text element splitting. Keep a document_id map for multi-document scenarios. If the need is only read-only preview or one-off export, the full write path may be overkill.