Lark CLI Skill: Docs — Document Creation & Editing

What it is

Lark CLI Docs is a skill for the Lark (Feishu) CLI that automates cloud document operations. It lets you create documents from Markdown, read and update existing doc content, insert images, and search across your document library -- all from the command line or scripts.

This skill targets developers and teams using Lark/Feishu for documentation who want to automate repetitive document tasks. It is particularly useful for CI/CD pipelines that generate release notes, teams that sync documentation from code repositories, and anyone who prefers writing in Markdown over the Lark web editor.

How it saves time or tokens

Manually creating and formatting documents in the Lark web UI is slow for repetitive tasks. This skill lets you batch-create documents from Markdown files, which means documentation generated by AI agents or build scripts flows directly into your Lark workspace without copy-pasting.

For AI-assisted workflows, an agent can generate Markdown content and push it to Lark in a single command, eliminating the human step of opening a browser and pasting content.

How to use

1. Install the Lark CLI and the docs skill:

npm install -g @larksuite/cli
npx skills add larksuite/cli -y -g

1. Configure authentication:

lark-cli config init
lark-cli auth login --recommended

1. Create a document from Markdown:

lark-cli docs create --title 'Release Notes v2.1' --content-file notes.md

Example

Search for documents and update one with new content:

# Search for documents by title
lark-cli docs search --query 'API Reference'

# Update a document by ID
lark-cli docs update --doc-id 'doxcn1234567890' \
  --content-file updated-api-reference.md

# Insert an image into a document
lark-cli docs insert-image --doc-id 'doxcn1234567890' \
  --image-path ./architecture-diagram.png

Related on TokRepo

• AI tools for documentation -- Tools for automated documentation workflows
• AI tools for automation -- CLI-based automation tools

Common pitfalls

• The Lark API has rate limits. Batch-creating many documents in rapid succession triggers throttling. Add delays between requests or use the batch API when available.
• Markdown-to-Lark conversion does not support all Markdown extensions. Complex tables and footnotes may lose formatting.
• Authentication tokens expire. Set up token refresh in your CI/CD pipeline to avoid failures in long-running jobs.
• Document IDs are required for update and delete operations. Store the ID returned by the create command for later use.