lark-workflow-meeting-summary▌
larksuite/cli · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md,其中包含认证、权限处理。然后阅读 ../lark-vc/SKILL.md,了解会议纪要相关操作。
会议纪要汇总工作流
CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md,其中包含认证、权限处理。然后阅读 ../lark-vc/SKILL.md,了解会议纪要相关操作。
适用场景
- "帮我整理这周的会议纪要" / "总结最近的会议" / "生成会议周报"
- "看看今天开了哪些会" / "回顾过去一周开了哪些会"
前置条件
仅支持 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: 获取纪要元数据
- 查询会议关联的纪要信息
lark-cli vc +notes --meeting-ids "id1,id2,...,idN"
- 根据上一步搜集到的
meeting-id查询会议纪要。 - 单次最多查询 50 个纪要信息,超过 50 个需分批调用。
- 部分会议返回
no notes available,在最终输出中标注"无纪要" - 记录每个会议的
note_doc_token(纪要文档 Token)和verbatim_doc_token(逐字稿文档 Token)
- 获取纪要文档和逐字稿文档链接
# 学习命令使用方式
lark-cli schema drive.metas.batch_query
# 批量获取纪要文档与逐字稿链接: 一次最多查询 10 个文档
lark-cli drive metas batch_query --data '{"request_docs": [{"doc_type": "docx", "doc_token": "<doc_token>"}], "with_url": true}'
Step 4: 整理纪要报告
根据时间跨度选择输出格式:
- 单日汇总("今天"/"昨天"):用"今日会议概览"标题,逐会议列出会议时间、主题、纪要链接、逐字稿链接。
- 多日/周报("这周"/"过去 7 天"等):用"会议纪要周报"标题,含概览统计、逐会议详情。
Step 5: 生成文档(可选,用户要求时)
阅读 ../lark-doc/SKILL.md 学习云文档技能。
lark-cli docs +create --title "会议纪要汇总 (<start> - <end>)" --markdown "<内容>"
# 或追加到已有文档
lark-cli docs +update --doc "<url_or_token>" --mode append --markdown "<内容>"
参考
- lark-shared — 认证、权限(必读)
- lark-vc —
+search、+notes详细用法 - lark-doc —
+fetch、+create、+update详细用法
How to use lark-workflow-meeting-summary on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add lark-workflow-meeting-summary
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches lark-workflow-meeting-summary from GitHub repository larksuite/cli and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate lark-workflow-meeting-summary. Access the skill through slash commands (e.g., /lark-workflow-meeting-summary) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★44 reviews- ★★★★★Pratham Ware· Dec 28, 2024
We added lark-workflow-meeting-summary from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Benjamin Martin· Dec 4, 2024
lark-workflow-meeting-summary is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Omar Martin· Dec 4, 2024
Solid pick for teams standardizing on skills: lark-workflow-meeting-summary is focused, and the summary matches what you get after install.
- ★★★★★Kwame Abbas· Nov 23, 2024
Solid pick for teams standardizing on skills: lark-workflow-meeting-summary is focused, and the summary matches what you get after install.
- ★★★★★Sophia Verma· Nov 23, 2024
lark-workflow-meeting-summary is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Sakshi Patil· Nov 19, 2024
lark-workflow-meeting-summary fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Benjamin Kapoor· Oct 14, 2024
We added lark-workflow-meeting-summary from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★William Johnson· Oct 14, 2024
lark-workflow-meeting-summary fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Chaitanya Patil· Oct 10, 2024
lark-workflow-meeting-summary is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Oshnikdeep· Sep 21, 2024
Useful defaults in lark-workflow-meeting-summary — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 44