agentleFS
vaaynevaayne/agent-kit/skills/lark-cli/SKILL.md

lark-cli

Skill54 starsChanged 27 days agoMITView on GitHub

Lark/Feishu workspace operations through the `lark-cli` tool — calendar and meeting rooms, docs, sheets, Base (多维表格), wiki, drive, mail, IM messages, tasks, OKR, approvals, minutes, video conferences, whiteboards, slides, contacts, attendance, and real-time events. Use whenever the user mentions 飞书 / Lark / 我的日程 / 约会议 / 订会议室 / 飞书文档 / 多维表格 / 知识库 / 云空间 / 发消息 / 群聊 / 邮件 / 待办 / OKR / 审批 / 妙记 / 会议纪要 / 画板 / 幻灯片, or asks to look up a colleague, or hands you a `feishu.cn` / `larksuite.com` URL. Also covers `lark-cli` setup, auth login, and permission-denied errors.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start with lark-cli --help to pick the domain, then read that domain's guide before the first call.

    line 34
  2. Very specific:

    Read lark-cli skills read lark-shared first for auth, --as user vs --as bot, and permission-denied handling.

    line 38
  3. Very specific:

    Every command's --help labels it read, write, or high-risk-write.

    line 44

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Lark CLI

lark-cli carries its own agent documentation, compiled into the binary and versioned with it. Read it from the CLI; do not work from memory and do not look for docs in this repo.

Routing

lark-cli --help                      # the 23 domains, one line each
lark-cli <domain> --help             # +shortcuts (prefer these) and raw API resources
lark-cli skills read lark-<domain>   # the domain guide: concepts, workflows, gotchas
lark-cli skills read lark-<domain> references/<file>.md   # deeper references
lark-cli schema <service>.<resource>.<method>             # params, types, scopes

Start with lark-cli --help to pick the domain, then read that domain's guide before the first call. lark-cli api <METHOD> <path> is the escape hatch when no typed command exists.

Read lark-cli skills read lark-shared first for auth, --as user vs --as bot, and permission-denied handling. Identity does not carry across commands: pass --as explicitly on every call in a workflow.

Rules

Every command's --help labels it read, write, or high-risk-write. high-risk-write requires --yes, and only after the user has confirmed. Use --dry-run to preview a request without sending it.

--jq <expr> filters JSON output. Suppress the _notice banner that otherwise pollutes every JSON response:

LARKSUITE_CLI_NO_UPDATE_NOTIFIER=1 LARKSUITE_CLI_NO_SKILLS_NOTIFIER=1 lark-cli ...

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.