How to use the Feishu Docs Editor agent skill (lark-doc)

What the lark-doc skill lets the agent do

The skill covers Feishu cloud documents (Docx and Wiki pages). According to its description, it handles reading, creating and editing documents, inserting or downloading image and attachment files, and working with mind notes. It also covers the document cover, whiteboards and document history.

The agent decides which reference guide to follow based on the task. Reading uses the fetch guide, new documents follow a creation workflow, and edits go through the update guide. The skill routes by the URL path or token, not by the domain name.

• Read or summarize a document from its URL or token
• Create a new document or import complete content you provide
• Edit, rewrite, polish or restructure existing text
• Insert or download images and attachments
• List, revert or check document history
• Manage the Docx cover and work with whiteboards and mind notes

What the skill does not cover

Some tasks belong to other skills. Comment operations (add, reply, list comments) and Drive file tasks such as finding, importing, exporting, uploading or managing permissions go to the lark-drive skill. Spreadsheet or Base table data is not covered by this skill at all.

If you ask to copy a document, the skill points the agent to the lark-drive copy command rather than rebuilding the content by reading and recreating it.

Install the lark-doc skill

Download the ZIP file from this page and unzip it. Then place the resulting folder in one of two locations: your user-level skills folder at ~/.claude/skills/, or a project-level .claude/skills/ folder inside the project you work in.

Alternatively, in the Claude apps you can upload the ZIP under Settings → Capabilities → Skills.

• User-wide: ~/.claude/skills/ (unzip here so the skill is available in every project)
• Single project: .claude/skills/ inside that project folder
• Claude apps: Settings → Capabilities → Skills, then upload the ZIP

Set up the requirements before first use

The skill cannot run without the lark-cli command-line tool, the lark-shared skill (which handles authentication and permission scopes) and a Feishu/Lark account. The skill recommends running document operations with --as user, which acts as your own user account.

The skill's metadata lists lark-cli help as the way to see available commands: lark-cli docs --help and lark-cli mindnotes --help. Authentication is only loaded when needed, so the agent reads the lark-shared guidance when it hits an authorization, identity or scope error, fixes it and retries.

• lark-cli command-line tool installed
• lark-shared skill present (authentication and scope handling)
• A Feishu/Lark account with user authorization

Trigger the skill with natural requests

You do not need special syntax. Paste a Feishu document link and say what you want done with it. The skill is meant to be triggered when you provide a document URL or token, including doubao.com links that contain /docx/ or /wiki/.

Links with /page/ followed by a token are a different product (a Miaoda app), not a Feishu cloud document, so the skill does not apply to them.

• "Summarize this Feishu doc: <link>"
• "Read the section on deployment in <link> and list the open steps"
• "Rewrite the introduction of <link> for a non-technical reader"
• "Create a new Feishu document with this outline: ..."
• "Download the images attached to <link>"

Read a document from the command line

The agent uses lark-cli under the hood. The read command below fetches a whole document, including unresolved comments visible to the current user. You can also read only part of a document by keyword, outline or section.

Use the outline scope first on long documents, then read a single section by its block ID.

Safety notes: scripts and network access

This skill runs scripts and uses the network. It sends requests to Feishu through lark-cli using your authorized account. Review what the agent plans to do before it writes.

The skill can change document content and can revert document history. Do not point it at important live documents without a review step. Consider working on a copy, which the lark-drive copy command can create.

• Check the proposed changes before accepting edits to live documents
• Prefer a copy when testing new edits
• Use history listing to confirm what can be reverted