
Feishu Drive
Let your agent list, organize, move, and delete files in Feishu (Lark) cloud drive from chat-driven JSON actions.
Overview
Feishu-drive is an agent skill for the Build phase that manages Feishu cloud drive files and folders via the feishu_drive tool actions.
Install
npx skills add https://github.com/m1heng/clawdbot-feishu --skill feishu-driveWhat is this skill?
- One tool `feishu_drive` with actions: list, info, create_folder, move, delete
- Parses folder tokens from Feishu drive URLs for navigation
- Supports doc, docx, sheet, bitable, folder, file, mindnote, and shortcut types
- Lists root or nested folders with token, name, type, url, and timestamps
- Move and delete operations require explicit file_token and type parameters
- 5 drive actions: list, info, create_folder, move, delete
- 8 documented Feishu file types including docx, sheet, and bitable
Adoption & trust: 867 installs on skills.sh; 4.3k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent needs to browse or reorganize Feishu Drive but lacks a single reference for tokens, actions, and file types.
Who is it for?
Builders running Feishu-connected agents who automate folder hygiene and file moves in Lark cloud storage.
Skip if: Teams not on Feishu/Lark, or workflows needing deep document editing inside docx/sheets rather than drive file operations.
When should I use this skill?
User mentions cloud space, folders, drive, or Feishu/Lark drive file operations.
What do I get? / Deliverables
The agent performs list, info, create_folder, move, and delete operations against Feishu drive with valid tokens and typed file identifiers.
- Executed drive operations (listing, folders created, files moved or deleted)
- Structured JSON action payloads the agent can reuse
Recommended Skills
Journey fit
Feishu Drive is an external product integration wired during Build when the agent needs real workspace storage APIs. Single-tool feishu_drive actions map to third-party SaaS integration, not core app frontend or backend code.
How it compares
Feishu-specific drive integration skill—not a generic cloud storage MCP or Google Drive connector.
Common Questions / FAQ
Who is feishu-drive for?
Solo developers and small teams using Feishu bots who want reliable drive list/move/delete behavior from their coding agent.
When should I use feishu-drive?
During Build when wiring agent tooling for cloud space, folders, or drive tasks, or when users ask to browse or reorganize Feishu storage.
Is feishu-drive safe to install?
Delete and move are destructive—review the Security Audits panel on this page and scope Feishu app permissions before enabling agent access.
SKILL.md
READMESKILL.md - Feishu Drive
# Feishu Drive Tool Single tool `feishu_drive` for cloud storage operations. ## Token Extraction From URL `https://xxx.feishu.cn/drive/folder/ABC123` → `folder_token` = `ABC123` ## Actions ### List Folder Contents ```json { "action": "list" } ``` Root directory (no folder_token). ```json { "action": "list", "folder_token": "fldcnXXX" } ``` Returns: files with token, name, type, url, timestamps. ### Get File Info ```json { "action": "info", "file_token": "ABC123", "type": "docx" } ``` Searches for the file in the root directory. Note: file must be in root or use `list` to browse folders first. `type`: `doc`, `docx`, `sheet`, `bitable`, `folder`, `file`, `mindnote`, `shortcut` ### Create Folder ```json { "action": "create_folder", "name": "New Folder" } ``` In parent folder: ```json { "action": "create_folder", "name": "New Folder", "folder_token": "fldcnXXX" } ``` ### Move File ```json { "action": "move", "file_token": "ABC123", "type": "docx", "folder_token": "fldcnXXX" } ``` ### Delete File ```json { "action": "delete", "file_token": "ABC123", "type": "docx" } ``` ## File Types | Type | Description | |------|-------------| | `doc` | Old format document | | `docx` | New format document | | `sheet` | Spreadsheet | | `bitable` | Multi-dimensional table | | `folder` | Folder | | `file` | Uploaded file | | `mindnote` | Mind map | | `shortcut` | Shortcut | ## Configuration ```yaml channels: feishu: tools: drive: true # default: true ``` ## Permissions - `drive:drive` - Full access (create, move, delete) - `drive:drive:readonly` - Read only (list, info) ## Known Limitations - **Bots have no root folder**: Feishu bots use `tenant_access_token` and don't have their own "My Space". The root folder concept only exists for user accounts. This means: - `create_folder` without `folder_token` will fail (400 error) - Bot can only access files/folders that have been **shared with it** - **Workaround**: User must first create a folder manually and share it with the bot, then bot can create subfolders inside it