Labsco
Labsco/Repos/larksuite/cli
REPO PACKAGE

larksuite cli

COMMUNITY
larksuite · publisher15,144 repository starsMIT · Freegithub.com/larksuite/cli
35skills
7ready to use

What's real here is broad: calendar (agenda, free/busy, room booking), messaging, docs, drive, native markdown files, sheets, slides, Base (Lark's multi-dimensional tables), tasks, mail, wiki, real-time event streaming, whiteboards, OKRs, attendance, approvals, and two workflow skills that chain several of those together into a meeting-summary or standup report. All of it sits on top of lark-cli's own 200+ commands and an OAuth login (lark-cli auth login --recommend) that grants scoped access per domain. Four of the 35 — good-skill, good-skill-complex, good-skill-minimal, and lark-demo — are named and described as exactly what they sound like: fixtures for testing the CLI's own skill-loading, not Lark functionality. A fifth, cli-e2e-testcase-writer, is for contributors adding Go end-to-end test coverage to the lark-cli codebase itself, which is a real job but not one about using Lark.

This is for someone already on Feishu or Lark who wants an agent sending messages, managing a calendar, or editing Base tables and sheets through their own logged-in account. If you aren't on that platform, the domain skills have nothing for you, and being "agent-native" — the README's own framing — doesn't change what account you need, only how smoothly an agent operates once you have one.

READ THE FULL ANALYSIS

Four skills point at a meeting skill that isn't in what we were given. lark-vc, lark-vc-agent, lark-minutes, and lark-note all carry the identical one-line description that a request is "handled uniformly by the lark-meeting skill" — but no skill named lark-meeting appears anywhere in the 35 we were shown. Whatever meeting-recording and minutes functionality the CLI actually has now lives somewhere we can't see from here.

Most of what's real needs a Lark account before it does anything. By the package's own accounting, 21 of the 35 skills need an authenticated Lark app and a granted OAuth scope (dep_class: account_key) before they work; 7 need nothing else to run, and the rest are unverified or need a local tool. That 7 figure is worth reading skeptically rather than as "free to use" — it's the bucket the fixture skills would fall into as well, since a skill that does nothing real also needs no account.

Checked 19 September 2026 against what we were given; we did not run the OAuth login flow or exercise any of the account-gated skills against a live Lark workspace.

7Work with nothing else to set up.
15,144Stars on the GitHub repository, at last check.