lark-workflow-standup-report
Generate Lark Standup Reports
Daily planning is slow when meetings and tasks live in separate Lark apps. This skill combines calendar agenda and unfinished tasks into one standup-ready summary.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "lark-workflow-standup-report" from https://skillstore.io/skills/larksuite-lark-workflow-standup-report.md and its manifest at https://skillstore.io/api/skills/larksuite-lark-workflow-standup-report/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.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-standup-report". Create my standup report for today.
Expected outcome:
A dated report with a meeting table, incomplete task list, conflict reminders, and a short daily summary.
Using "lark-workflow-standup-report". Show tomorrow’s agenda and tasks due by tomorrow.
Expected outcome:
A next-day planning summary with calendar events, pending tasks, overdue markers, and estimated free time.
Using "lark-workflow-standup-report". Review my week for conflicts and unfinished work.
Expected outcome:
A weekly overview that groups schedule items by day and highlights unresolved task load.
Security Audit
SafeThe static findings are false positives caused by Markdown code fences, inline command names, fixed Lark CLI examples, relative documentation links, and multilingual text entropy. No evidence found of hidden execution, arbitrary filesystem traversal, prompt injection, obfuscation, or data exfiltration intent in SKILL.md.
Risk Factors
⚙️ External commands (23)
📁 Filesystem access (4)
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-standup-report/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/larksuite-lark-workflow-standup-report?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/larksuite-lark-workflow-standup-report?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/larksuite-lark-workflow-standup-report/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/larksuite-lark-workflow-standup-report.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-standup-report security audit report (audit version 7) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/larksuite-lark-workflow-standup-report/audits/7BibTeX citation
@techreport{larksuite-larksuite-lark-workflow-standup-report-2026,
author = {larksuite},
title = {lark-workflow-standup-report security audit report (audit version 7)},
institution = {Skillstore},
year = {2026},
number = {7},
url = {https://skillstore.io/skills/larksuite-lark-workflow-standup-report/audits/7},
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-standup-report security audit report (audit version 7)"
version: "1.0.0"
type: report
authors:
- name: "larksuite"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/larksuite-lark-workflow-standup-report/audits/7"
identifiers:
- type: other
value: "skillstore:larksuite-lark-workflow-standup-report:audit:7"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Prepare a personal standup
Review today’s meetings, pending tasks, conflicts, and open time before the workday starts.
Plan tomorrow’s priorities
Generate a next-day agenda and task view before ending the current day.
Check weekly workload
Review upcoming schedule pressure and unfinished tasks for a short planning window.
Try These Prompts
Create my Lark standup report for today. Include meetings, incomplete tasks, conflicts, and free time.
Create my Lark standup report for tomorrow. Use the correct ISO date range and include tasks due by tomorrow.
Summarize my Lark schedule and unfinished tasks for this date. Highlight overdue tasks and meetings that need RSVP action.
Generate a Lark workload report for this week. Group events by day, list incomplete tasks by due date, and call out schedule conflicts.
Best Practices
- Authorize only the calendar and task scopes required for the report.
- Use ISO 8601 date ranges for any day other than today.
- Filter tasks by due date when you need a concise standup report.
Avoid
- Do not omit the incomplete-task filter for pending task summaries.
- Do not use natural language date strings in Lark CLI date arguments.
- Do not treat declined meetings as busy time when checking conflicts.