How to use the Feishu Drive File Manager agent skill (lark-drive)

What is an agent skill, and what does lark-drive let the agent do?

An agent skill is a folder containing a SKILL.md file and supporting reference files. When an agent loads it, it gets specific procedures for one tool or product instead of guessing. The lark-drive skill (version 1.0.0 in its metadata) covers Feishu Drive, which the source also calls 云盘, 云存储, 网盘 or 我的空间.

With the skill installed, the agent knows how to upload and download files, create and copy folders and documents, look up metadata and permission settings, add or resolve comments, manage version history, rename items, apply secure labels, and import local Word, Markdown, Excel, CSV, PPTX or .base files into online Feishu formats. It works through the lark-cli command-line tool.

• Manage files and folders: upload, download, create folders, copy, move, delete
• Check metadata, permission settings, comments, subscriptions and version history
• Import local files: .docx/.md/.txt/.html to docx, .xlsx/.csv to sheet or bitable, .pptx to slides
• Resolve Feishu or doubao.com drive URLs and tokens to the real resource type

Install the lark-drive skill

Download the skill ZIP from this page and unzip it into one of these locations. Use ~/.claude/skills/ for a personal install available across your projects, or a project's .claude/skills/ folder to limit it to one project.

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

• Personal: unzip into ~/.claude/skills/
• Project only: unzip into the project's .claude/skills/ folder
• Claude apps: Settings → Capabilities → Skills, then upload the ZIP

Set up the prerequisites before you start

The skill cannot work without the lark-cli command-line tool and a Feishu/Lark account with appropriate Drive scopes or bot authorization. The SKILL.md file tells the agent to read the lark-shared skill first, because that file explains authentication and permission handling.

Run lark-cli drive --help to see the drive command list that the skill's metadata points to.

• lark-cli installed and available on the command line
• A Feishu/Lark account with the needed Drive scopes, or bot authorization
• The lark-shared skill present, since the drive skill depends on its authentication instructions

How to trigger the skill with natural requests

You do not need special syntax. Describe the task in plain language and include the document URL or token when you have one. The skill's routing rules map common phrases to the right command.

Useful phrasings include finding recently edited or self-created files, importing a local file into a target type, and asking for a permission or risk review. Requests to delete things or open sharing broadly will trigger a read-only discovery step first, followed by a list for you to confirm.

• "Find the Feishu docs I created last week about the Q3 budget"
• "Import this local CSV into Feishu as a spreadsheet"
• "Add a comment on this doc asking for the release notes"
• "Check who can view this document link and list any public access"
• "Rename this file to Final Report 2024"

Examples of what the agent will do

For imports, the skill says a local .xlsx, .csv or .base file must go to a bitable through lark-cli drive +import --type bitable, and a local .pptx goes to slides with a 500MB limit. Batch imports into the same folder must run one at a time, because concurrent imports to one location can hit server conflict errors.

For copies, the skill requires lark-cli drive +copy rather than exporting and re-importing. For comments, it selects the matching drive +<verb> comment command and reads its reference first.

Safety: scripts, network and confirmations

This skill runs scripts and uses the network: it calls lark-cli, which talks to Feishu services with your authorization. Only install skills you trust and check that your Feishu account has the access you intend to give.

For high-risk writes such as deletions, public permission changes, owner transfers, version deletion or rollback, and bulk move, overwrite or sync, the skill requires the target, the exact execution details and your explicit confirmation in the same turn. Requests like "delete the unused files" only produce a list of candidates for review. The skill also says that when drive +inspect or drive +upload fails with not found, permission denied or missing scope, the agent should stop rather than retry.

• Do not run bulk permission or deletion jobs without reviewing the candidate list
• Expect the agent to ask for confirmation before any high-risk write
• Stop and fix permission or scope errors instead of retrying

Tips for getting good results

Give the full URL or token and say what type you expect. Name the target folder for imports so the agent does not default to the root. If you only know a title, ask the agent to search first so it can identify a unique source.

For document content edits, the skill hands off to lark-doc; for spreadsheet or Base row data it hands off to lark-sheets or lark-base; for wiki nodes and members it hands off to lark-wiki; and for native Markdown files it hands off to lark-markdown. Install those skills if you need those tasks.

• Paste the full URL when you can, rather than a bare token
• Name the target folder for imports
• Ask for a plan first when you want to review before anything changes