larksuite/cli

29 skills11M installs18.2k starsGitHub

Install

npx skills add https://github.com/larksuite/cli

Skills in this repo

1Lark Doclark-doc enables agents to read and edit Feishu cloud documents (docx and wiki documents). It supports creating documents from scratch, fetching content in XML or Markdown, patching local changes, inserting media, and managing revisions.501kinstalls2Lark Baselark-base teaches an agent to operate Feishu (Lark) Base, the multidimensional table product, through lark-cli base commands. It covers resolving URLs and titles to tokens, tables, fields, records, views, forms, dashboards, workflows, BaseApp pages, advanced permissions and roles, and the template center. The main file routes each task to a detailed reference document that the agent must read before editing. The text is written in Chinese and defers authentication to lark-shared and file import or export to lark-drive.499kinstalls3Lark Sharedlark-shared is the base layer that every lark-cli skill relies on. It defines how an agent picks user or bot identity, handles login and scope errors, and shows authorization URLs with a QR code. It sets safety rules such as never printing secrets, confirming writes and deletes, and pausing at the exit code 10 gate for high-risk writes. A table of triggers points to reference files for identity, output contract, approvals, config init and update notices. The text is written in Chinese.498kinstalls4Lark Drivelark-drive provides CLI access to Feishu cloud storage (Drive/cloud disk), enabling file and folder management, local file imports, document copying, permission governance, and comment management.495kinstalls5Lark ImThe lark-im skill guides agents through Feishu Lark instant messaging with the lark-cli binary. It covers messages, chats, threads, reactions, flags, and media resources, with shortcuts like +messages-send, +chat-search, +messages-search, and +messages-resources-download for common workflows. Agents must read lark-shared first for authentication and permission handling. The skill distinguishes user identity (--as user) from bot identity (--as bot), explaining when each token type succeeds or fails based on chat membership, tenant boundaries, and app visibility. It documents resource relationships between chats, messages, threads, and members, plus scope tables for every API method. Shortcut commands are preferred over raw API calls, and schema inspection is required before constructing --data payloads. Use it when users need to message teammates, search chat history, manage group members, download attachments with chunked large-file support, or handle emoji reactions and bookmarks in Lark IM.495kinstalls6Lark Sheetslark-sheets enables agents to create and operate Feishu spreadsheets via CLI. It supports creating workbooks, managing sheets and row/column structure, reading and writing cells with formulas and styles, and building visualizations like charts and pivot tables.495kinstalls7Lark Wikilark-wiki provides CLI access to Feishu knowledge bases (wikis), enabling agents to create and query wiki spaces, manage members, organize document nodes in the hierarchy, and browse space structure.494kinstalls8Lark Whiteboardlark-whiteboard is a larksuite/cli agent skill for generating Feishu/Lark Whiteboard (Board) documents with schema-compliant structure. WBDocument version 2 requires connector nodes in the root nodes array—not nested inside frame children—or schema errors occur. Connector strategy scales by count: draw individually for ≤8 lines, representative cross-layer links for 9–15, and layer-to-layer or simplified grouping beyond 15. Default arrow rules set endArrow to arrow and startArrow to none. Developers reach for lark-whiteboard when visualizing architecture, flows, or embedded board content referenced from lark-doc tokens. Polyline auto-routing recommends specifying node ids and letting the engine infer exit directions.492kinstalls9Lark Tasklark-task is a version 1.0.0 agent skill in larksuite/cli that exposes Lark (Feishu) task management through lark-cli task v2 commands. It supports creating todos, viewing and updating status, splitting subtasks, organizing task lists, assigning collaborators, uploading attachments, and registering task agents. Developers use lark-task when automating standup prep, syncing issue trackers into Lark tasks, or closing loops on assigned work without leaving the terminal. The skill routes keyword searches to +search while scope-only queries such as my open tasks favor +get-my-tasks or +get-related-tasks. Authentication and permission rules live in lark-shared, which agents must read before invoking any task command.492kinstalls10Lark Calendarlark-calendar provides CLI access to Feishu calendar functionality for managing events and schedules. It enables agents to create, read, update and delete calendar events, making it suitable for scheduling automation and calendar integration workflows.491kinstalls11Lark Maillark-mail is a version 1.0.0 agent skill from larksuite/cli that drives Lark (Feishu) email through lark-cli mail v1. It covers drafting and composing messages, sending and replying, forwarding, reading threads, searching inbox content, managing drafts, folders, labels, contacts, attachments, and mail rules. Developers reach for lark-mail when notifying stakeholders from deployment scripts, triaging inbox items in agent sessions, or automating reply drafts without switching to the web client. The skill documents bilingual trigger phrases for compose, inbox, and rule operations and depends on lark-shared for authentication. All mailbox mutations run through structured CLI commands rather than browser automation.490kinstalls12Lark Eventlark-event is a version 1.0.0 agent skill from larksuite/cli that subscribes to Lark (Feishu) real-time events through lark-cli event consume <EventKey>. It streams IM messages, reactions, chat changes, VC meeting ended, Minutes generated, and related push payloads as newline-delimited JSON designed for AI agents running as subprocesses. Developers use lark-event for bot backends, webhook replacements, and bounded event polling with --max-events and --timeout flags plus a stderr ready-marker contract. The skill targets long-running subscribers rather than one-shot REST calls. Authentication and global parameters follow lark-shared SKILL.md prerequisites before starting any consume session.489kinstalls13Lark ContactSearch and retrieve Lark/Feishu user profiles by name, email, or phone. Agents can look up contact information and user identities for team operations.489kinstalls14Lark Workflow Meeting Summarylark-workflow-meeting-summary is a version 1.0.0 workflow skill in larksuite/cli that aggregates Lark (Feishu) meeting minutes across a chosen time window into structured reports. It orchestrates lark-vc commands after agents read lark-shared for auth and lark-vc plus vc-domain-boundaries.md for calendar versus VC responsibilities and minutes versus 妙记 product boundaries. Developers invoke it for weekly meeting digests, sprint review rollups, or retrospective packets without manually opening each meeting record. The workflow encodes standard steps for searching ended meetings, selecting the right artifact type, and extracting summaries and action items. Misreading domain boundaries leads to wrong commands or duplicate data from independent minutes sources.488kinstalls15Lark Workflow Standup Reportlark-workflow-standup-report is a version 1.0.0 workflow skill in larksuite/cli that composes a standup digest from two lark-cli sources for a given date. It calls calendar +agenda with --start and --end for meetings and events, then task +get-my-tasks with --due-end for open todos, merging both into a readable summary. Developers use it for prompts like today schedule and todos, tomorrow meetings, or weekly planning snapshots. The workflow requires user identity with lark-cli auth login --domain calendar,task before execution. Read lark-shared for credential handling. Bot identity is not supported for this combined calendar-and-task report path.487kinstalls16Lark Openapi Explorerlark-openapi-explorer is a lark-cli companion skill for Feishu/Lark integrations. When packaged lark-* skills or registered lark-cli commands cannot satisfy a requirement, the skill walks a three-level markdown doc hierarchy—llms.txt module index, llms-<module>.txt overviews, and per-endpoint <api-doc>.md files—to locate the exact HTTP method, path, parameters, response schema, and error codes. After discovery it executes the call with lark-cli api using --data or --params, following authentication and identity rules from lark-shared. Developers reach for it during bot, workflow, or enterprise automation builds that hit gaps in the CLI surface. Prerequisite: lark-cli must be installed and configured.487kinstalls17Lark Skill Makerlark-skill-maker is a meta-skill in the larksuite/cli repository for packaging Feishu/Lark automation as agent-ready SKILL.md files. It teaches the priority order Shortcut > registered API > lark-cli api raw call, and guides research with lark-cli --help, lark-cli schema <service.resource.method>, and lark-openapi-explorer for unregistered endpoints. A finished skill is one SKILL.md that documents CLI commands, parameters, and workflow steps so Claude, Cursor, or Codex agents can execute Feishu tasks reliably. Developers reach for it after validating an API path and wanting durable, shareable agent instructions. Version 1.0.0; requires lark-cli.486kinstalls18Lark ApprovalQuery and process Lark approval workflows via the CLI - search definitions, create instances, approve, reject, or transfer approvals. The skill routes through lark-cli with schema discovery for form parameters and node configuration.462kinstalls19Lark SlidesGenerates and updates Lark Slides presentations from structured XML via the Lark CLI. Developers use this to automate slide deck creation from agent workflows, supporting themes, images, and per-slide styling.443kinstalls20Lark Attendancelark-attendance is a v1.0.0 agent skill in larksuite/cli that wraps lark-cli attendance commands to fetch the authenticated user's punch and attendance history. It auto-fills required API parameters—employee_type is always employee_no and user_ids is always an empty array—so agents never prompt users for those fields. Developers must read lark-shared/SKILL.md first for authentication and permission handling, matching other lark-cli skills. Reach for lark-attendance when you need punch records, clock-in/out history, or attendance summaries from a coding agent or shell workflow instead of opening the Feishu HR attendance UI or constructing Lark Open API requests manually.440kinstalls21Lark Okrlark-okr is a larksuite/cli agent skill (v1.0.0) for managing Feishu/Lark OKRs from the command line or agent sessions. It covers OKR cycles, Objectives, Key Results, alignment relationships, quantitative metrics, and progress records. Operations run through lark-cli okr with shortcut verbs such as +cycle-list for common tasks. The skill requires lark-cli installed and mandates reading lark-shared/SKILL.md first for authentication and permission handling. Developers reach for lark-okr when they need to list cycles, draft objectives, update key-result progress, or inspect alignment without opening the Lark web UI. Shortcut commands are preferred over raw API flags when available.426kinstalls22Lark MarkdownCreate, view, edit, and compare Markdown files in Lark Drive. Fetch remote files, apply local patches, and overwrite with full content via lark-cli markdown commands.408kinstalls23Lark Appslark-apps is an agent skill from larksuite/cli for querying Lark (Feishu) application access scope without writing HTTP client code. The skill runs `lark-cli apps +access-scope-get --app-id app_xxx` to call GET /apps/{appId}/access-scope and return the server contract verbatim. Responses include scope enums such as Range or All, plus target arrays for users, departments, and chats, and optional apply_config with enabled status and approver lists. The skill requires reading the shared lark-shared skill first as a prerequisite. Developers reach for lark-apps when debugging why a Lark bot or enterprise app cannot reach certain users or departments and they need the live access-scope configuration from the API.338kinstalls24Lark Notelark-note is a v1.0.0 agent skill for the larksuite/cli repository that requires the lark-cli binary and routes only explicit note_id values to Lark Note APIs as an authenticated user. Developers use note +detail --note-id to fetch meeting summary metadata and linked Docx tokens, and can read unified raw transcripts when a vc-node-id is known from docs +fetch --api-version v2. The skill deliberately does not infer note_id from doc_token, titles, backlinks, or calendar search, which keeps agent calls deterministic. Reach for lark-note when an agent must pull Feishu meeting minutes or transcript text after the user or a prior docs fetch supplies a valid note_id.264kinstalls25Lark MeetingUse lark-meeting in a coding agent to apply its workflow on a real project.75.8kinstalls26Good Skillgood-skill is a deliberately small reference skill from the Lark CLI repo that demonstrates how to format an agent skill correctly for catalogs like Prism and skills.sh. Solo and indie builders who package skills for Claude Code, Cursor, or Codex can copy its structure: YAML frontmatter with semantic version, a one-line description, and metadata that declares required binaries such as lark-cli. The markdown body stays short and instructional rather than implementing a product workflow. Install or study it when you are authoring your first skill, auditing repo skills before publish, or fixing ingestion failures caused by missing fields or unclear dependency hints. It does not automate builds or integrations; it encodes the packaging contract so downstream directories can index your capability reliably and agents know what must be on PATH before invocation.77installs27Good Skill Complexgood-skill-complex is a reference agent skill from the Lark CLI ecosystem meant to stress-test SKILL.md frontmatter rather than ship end-user product value. Solo builders and skill authors use it when verifying that installers, catalog ingest, or documentation generators correctly handle long descriptions, nested metadata.requires bins, cliHelp strings, and arbitrary custom fields. It declares dependencies on lark-cli and node and carries version 2.5.1-beta in the manifest. Treat it as a Skill Development specimen: install only when you are debugging skill packaging, Prism tagging pipelines, or Lark CLI behavior. It does not implement a business workflow, MCP bridge, or creative pipeline—its deliverable is a well-formed complex skill document for regression checks.77installs28Good Skill MinimalGood Skill Minimal is a reference agent skill from the Lark CLI ecosystem that exists to prove the smallest publishable SKILL.md shape. Indie builders and skill authors install or copy it when they need a lint-passing stub before layering triggers, tools, and body content. It is not a workflow for shipping features; it is a schema anchor so CLI validators, marketplaces, and local generators can diff real skills against a known-good minimum. The frontmatter carries name, semver-style version, a one-line description, and an empty metadata map, with a trivial markdown body. Use it while bootstrapping custom skills, writing tests for skill packaging, or teaching agents what valid metadata looks like. Once your skill grows beyond the minimum, graduate to fuller templates that include invokeWhen, permissions, and procedural steps.77installs29Cli E2e Testcase WriterCLI E2E Testcase Writer is a Ship-phase agent skill for maintainers of the compiled lark-cli who need trustworthy, domain-scoped end-to-end coverage without rewriting shared harness code. Each invocation focuses on exactly one tests/cli_e2e/{domain} area and delivers two artifacts: scenario test files and an updated coverage.md that tracks what is proven versus intentionally skipped. The workflow forces discovery-first behavior—running --help, group help, and schema subcommands on a real binary—so tests match the live command tree rather than stale docs. Tests must read as full workflows (create plus follow-up read, or mutate plus teardown) with assertions on stored state, not exit codes alone. Shared support in tests/cli_e2e/core.go and the demo folder stay off limits unless you explicitly expand scope. Solo builders shipping a Go CLI fork or internal Lark tool gateway use this skill to grow coverage incrementally while keeping denominators honest via leaf command counts in coverage.md.76installs

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.