Skip to content

Guide · Agent skill

How to use the Lark IM agent skill (lark-im) with lark-cli

Updated · written with AI from the project's own documentation and checked against our catalogue data

The lark-im skill is a set of instructions that teaches an AI agent how to work with Lark/Feishu instant messaging through the lark-cli command-line tool. Once it is installed, you can ask the agent to send or reply to messages, search chat history, download files from chats, look up group members, and build interactive cards. This guide explains what agent skills are, how to install lark-im, how to phrase requests, and what safety points to check first.

Lark Instant Messaginglarksuite/cli · MIT

Quick start

  1. 1Install lark-cli. Install and authorise the lark-cli command-line tool, which the skill requires. Confirm it works by running lark-cli im --help.
  2. 2Get the authorisation guide. Obtain the separate lark-shared guide that covers authentication and permissions, since it is not included in these files.
  3. 3Download the ZIP. Download the lark-im skill ZIP from this page and unzip it.
  4. 4Place the skill folder. Move the folder into ~/.claude/skills/ for personal use, or into .claude/skills/ in a project. Alternatively, upload it in the Claude apps under Settings → Capabilities → Skills.
  5. 5Make a natural request. Ask the agent in plain language for a Lark/Feishu messaging task, naming the chat, person and content.
  6. 6Review before sending. Check any drafted message or card before the agent sends it, because sent messages cannot be recalled.

What is an agent skill, and what does lark-im let the agent do?

An agent skill is a folder of instructions and supporting files that an AI agent reads when a task matches the skill's description. The lark-im skill covers Lark/Feishu instant messaging. It tells the agent how to use lark-cli to handle messages and chats.

According to the skill, the agent can send and reply to messages, search chat history, download images and files from chats, manage group members, create group or topic chats, manage emoji reactions, and send urgent alerts (in-app, SMS or phone). It can also build and handle interactive cards, including listening for button callbacks (card.action.trigger). The skill additionally covers feed pinning, flags and tag data.

Install the lark-im skill

Download the lark-im ZIP from this page and unzip it. To make it available to all your projects, place the unzipped folder in ~/.claude/skills/. To limit it to one project, place it in that project's .claude/skills/ folder.

If you use the Claude apps instead, upload the skill under Settings → Capabilities → Skills.

  • Personal install: ~/.claude/skills/
  • Project install: .claude/skills/ inside your project
  • Claude apps: Settings → Capabilities → Skills

Set up lark-cli and authorisation before you start

The skill depends on the lark-cli command-line tool (the required binary is lark-cli). The skill itself says that lark-cli must be installed and that you need Lark/Feishu app credentials and user or bot authorisation. Authentication and permission handling are described in a separate lark-shared guide, which is not included in these files, so you will need to obtain it separately.

To see the commands the skill can use, the skill points to lark-cli im --help.

  • Install and authorise lark-cli first; the skill will not work without it.
  • Make sure your app has the Lark IM scopes you need, such as message reaction read for enrichment features.
lark-cli im --help

Trigger the skill with natural requests

You do not need to name the skill. Ask for a Lark/Feishu messaging task in plain language, and the agent should pick the skill when your request matches its description, such as sending a message, searching chat records, downloading a file from a chat, viewing group members, or handling a card callback.

Be specific about the chat, person or group, and the content. The skill notes that the agent should confirm with you before sending anything real, so state clearly whether you want a draft or an actual send.

  • Send a message: "Send a message to the Project Alpha group saying the build is ready."
  • Search history: "Search the Lark chat for messages about the Q3 budget from last week."
  • Download a file: "Download the spreadsheet attached in the design group chat."
  • List members: "Show me the members of the support team group."

Understand identity: user or bot

The skill distinguishes two identities. With --as user, calls run as the authorised person and depend on that person's access to the chat. With --as bot, calls run as the app bot and depend on the bot's membership and app permissions. The same action can succeed with one identity and fail with the other, so if a request fails, check which identity was used.

Use cards and safety features carefully

For interactive cards, the skill requires the agent to follow its card-creation workflow rather than writing card JSON by hand. Cards can have buttons, forms and charts, and button clicks can be handled through callbacks. Card messages are not yet compacted in event subscriptions, so raw event data is returned instead.

The skill runs scripts and uses the network. Audio messages via --audio accept only Opus files (.opus or .ogg); for mp3 or wav, convert to Opus first or send the file with --file.

  • Review any message the agent drafts before it is sent to colleagues or groups, because sent messages cannot be undone.
  • Use --concise for compact output only when you ask for a smaller result.
  • Use --no-reactions if you do not want reaction data attached to message pulls.
  • Opt in to --download-resources only when you need attachments saved to ./lark-im-resources/.

What people use it for

  • Send status updates to a team group after a build or release.
  • Search a chat for a decision or link made in a past conversation.
  • Download a file shared in a chat to a local folder for review.
  • Look up members of a group before adding someone or checking who has access.
  • Build an interactive card with buttons or a form and handle the button callbacks.

Frequently asked questions

Is the lark-im skill free to use?

The source material does not state pricing or licence terms beyond the licence listed for this item, which is MIT. Lark/Feishu accounts and the lark-cli tool may have their own requirements, which are not covered in these files.

What do I need to install lark-im?

You need the lark-cli command-line tool, Lark/Feishu app credentials, and user or bot authorisation set up through the separate lark-shared guide. You also need the lark-im folder placed in ~/.claude/skills/ or a project's .claude/skills/ folder.

Does lark-im work with Feishu as well as Lark?

The skill's description is written for Feishu/Lark instant messaging, and it works through the Lark IM APIs. It only talks to that platform, so it will not help with other messaging services.

Why does the agent say it lacks permission?

Permissions depend on the identity used. A user identity needs access to the chat or message, and a bot identity depends on its membership, app visibility and scopes. Check your authorisation and the app's scopes, such as message reaction read for enrichment features.

Can the agent send messages without my approval?

The skill can send real messages, and those cannot be undone. Review drafts before sending, especially to colleagues or groups.

How is lark-im different from using lark-cli directly?

lark-cli is the tool that performs the actions. The skill adds instructions that tell the agent how to use it for IM tasks, including card workflows, identity rules and output options.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

lark-im suits teams that run daily work in Lark/Feishu and developers building bots or automations that post cards and handle callbacks. It is not suited to people who do not use Lark/Feishu, or to anyone who wants messages sent without review. Set up lark-cli and the separate authorisation guide before you rely on it.

Download the skill