Lark CLI Skill: Drive — File & Folder Management

What it is

The Lark CLI Drive skill adds cloud drive management capabilities to the Lark (Feishu) command-line interface. It lets you upload files, download documents, create folder hierarchies, and manage sharing permissions without opening the Lark web app. The skill integrates with the Lark Open API to perform drive operations directly from your terminal.

This skill is built for developers and teams who use Lark/Feishu as their collaboration platform and want to automate file operations. It is particularly useful for CI/CD pipelines that need to push build artifacts to shared drives, or for scripts that sync local directories with cloud storage.

How it saves time or tokens

Instead of navigating the Lark web interface to upload files or adjust permissions, you run a single command. Batch operations that would take minutes of clicking become one-line scripts. The CLI also enables automation in shell scripts and cron jobs, removing the need for manual file management entirely.

How to use

1. Install the Lark CLI and the Drive skill:

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

1. Configure authentication (one-time setup):

lark-cli config init
lark-cli auth login --recommend

1. Use drive commands to manage files:

# Upload a file
lark-cli drive upload ./report.pdf --folder <folder-token>

# Download a file
lark-cli drive download <file-token> -o ./downloads/

# Create a folder
lark-cli drive mkdir 'Project Assets' --parent <parent-token>

# List folder contents
lark-cli drive ls <folder-token>

Example

# Batch upload all PDFs in a directory to a Lark folder
for file in ./reports/*.pdf; do
  lark-cli drive upload "$file" --folder <folder-token>
  echo "Uploaded: $file"
done

# Set sharing permissions
lark-cli drive share <file-token> \
  --user user@example.com \
  --permission view

# Add a comment to a file
lark-cli drive comment <file-token> 'Review completed, approved for release'

Related on TokRepo

• Automation tools -- Explore other CLI-based automation workflows
• Task management tools -- Combine file management with project tracking

Common pitfalls

• Forgetting to run lark-cli auth login before drive commands results in authentication errors. The token expires periodically, so re-auth may be needed.
• Folder tokens are not the same as folder names. You need the token from the Lark URL or from lark-cli drive ls output.
• Large file uploads over slow connections may time out. Use the --retry flag for reliability on unstable networks.