Building & integrations

Feishu / Lark CLI

Documents, sheets, bitable, calendar, messages and mail from the command line.

Paid $9 list, $7 until 2026-12-31 · one skill, yours for good. The outline, the steps and the file open after purchase.

Background

lark-cli is the official command-line tool for Feishu/Lark. It can operate the various Feishu resources: documents, calendar, messages, bitable, mail, tasks and so on.

When the user asks to operate Feishu resources (checking a schedule, creating a document, sending a message, etc.), use this skill to call lark-cli.

Why it is built this way

The body teaches the lookup before it gives any command. Only documents and today's agenda get concrete syntax; im, base, task and mail are listed as lark-cli <domain> --help. Subcommand names and parameter names belong to the installed CLI, so a syntax table copied into a skill ages badly. Steps 1 and 2 therefore say: read the domain help, then the command help, and only then assemble the call.

Steps 4 and 5 stay apart on purpose. --dry-run previews a request without executing it, while --yes is the flag a delete or a send requires, so the preview is meant to be read before the flag that commits. Every call runs as the signed-in user, which makes a wrong recipient leave a mark on the user's own account. The caution against bulk deleting and bulk sending follows from that identity, since the account carrying the result is the user's own.

Where it bites

• Example syntax reused across domains Documents and today's agenda have a written-out call, and the other domains do not. Typing an im or base command from memory tends to end in an unrecognised parameter and a CLI error, or in a call that hits a different resource than intended. The two lookup steps exist for exactly this gap.
• A send with nothing previewed --dry-run previews the request without executing it. Skipping it means the request that goes out was never read, and a send or delete still needs --yes. The bulk deletes and bulk sends called out at the end of the body are the cases where that missing preview costs the most.
• Raw output pasted back into the chat A calendar or bitable listing without --jq returns the full response, and pasting it back buries the answer the user asked for. Usage note 3 puts --jq on the default path. The response shape comes from the CLI, so the filter is also where the field names get checked against what the command really returns.

When to use it

Operate Feishu/Lark resources through lark-cli, including documents, spreadsheets, bitable, calendar, messages, tasks and mail. Use when the user mentions Feishu documents, Feishu spreadsheets, Feishu calendar, Feishu messages, Feishu tasks, Feishu mail, or asks to create a document, check a schedule, send a message, or read meeting notes. Executes as the logged-in user's own identity; high-risk actions require explicit authorization from the user.