CodexClaude CodeCursorGeneric
Back to Tools
cli · tool profile
Cli
The official Lark/Feishu CLI tool, maintained by the larksuite team — built for humans and AI Agents. Covers core business domains including Messenger, Docs, Base, Sheets, Calendar, Mail, Tasks, Meetings, and more, with 200+ commands and 20+ AI Agent Skills.
productivity CodexClaude CodeCursorGeneric
01
At a glance.
A compact read before the deeper capability notes and official setup links.
02
Core features.
Feature cards focus on what the tool helps users do, not generated setup commands.
The official Lark/Feishu CLI tool, maintained by the larksuite team — built for humans and AI Agents.
Covers core business domains including Messenger, Docs, Base, Sheets, Slides, Calendar, Mail, Tasks, Meetings, Markdown, and more, with 200+ commands and 24 AI Agent Skills.
Wide Coverage — 17 business domains, 200+ curated commands, 24 AI Agent Skills
AI-Friendly & Optimized — Every command is tested with real Agents, featuring concise parameters, smart defaults, and structured output to maximize Agent call success rates
💬 Messenger Send/reply messages, create and manage group chats, view chat history & threads, search messages, download media
📁 Drive Upload and download files, search docs & wiki, manage comments
📊 Base Create and manage tables, fields, records, views, dashboards, workflows, forms, roles & permissions, data aggregation & analytics
🖼️ Slides Create and manage presentations, read presentation content, and add or remove slides
04
Agent / Skill / MCP / Workflow fit.
This panel keeps technical format separate from the user-facing AI category.
05
Official setup path.
Generated install snippets are intentionally not mirrored here because they drift. The page links to source-owned setup docs instead.
06
Evidence and adoption notes.
These notes help a user decide whether to investigate the official project further.
Source repository last pushed at 2026-05-18T10:03:54Z.
Generated from source metadata; confirm operational details in the official project before adopting it.
Review the upstream license, maintenance activity, and issue history before using it in production.
Trusted source