lark

Automate Lark document, chat, and Base/Bitable interactions via a shell-based API client.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/popodidi/harvis --skill lark-popodidi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark
Source: https://github.com/popodidi/harvis/tree/main/projects/truenorth/skills/lark
Command: npx skills add https://github.com/popodidi/harvis --skill lark-popodidi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, jq, git, bc, and includes scripts (resource) components.

What problem does it solve?

Organizations using Lark/Feishu often work with documents, chats, and directory data across multiple apps. This skill provides a unified, scriptable interface to read and edit documents, send messages, look up users, and query Base/Bitable data from Lark.

Core Features & Use Cases

  • Read and edit Lark documents and extract content for downstream processing.
  • Send messages to chats and manage contacts within Lark.
  • Look up user information and query Lark Base/Bitable data for automation workflows.
  • Use cases: automatically notify teams, fetch user details by email, or update wiki notes from your automation pipeline.

Quick Start

Source the authentication script and obtain a token with get_lark_token. Retrieve a document's blocks with get_document_blocks or get_all_document_blocks. Use the provided MCP tools or the lark_api helper to perform actions such as reading content, sending messages, or looking up users.

Frequently Asked Questions about lark

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate sending Lark messages and reading documents from my team workflows?

You can automate sending Lark messages and reading documents by using a scriptable shell-based API client that manages tokens and interacts with Lark Base data, chats, and docs. It supports looking up users and extracting document content for pipelines.

Can I use curl and jq to query Lark Base data and look up users by email?

Yes, curl and jq are required dependencies to query Lark Base data and look up users by email. The skill uses these shell tools to handle API requests, parse JSON responses, and manage local token caching with retry logic.

What is the best way to manage Feishu authentication tokens for API automation?

The best way to manage Feishu authentication tokens for API automation is through a dedicated script that handles token retrieval and local token caching with retry logic. You source the authentication script and call get_lark_token to obtain a valid token.

How do I extract document blocks from Lark docs for downstream processing?

To extract document blocks from Lark docs for downstream processing, you use the get_document_blocks or get_all_document_blocks functions. These retrieve the structural content of your Lark documents, allowing you to read and edit the information within your automation pipeline.

Does Lark API automation work with Bitable data for team notifications?

Yes, Lark API automation works with Bitable data for team notifications by querying Lark Base records and sending messages to chats. You can integrate these actions to automatically notify teams or update wiki notes based on your Bitable data.

Why do I need git and bc to run Lark integration scripts?

Git and bc are required dependencies to run Lark integration scripts because git likely handles script versioning or updates, while bc provides shell-based calculation logic needed for the API client operations. They ensure the local token caching and retry logic function correctly.