How to use the Feishu Meeting & Minutes agent skill (lark-meeting)

What the skill lets the agent do

The skill covers two areas. The first is past meetings: finding a meeting, then retrieving its AI notes (智能纪要, called Note), its recording-based minutes (妙记, called Minutes), summaries, to-dos, chapters, keywords and transcripts (逐字稿). It can also search minutes, upload local audio or video to generate minutes, download the original media, and edit titles, summaries, to-dos or speaker names.

The second area is live meetings. The agent can list meetings that are in progress, read in-meeting events such as speech, chat and shared documents, take a screenshot, and send chat text or emoji. A Feishu bot can also join a meeting, invite people, or end a meeting, but those actions are separate and should be explicitly authorised.

The skill also explains how the identifiers relate. A meeting_id, a meeting_no (the 9-digit number people type to join), an event_id, a note_id and a minute_token are different things and cannot be swapped for one another. The skill routes each task to the right commands. Scheduling meetings, free/busy checks and room management are handled by a separate calendar skill, lark-calendar.

Install the skill

Download the ZIP for this skill from this page and unzip it. You can install it in one of two ways. For a personal setup, unzip it into ~/.claude/skills/. For a single project, unzip it into the project's .claude/skills/ folder. Alternatively, in the Claude apps, open Settings, go to Capabilities, then Skills, and upload the ZIP.

The skill needs the lark-cli command-line tool on your machine, because the agent runs its commands. Your Feishu/Lark account must authorise access, and the account or app needs the scopes for VC, Minutes, Note and Drive. Without lark-cli installed, nothing in this skill works.

• Unzipped folder should contain SKILL.md at its top level, next to a references folder.
• The skill's metadata lists lark-cli as its required binary.
• Check the tool is available by running lark-cli vc --help, lark-cli minutes --help and lark-cli note --help, which the skill itself lists as its help commands.

How to trigger the skill with natural requests

You do not need a special command. Describe what you want in plain language and mention the meeting, minutes or transcript. Good triggers include asking for the summary of a named meeting, asking for the action items from last week's client call, or pasting a minutes URL and asking for its transcript. If you have a minute_token, a note_id or a minutes link, include it, because the skill uses these to avoid guessing.

For a live meeting, say so: ask what has been said in the meeting that is running now, or ask the agent to post a message in it. The skill will look up the active meeting first, and if more than one is running it should ask you which one you mean.

• Summarise the meeting on 12 March with Acme and list the decisions and owners.
• Find the minutes titled Q2 planning and show me the to-do items.
• Download the recording for this minutes link: a minute_token is in the URL after /minutes/.
• What has been shared in the meeting that is running right now?

Identity: user or bot

The skill uses a source identity, either user (you) or bot (the Feishu app's bot). If the context already has an identity, the agent keeps it. If you name one, it uses that. Otherwise it uses bot only when the action clearly needs the app bot, and user in other cases. The agent should not silently switch identity. Permissions differ between the two, so a result found as one identity may be empty or missing when checked as the other.

When the agent reports results it describes them as user or app identity, not the internal words user and bot.

Examples of commands the skill uses

These are examples from the skill's reference. Replace the placeholder values with your own identifiers. The minute token in the examples is a sample string.

Use the first command to see meetings you are currently in. Use the detail command to fetch summary, to-do and transcript for a minutes token. Use the download command to save the original media to a folder.

• Active meetings for you: lark-cli vc +meeting-list-active --as user
• Minutes details with summary and to-dos: lark-cli minutes +detail --as <source_identity> --minute-tokens obcxxx --summary --todo
• Download minutes media to a folder: lark-cli minutes +download --minute-tokens obcnxxxxxxxxxxxxxxxxxxxx --output-dir ./downloads
• Get a download link valid for one day without downloading: add --url-only to the download command

Safety: scripts, network and bot actions

This skill runs scripts and uses the network, because lark-cli calls Feishu's services on your behalf. Only install it from a source you trust, and keep the Feishu permissions you grant to the minimum needed.

Some actions change things. Applying for minutes permission, editing minutes, uploading media and replacing speaker names are write operations. Asking a bot to join, invite people, send chat messages or end a meeting affects other people in a live meeting. The skill says these should only run when you have clearly asked for them. Be careful with sensitive meetings, and do not let an agent join or speak in them unless you have explicitly approved that.

• Use --dry-run where a command supports it to preview the API call before it runs. The apply-permission reference documents this flag.
• A bot-applied permission grants access to the app, not to the requesting user.
• An empty result from the bot identity does not mean nobody is in the meeting.

Tips for better results

Give the agent a precise identifier when you have one. A meeting_id is a long numeric string and is not the 9-digit meeting number. A minute_token is a lowercase letter and digit string taken from the minutes URL. Do not pass one kind of ID where another is expected.

Remember that a meeting may have an AI note, a minutes record, both, or neither. If a note does not show a minutes record, that does not mean there is none, and the reverse also holds.

• Ask for specific artifacts, such as summary or to-do, so the agent requests only what you need.
• For a scheduling question, use a calendar tool instead, because this skill does not book meetings or check rooms.
• If the agent reports a token, identity or scope error, the skill tells it to load the shared authentication guidance, fix the problem and retry.