What problem does it solve?
Working with Lark/Feishu resources through a CLI involves many object types (docs, wiki, sheets, Base, calendar, IM, mail) with non-interchangeable tokens and different identity requirements, making it easy to call the wrong API, use the wrong identity, or leak sensitive internal data.
Core Features & Use Cases
- Task Routing: Classifies each request and delegates to the matching
lark-* skill (lark-doc, lark-wiki, lark-drive, lark-sheets, lark-base, lark-calendar, lark-im, lark-mail, and more).
- Token and Identity Handling: Resolves wiki node wrappers to real object tokens and chooses between
--as user and --as bot identities deliberately.
- Safe Read/Write Patterns: Starts with narrow reads, prefers block-level updates over whole-document overwrites, and requires explicit intent for high-risk actions like deletes or permission changes.
- Use Case: Given a Feishu wiki URL, resolve the underlying document token, fetch the docx content with
--api-version v2, and update a specific section without touching comments or permissions.
Quick Start
Use the lark-cli-workflow skill to read this Feishu doc URL and summarize its contents without exposing internal links.