Guide · Agent skill
How to use the Lark Meeting Summary Workflow agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The Lark Meeting Summary Workflow is an agent skill, a folder of instructions that a Claude agent loads when your request matches its purpose. This one, named lark-workflow-meeting-summary, tells the agent how to find the meetings in a date range, collect the AI meeting notes and transcripts attached to them, and assemble a structured report. This guide covers what it does, how to install it, how to trigger it, what it needs, and the safety points to check before you use it.
Lark Meeting Summary Workflowlarksuite/cli · MIT Download the skill Quick start
- 1Install lark-cli and sign in. Install the lark-cli tool so it is on your PATH, then run lark-cli auth login with the vc domain. Add drive and minutes if you need document bodies or the minutes fallback.
- 2Install the skill files. Download the ZIP from this page, unzip it, and place the folder in ~/.claude/skills/ or a project's .claude/skills/ folder. Or upload the ZIP under Settings → Capabilities → Skills in the Claude apps.
- 3Make sure companion skills are present. Confirm that lark-shared, lark-meeting and, for document output, lark-doc are available alongside this skill.
- 4Ask for a summary with a time range. Say something like "summarize this week's meetings". The agent picks the date range, defaulting to the past 7 days if you give none.
- 5Review the report. Check the list of meetings, note links and transcript links. Meetings marked unified have no separate transcript link.
- 6Optionally write a document. Ask the agent to create a document or append to an existing one. Confirm the destination is appropriate for the meeting content first.
What the skill makes the agent do
When you ask for a summary of recent meetings, the agent uses the Lark command-line tool (lark-cli) to search your meetings in a date range. For each meeting it finds the note ID and document tokens, looks up the note and transcript links, and then writes a report listing each meeting with links to its notes.
The skill works in two output styles. For a single day, it produces a "today's meeting overview" that lists each meeting's time, topic, note link and transcript link. For multi-day requests such as "this week" or "past 7 days", it produces a "meeting notes weekly report" with summary statistics and per-meeting details. It can also write the report into a new Lark document, or append it to an existing one, but only when you ask.
Install the skill: download, unzip and place it
Download the ZIP of the skill from this page and unzip it. The skill is a single SKILL.md file. Put the folder in one of these locations:
- Personal skills: ~/.claude/skills/ (available across your projects)
- Project skills: the .claude/skills/ folder inside a specific project
- Claude apps: open Settings → Capabilities → Skills and upload the ZIP
Install the required tools and permissions
The skill depends on the lark-cli command-line tool, which must be installed and on your PATH. It also reads two companion skills, lark-shared and lark-meeting, and uses lark-doc when it creates a document. Install those alongside this skill.
Then authorize your Lark user account. The skill supports user identity only. Choose the scope that matches what you need:
- Basic search and notes: lark-cli auth login --domain vc
- Also read note document bodies and create documents: lark-cli auth login --domain vc,drive
- Also use the minutes fallback when a meeting has no note ID: lark-cli auth login --domain vc,drive,minutes
lark-cli auth login --domain vc
lark-cli auth login --domain vc,drive
lark-cli auth login --domain vc,drive,minutesTrigger the skill with natural requests
You do not need a special command. Ask in plain language, and the agent will load the skill when your request matches. The skill's own examples include these phrasings:
- Organize this week's meeting notes
- Summarize recent meetings
- Generate a meeting weekly report
- Show which meetings I had today
- Review the meetings from the past week
How the agent builds the report
The agent first sets the date range. By default it covers the past 7 days, and it reads phrases like "this week" (Monday to now), "last week" (last Monday to last Sunday) and "this month" (the 1st to now). The skill requires the agent to get dates from a system command such as date rather than calculating them in its head.
Search covers at most one month per call, so longer ranges are split into one-month windows. The agent then looks up each meeting's notes, follows any page tokens to collect every result, and reads the note and transcript document links. Meetings without a note ID or with a no notes available error are checked for a minute token before being marked as having no notes.
- Search limit: up to 30 results per page, one month per window
- Detail lookups: up to 50 meeting IDs per call, batched above that
- Document link lookups: up to 10 documents per call
Safety, permissions and what gets shared
The skill runs scripts and uses the network, since every step calls lark-cli against Lark services. It works only with the permissions your own Lark account already has. If a transcript returns a No read permission error (code 2091005), the skill tells you first and asks before requesting access. Access requests need the document owner to approve in the Lark client before a retry works.
Transcript content is pulled into the agent's context, and the report can be written to a shared document. Check the destination before you create or append a document, especially for confidential meetings.
- Read-only by default: documents are created or updated only when you ask
- Permission requests are made only with your agreement
- Transcript text passes through the agent, so review where the report goes
What people use it for
- A team lead gets a weekly digest of all meetings held in the past seven days, with links to each set of notes.
- A person who attends many meetings reviews the past month to see which discussions took place and where the notes are.
- A manager asks for today's meeting overview to catch up on what was discussed before an afternoon review.
- A user saves the weekly report into a new Lark document so the team can read it in one place.
Frequently asked questions
How do I install the lark meeting summary agent skill?
Download the ZIP from this page and unzip it. Put the folder in ~/.claude/skills/ for personal use, or in a project's .claude/skills/ folder. In the Claude apps you can instead upload the ZIP under Settings → Capabilities → Skills.
What do I need before the skill works?
You need the lark-cli command-line tool installed and on your PATH, a Lark account, and authorization through lark-cli auth login with the vc domain. The companion skills lark-shared and lark-meeting are also required, and lark-doc is needed to create documents.
Is the skill free to use?
The source material for this skill is published under the MIT licence. The source does not state any price, so check the licence and the lark-cli tool's own terms for details.
Does it work with Google Calendar or Zoom?
No. The skill depends entirely on Lark data and the lark-cli tool, so it will not work with Google Calendar or Zoom meetings.
Why does the skill say a meeting has no notes when it may have a recording?
It only marks a meeting as having no notes after checking for both a note ID and a minute token. If a minute token exists, it follows the minutes path to fetch the transcript, because the AI notes and minutes are separate artifacts.
What should I do if I get a No read permission error?
The skill will tell you that access is missing and ask for your agreement before requesting it. The document owner must approve the request in the Lark client, and then you can retry.
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
This skill suits managers, team leads and frequent meeting attendees who already use Lark and lark-cli and want a regular digest of past meetings with links to their notes. It is a poor fit if you do not use Lark or Feishu, or if you need to summarize meetings across other platforms. Because transcripts pass through the agent and reports can be shared, check permissions before using it on confidential meetings.
Download the skill