lark-workflow-meeting-summary
Summarize Lark Meetings into Clear Reports
Reviewing many meeting records takes time and can hide important details. This skill gathers Lark meeting notes and creates a structured daily or weekly report.
This skill is part of a pack
Install the whole pack to get every skill the task needs, in one command.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "lark-workflow-meeting-summary" from https://skillstore.io/skills/larksuite-lark-workflow-meeting-summary.md and its manifest at https://skillstore.io/api/skills/larksuite-lark-workflow-meeting-summary/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "lark-workflow-meeting-summary". Summarize my meetings from today.
Expected outcome:
Today Meeting Overview
Three meetings found. Product Planning has normal notes and a transcript link. Operations Review has unified notes. Hiring Sync has no notes.
Using "lark-workflow-meeting-summary". Create a meeting report for the past seven days.
Expected outcome:
- Weekly Meeting Report: 12 meetings across five days.
- Nine meetings include notes, two use unified notes, and one has no notes.
- Each meeting entry includes its time, topic, note status, and available document links.
Using "lark-workflow-meeting-summary". Append this month's meeting summary to my team document.
Expected outcome:
The monthly meeting summary was organized by day and appended to the requested Lark document. Meetings without notes were clearly labeled.
Security Audit
High RiskAll 45 static findings are false positives caused by Markdown syntax, fixed documentation links, expected Lark CLI examples, and multilingual text entropy. However, document creation templates place generated content inside shell-quoted arguments, creating a command injection risk when content is inserted without robust escaping.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (30)
📁 Filesystem access (9)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/larksuite-lark-workflow-meeting-summary/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/larksuite-lark-workflow-meeting-summary?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/larksuite-lark-workflow-meeting-summary?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/larksuite-lark-workflow-meeting-summary/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/larksuite-lark-workflow-meeting-summary.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
larksuite. (2026). lark-workflow-meeting-summary security audit report (audit version 6) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/larksuite-lark-workflow-meeting-summary/audits/6BibTeX citation
@techreport{larksuite-larksuite-lark-workflow-meeting-summary-2026,
author = {larksuite},
title = {lark-workflow-meeting-summary security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/larksuite-lark-workflow-meeting-summary/audits/6},
note = {Author version 1.0.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "lark-workflow-meeting-summary security audit report (audit version 6)"
version: "1.0.0"
type: report
authors:
- name: "larksuite"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/larksuite-lark-workflow-meeting-summary/audits/6"
identifiers:
- type: other
value: "skillstore:larksuite-lark-workflow-meeting-summary:audit:6"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Prepare a Weekly Team Review
Collect the past week of meetings and organize topics, note links, and transcript availability.
Track Project Discussions
Review meetings from a project period and identify which sessions have usable notes.
Create a Daily Meeting Brief
Produce a concise overview of today's meetings with available notes and document links.
Try These Prompts
Summarize my Lark meetings from today. List each meeting time, topic, note link, and transcript availability.
Create a meeting report for the past seven days. Include totals, meeting details, note links, and missing-note labels.
Review my Lark meetings from <start date> through <end date>. Group them by day and distinguish normal, unified, and missing notes.
Build a weekly meeting report for <date range>. Include complete pagination and transcript routing. Append the final report to <Lark document>.
Best Practices
- Confirm the intended date range before processing a large meeting history.
- Authorize only the Lark domains required for the requested output.
- Review sensitive meeting details before publishing the report to a shared document.
Avoid
- Do not assume every meeting has notes or a separate transcript document.
- Do not request more than one month in a single meeting search.
- Do not place untrusted meeting content directly inside shell command strings.