Feishu / Lark Workflows
Overview
A routing skill for Feishu/Lark automation: native docs, Drive uploads, Bitable schema discovery, record writes, and CLI setup validation.
Use this skill whenever a task mentions Feishu, Lark, 飞书, 多维表, Bitable, Drive, native docs, or lark-cli.
Core Routes
| Route | Use When |
|---|---|
| Native docs | Create or fetch real Feishu/Lark documents |
| Drive upload | Upload local files and resolve openable URLs |
| Bitable metadata | Inspect fields before writing records |
| Bitable sync | Create/update records with correct field shapes |
| CLI setup | Validate lark-cli auth and scopes |
Common Commands
bashlark-cli auth status lark-cli auth scopes lark-cli docs +create --as user --title '<TITLE>' --markdown '<MARKDOWN>' lark-cli docs +fetch --as user --doc '<DOC_URL>' --format pretty lark-cli api GET "/open-apis/bitable/v1/apps/<BASE_TOKEN>/tables/<TABLE_ID>/fields?page_size=100" --as user
Bitable Rules
- Inspect field metadata before writing.
- URL fields often require
{link, text}. - Attachment fields usually require upload first, then field update.
- Do not assume wrapper commands support every field shape; direct
bitable/v1calls are often clearer.
Verification Checklist
-
lark-cliis installed -
lark-cli auth statuspasses - Target workspace/base/table IDs are known
- Field types are checked before writes
- Returned tokens are resolved to user-openable URLs


