Lark CLI Skill: Meeting Summary Workflow

What it is

This CLI skill for Lark (Feishu) automates the process of aggregating meeting minutes across a specified time range and generating structured summary reports. It pulls data from Lark's calendar and meeting APIs, extracts key points, and produces formatted summaries.

The skill targets team leads, project managers, and operations staff who need weekly or monthly meeting summaries without manually reading through individual meeting notes.

The project is actively maintained and suitable for both individual developers and teams looking to integrate it into their existing toolchain. Documentation and community support are available for onboarding.

How it saves time or tokens

Manually reviewing dozens of meeting notes to extract action items and decisions takes hours per week. This skill automates the aggregation, identifies key topics across meetings, and produces a structured report. A week of meetings becomes a single-page summary in seconds.

How to use

1. Install the Lark CLI skill in your Claude Code or AI coding assistant.
2. Configure your Lark API credentials (app_id, app_secret) for calendar and meeting access.
3. Run the skill with a time range: lark-cli meetings summarize --from 2026-04-01 --to 2026-04-15
4. Review the generated summary report with sections for decisions, action items, and key topics.

Example

# Configure Lark API credentials
export LARK_APP_ID='cli_xxxxx'
export LARK_APP_SECRET='xxxxx'

# Generate a weekly meeting summary
lark-cli meetings summarize \
  --from 2026-04-07 \
  --to 2026-04-11 \
  --format markdown \
  --output weekly-summary.md

# Output structure:
# ## Weekly Meeting Summary (Apr 7-11, 2026)
# ### Key Decisions
# - Decision 1 from meeting X
# ### Action Items
# - [ ] Task assigned to Person A (due: Apr 15)
# ### Topics Discussed
# - Topic summary across multiple meetings

Related on TokRepo

• AI Tools for Documentation — Documentation and report generation tools.
• AI Tools for Automation — Workflow automation tools for recurring tasks.

Common pitfalls

• Not granting sufficient API permissions. The skill needs read access to calendar events and meeting records. Missing permissions cause silent failures with empty summaries.
• Setting time ranges that are too broad. A month of meetings produces an unwieldy summary. Weekly summaries are more actionable.
• Expecting the skill to capture unrecorded discussions. The skill can only summarize what is documented in Lark meeting notes. Meetings without notes are excluded from the summary.
• Applying the skill without reading the documentation first. Each skill has specific prerequisites and configuration requirements that affect the quality of results.