Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
open.feishu.cn avatar

Lark Workflow Meeting Summary

  • 492k installs
  • open.feishu.cn

lark-workflow-meeting-summary is a Claude workflow skill that aggregates Feishu/Lark meeting minutes over a time range into a structured report by chaining vc and drive commands.

About

This workflow aggregates Feishu/Lark meeting minutes over a chosen time range and produces a structured report. It chains vc +search to find meetings, vc +notes to get minutes tokens, and drive metas to fetch document links, then formats a daily overview or weekly digest. A developer uses it to compile a meeting recap or weekly meeting report, optionally writing it to a Lark document.

  • Orchestrates vc +search -> vc +notes -> drive metas to aggregate meeting minutes over a time range
  • Produces a structured report (daily overview or weekly digest) with minutes and transcript links
  • Optionally generates a Feishu doc of the aggregated meeting summary

Lark Workflow Meeting Summary by the numbers

  • 492,459 all-time installs (skills.sh)
  • +41,440 installs in the week ending Jul 29, 2026 (Skillselion tracking)
  • Ranked #4 of 2,726 Automation & Workflows skills by installs in the Skillselion catalog
  • Data as of Jul 29, 2026 (Skillselion catalog sync)
At a glance

lark-workflow-meeting-summary capabilities & compatibility

Free skill; requires lark-cli auth (vc, optionally drive).

Capabilities
meeting aggregation · report generation · minutes retrieval · workflow orchestration
Use cases
orchestration · transcription
Runs
Runs locally
Pricing
Free
From the docs

What lark-workflow-meeting-summary says it does

会议纪要整理工作流:汇总指定时间范围内的会议纪要并生成结构化报告。
SKILL.md
默认**过去 7 天**。
SKILL.md
npx skills add https://github.com/open.feishu.cn --skill lark-workflow-meeting-summary

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs492k
Repositoryopen.feishu.cn

What it does

Aggregate Feishu/Lark meeting minutes over a time range into a structured recap report.

Who is it for?

Compiling a recap or weekly report of Feishu/Lark meetings over a date range.

Skip if: One-off retrieval of a single meeting's minutes (use lark-vc directly).

When should I use this skill?

A user asks to organize this week's meeting minutes, summarize recent meetings, or generate a meeting weekly report.

By the numbers

  • 5-step workflow (Step 1 through Step 5)
  • vc +search page-size max 30
  • vc +notes max 50 meeting-ids per call

Files

SKILL.mdMarkdownGitHub ↗

会议纪要汇总工作流

CRITICAL — 开始前 MUST 先用 Read 工具读取 [`../lark-shared/SKILL.md`](../lark-shared/SKILL.md),其中包含认证、权限处理。然后阅读 `../lark-vc/SKILL.md`,了解会议纪要相关操作。

CRITICAL — 开始前 MUST 先用 Read 工具读取 [`../lark-vc/references/vc-domain-boundaries.md`](../lark-vc/references/vc-domain-boundaries.md),不读将导致命令使用、会议产物决策、领域边界职责判断错误:

1. 了解日历 & VC、会议产物 & 文档的关联关系和职责划分
2. 了解会议产物(妙记和纪要)之间的关联关系,例如:妙记和纪要产生条件相互独立
3. 了解不同会议产物的组成部分,以便根据需求决策使用哪种产物的数据
4. 了解会议总结、分析和信息提取的标准流程

适用场景

  • "帮我整理这周的会议纪要" / "总结最近的会议" / "生成会议周报"
  • "看看今天开了哪些会" / "回顾过去一周开了哪些会"

前置条件

仅支持 user 身份。执行前确保已授权:

lark-cli auth login --domain vc        # 基础(查询+纪要)
lark-cli auth login --domain vc,drive   # 含读取纪要文档正文、生成文档

工作流

{时间范围} ─► vc +search ──► 会议列表 (meeting_ids)
                   │
                   ▼
               vc +notes ──► 纪要文档 tokens
                   │
                   ▼
               drive metas batch_query 纪要元数据
                   │
                   ▼
               结构化报告

