Lark Workflow Meeting Summary
lark-cli vc +search --start "<YYYY-MM-DD>" --end "<YYYY-MM-DD>" --format json --page-size 30
Lark Workflow Meeting Summary:
Automate and Structure Your Meeting Notes
What Is This Skill?
Lark Workflow Meeting Summary is a command-line workflow skill designed to automate the summarization, extraction, and structuring of meeting notes within a specified time range from Lark's video conferencing (VC) module. By leveraging the Lark CLI and its underlying APIs, this workflow gathers all meetings within a defined period, retrieves associated meeting minutes (notes), and generates a structured summary report. The skill is intended for users who need to organize, review, or report on meetings efficiently, such as creating weekly summaries or periodic meeting reviews.
This skill integrates several Lark CLI modules (vc, drive) and requires user-level authentication to operate. It is particularly useful for teams that rely on Lark for collaboration and need consistent, automated documentation of their meeting activities.
Skill ID: lark-workflow-meeting-summary
Category: Design
Source: GitHub - Lark CLI Skill
Why Use the Lark Workflow Meeting Summary Skill?
Manual collation of meeting notes is time-consuming and error-prone, especially in organizations where multiple meetings occur daily or weekly. The Lark Workflow Meeting Summary skill addresses these pain points by:
- Automating the search and retrieval of meeting records and notes within a user-defined or inferred time range.
- Generating structured reports for easy review, documentation, or sharing.
- Ensuring consistency in the way meeting information is summarized and reported.
- Reducing repetitive manual work for team leaders, project managers, and administrative staff.
Typical use cases include weekly meeting reviews, preparing periodic reports, and quickly referencing what meetings occurred during a certain period.
How to Use the Lark Workflow Meeting Summary Skill
1. Prerequisites
- User Identity Required: Only individual user authentication is supported.
- Lark CLI Installed: Ensure the
lark-clibinary is available on your system. - Proper Authorization: Must log in to the required domains before executing the workflow.
## For basic querying and note retrieval
lark-cli auth login --domain vc
## For reading note document content and generating new documents
lark-cli auth login --domain vc,drive2. Workflow
Overview
The workflow comprises several logical steps:
- Determine the Time Range
- Query Meetings within the Time Range
- Retrieve Notes Metadata for Each Meeting
- Generate a Structured Summary Report
Step 1:
Determine the Time Range
- The default range is the last 7 days.
- Intelligent inference for common expressions:
- "today": current day
- "this week": Monday to now
- "last week": previous Monday to previous Sunday
- "this month": first day of month to now
Important: Always use system commands (such as date) to format dates, never calculate by hand. Format dates as YYYY-MM-DD or ISO 8601 as required by the CLI.
Step 2:
Query Meeting Records
Use lark-cli vc +search to retrieve meetings in the time range. The command supports pagination and outputs results in JSON format.
lark-cli vc +search --start "<YYYY-MM-DD>" --end "<YYYY-MM-DD>" --format json --page-size 30Key Points:
- Maximum search window: 1 month. For longer periods, split into multiple 1-month queries.
- The
--endargument is inclusive (e.g., for "today," set both--startand--endto today). --page-sizemax is 30. Use thepage_tokenfield to handle pagination and collect all meeting IDs.
Example Pagination Loop:
## Pseudocode
page_token=""
while true; do
output=$(lark-cli vc +search --start "2024-06-01" --end "2024-06-07" --format json --page-size 30 --page-token "$page_token")
extract meeting_ids from output
page_token=$(extract_next_page_token from output)
if [ -z "$page_token" ]; then break; fi
doneStep 3:
Retrieve Meeting Notes Metadata
For each meeting ID, fetch the associated notes document tokens, then use the drive module to batch query metadata for those documents. This step may involve additional commands, depending on your organization's Lark CLI extensions.
Step 4:
Generate the Structured Summary
Aggregate the relevant metadata and notes content to produce a final structured JSON or markdown report, suitable for review or sharing.
When to Use This Skill
- Weekly or Monthly Meeting Reviews: When you need a high-level summary or detailed report of all meetings in a period.
- Project Documentation: To maintain an up-to-date record of project-related meetings and their outcomes.
- Auditing and Compliance: When an accurate, timestamped record of meetings and decisions is required.
- Quick Meeting Lookups: For questions like "What meetings did we have today?" or "Show me all meetings from last week."
Important Notes
- Authentication is Mandatory: The workflow will not function without proper user-level authorization for the relevant Lark domains (
vc,drive). - Date Handling: Always use system utilities for date calculations and formatting. Do not hardcode or guess date formats.
- Pagination: The command only returns up to 30 results per page. Always implement pagination logic to ensure complete data retrieval.
- Time Range Limits: Maximum query window is 1 month per request. For longer periods, split the time frame into chunks.
- User Identity Only: The workflow does not support bot or service account identities.
For further details, refer to the official documentation and the source repository.
By automating the meeting summary process with this skill, you can ensure consistency, save time, and deliver comprehensive documentation across your organization.
More Skills You Might Like
Explore similar skills to enhance your workflow
Microservices Patterns
- Implementing service discovery and load balancing
Churn Prevention
Reduce voluntary and involuntary churn through cancel flow design, save offers, exit surveys, and dunning sequences. Use when designing or optimizing
sheets (v3)
|----------|---------------------------------------------------------|-----------|----------|
Story Readiness
argument-hint: "[story-file-path or 'all' or 'sprint']"
React UI Patterns
1. Never show stale UI - Loading spinners only when actually loading
dbt Transformation Patterns
Production-ready patterns for dbt (data build tool) including model organization, testing strategies, documentation, and incremental processing