Manage files, folders, and documents in Lark Drive with upload, download, import, comments, and permissions. Upload and download files; create folders; copy, move, and delete files; import local Word/Markdown/Excel/CSV/PPTX and Base snapshots as cloud documents Add full-text or block-level comments to docs, sheets, slides, and files; manage comment replies and reactions; subscribe to comment change events Manage document permissions, transfer ownership, and apply for access; update file titles across docx, sheet, bitable, file, folder, and wiki types Auto-unwrap wiki URLs to underlying document types (docx, sheet, bitable, slides, file); inspect document metadata and view access records Sync local directories with Drive folders using hash-based or timestamp-based diffing; version history, export, and secure label management

Manage Lark Wiki spaces, members, nodes, and document organization hierarchies. Create, list, and delete knowledge spaces; retrieve space and node information via token or URL Add, remove, and list space members with support for users, groups, and departments; enforces identity constraints (bot identity cannot manage department members) Create, move, copy, and delete wiki nodes; organize documents and shortcuts within space hierarchies Prioritizes user identity over bot identity for personal knowledge resources; includes safety checks for destructive operations like space deletion requiring explicit user confirmation

Create and edit Lark Office slides with XML protocol, supporting presentation creation, page management, and content modification. Supports three creation workflows: one-step creation for simple slides, two-step creation (empty presentation + page-by-page addition) for complex content, and block-level editing of existing pages without reordering Handles slide operations including create, read, delete, and replace at both presentation and individual page levels; automatically parses /slides/ and /wiki/ URLs to extract presentation tokens Requires planning layer (slide_plan.json) before XML generation for new presentations or major rewrites; includes visual planning (layout_type, visual_focus, text_density) and asset planning with fallback strategies Enforces strict XML validation: text must use <content><p>...</p></content> , images require uploaded file_tokens (no external URLs), and all complex content undergoes post-creation verification against validation checklist Provides template search, summarization, and extraction via template_tool.py to avoid boilerplate; prioritizes user identity ( --as user ) for personal content operations

Markdown file operations for Feishu Drive: create, read, edit, patch, and compare native .md files. Five core commands: create new files, fetch remote content, overwrite existing files, apply local text/regex patches, and diff versions or remote vs. local drafts Patch operation downloads the full file, applies replacements locally, then re-uploads; supports single pattern-content pairs and rejects empty results File names must explicitly include .md suffix; content input accepts strings, local files via @file , or stdin via - Requires lark-cli binary and authentication via shared Feishu credentials; file management tasks like rename, move, delete, and permissions belong in lark-drive skill