Step 1: 确定时间范围

默认过去 7 天。推断规则:"今天"→当天,"这周"→本周一~now,"上周"→上周一~上周日,"这个月"→1日~now。

注意:日期转换必须调用系统命令(如 date),不要心算。时间范围参数需根据 CLI 实际要求格式化(通常为 YYYY-MM-DD 或 ISO 8601)。

Step 2: 查询会议记录

# page-size 最大为 30
lark-cli vc +search --start "<YYYY-MM-DD>" --end "<YYYY-MM-DD>" --format json --page-size 30
  • 时间范围拆分:搜索的时间范围最大为 1 个月。搜索更长时间范围的会议,需要拆分为多次时间范围为一个月查询。
  • --end包含当天的日期(即查"今天"时 start 和 end 都填今天)
  • --format json 输出 JSON 格式,你更佳擅长解析 JSON 数据。
  • --page-size 30 每页最多 30 条。
  • page_token 时必须继续翻页,收集所有 id 字段(meeting-id)

Step 3: 获取纪要元数据

1. 查询会议关联的纪要信息

lark-cli vc +notes --meeting-ids "id1,id2,...,idN"   
  • 根据上一步搜集到的 meeting-id 查询会议纪要。
  • 单次最多查询 50 个纪要信息,超过 50 个需分批调用。
  • 部分会议返回 no notes available,在最终输出中标注"无纪要"
  • 记录每个会议的 note_id(纪要 ID)、note_display_type(展示类型:unknown / normal / unified)、note_doc_token(纪要文档 Token)和 verbatim_doc_token(逐字稿文档 Token)
逐字稿路由按 `note_display_type` 决定(详见 vc-domain-boundaries.md 的 Note 域):
- normal:逐字稿是独立文档,链接/正文走 verbatim_doc_token
- unified:逐字稿不是独立文档,没有可分享的逐字稿文档链接;需要逐字稿内容时用 note +transcript --note-id <note_id>lark-note)拉取到本地,报告中标注"unified 纪要"即可。

2. 获取纪要文档和逐字稿文档链接

# 学习命令使用方式
lark-cli schema drive.metas.batch_query

# 批量获取纪要文档与逐字稿链接: 一次最多查询 10 个文档
# 仅对 note_doc_token 与 normal 纪要的 verbatim_doc_token 查询链接
lark-cli drive metas batch_query --data '{"request_docs": [{"doc_type": "docx", "doc_token": "<doc_token>"}], "with_url": true}'

Step 4: 整理纪要报告

根据时间跨度选择输出格式:

  • 单日汇总("今天"/"昨天"):用"今日会议概览"标题,逐会议列出会议时间、主题、纪要链接、逐字稿链接(unified 纪要无逐字稿链接,标注"unified 纪要,逐字稿需 note +transcript 拉取")。
  • 多日/周报("这周"/"过去 7 天"等):用"会议纪要周报"标题,含概览统计、逐会议详情。

Step 5: 生成文档(可选,用户要求时)

阅读 `../lark-doc/SKILL.md` 学习云文档技能。

lark-cli docs +create --api-version v2 --doc-format markdown --content $'<title>会议纪要汇总 (<start> - <end>)</title>\n<内容>'
# 或追加到已有文档
lark-cli docs +update --api-version v2 --doc "<url_or_token>" --command append --doc-format markdown --content $'<内容>'

参考

  • lark-shared — 认证、权限(必读)
  • lark-vc+search+notes 详细用法
  • lark-notenote +detailnote +transcript(unified 纪要逐字稿)
  • lark-doc+fetch+create+update 详细用法

Related skills

Forks & variants (1)

Lark Workflow Meeting Summary has 1 known copy in the catalog totaling 386k installs. They canonicalize to this original listing.

FAQ

What is the default time range?

The past 7 days, unless the user specifies today, this week, last week or this month.

Can it produce a document?

Yes; Step 5 optionally creates or appends a Feishu doc via lark-doc when the user asks.

This week in AI coding

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

unsubscribe anytime.