lark-workflow-standup-report

Schedule and To-Do Summary Workflow

CRITICAL, Before starting, you MUST use the Read tool to read ../lark-shared/SKILL.md, which contains information on authentication and permission handling.

Applicable Scenarios

• "What is on my schedule today?" / "Today's schedule and to-dos"
• "What meetings do I have tomorrow?" / "Tomorrow's schedule and pending tasks"
• "Help me see what I need to do today" / "Morning briefing summary"
• "Work start summary" / "standup report"
• "What else is scheduled for this week?"

Prerequisites

Only user identity is supported. Ensure authorization is granted before execution:

lark-cli auth login --domain calendar,task

Workflow

{date} ─┬─► calendar +agenda [--start/--end]              ──► Schedule list (meetings/events)
        └─► task +get-my-tasks --complete=false [--due-end] ──► Pending to-do list
                    │
                    ▼
              AI Summary (time conversion + conflict detection + sorting) ──► Summary

Step 1: Get Schedule

# Today (default, no extra parameters needed)
lark-cli calendar +agenda

# Specify date range (must use ISO 8601 format, natural language like "tomorrow" is not supported)
lark-cli calendar +agenda --start "2026-03-26T00:00:00+08:00" --end "2026-03-26T23:59:59+08:00"

Note: --start / --end only support ISO 8601 format (e.g., 2026-01-01 or 2026-01-01T15:04:05+08:00) and Unix timestamps. They do not support natural language such as "tomorrow" or "next monday". The AI must calculate the target date based on the current date.

The output includes: event_id, summary, start_time (including timestamp + timezone), end_time, free_busy_status, self_rsvp_status.

Step 2: Get Pending To-Dos

# Default pending summary: must explicitly filter for incomplete tasks (up to 20 items)
lark-cli task +get-my-tasks --complete=false

# Only view incomplete tasks due before a specific date (recommended for summary scenarios to reduce data volume)
lark-cli task +get-my-tasks --complete=false --due-end "2026-03-27T23:59:59+08:00"

# Get all incomplete tasks (when there are more than 20)
lark-cli task +get-my-tasks --complete=false --page-all

Note: If +get-my-tasks is called without --complete, it will return both completed and incomplete tasks, which would display completed tasks as "to-dos" in the summary. For pending summary scenarios like standups or daily reports, you must explicitly include --complete=false. Do not omit it.

It is also recommended to add filters for data volume:

• Use --due-end to filter tasks due before the target date.
• If tasks without deadlines are also needed, you can omit --due-end, but the AI should only display those created within the last 30 days in the summary, collapsing the rest as "N other historical to-dos."

Step 3: AI Summary

Integrate the results from Step 1 and Step 2 and output them in the following structure:

## {Date} Summary ({YYYY-MM-DD Day of Week})

### Schedule
| Time | Event | Organizer | Status |
|------|-------|-----------|--------|
| 09:00-10:00 | Product Requirement Review | Zhang San | Accepted |
| 14:00-15:00 | Technical Discussion | Li Si | Pending |

### To-Do Items
- [ ] {task_summary} (Due: {due_date})
- [ ] {task_summary}

### Brief Summary
- Total {n} meetings, {m} to-dos
- Conflict alert: {list schedule items with overlapping times}
- Free time slots: {free_slots} (calculated based on schedule)

Data Processing Rules:

1. Time Conversion: The API returns Unix timestamps. Convert these to HH:mm format based on the timezone field (usually Asia/Shanghai).
2. RSVP Status Mapping:

   API Value	Display Text
   accept	Accepted
   decline	Declined
   needs_action	Pending
   tentative	Tentative

3. Schedule Sorting: Sort in ascending order by start time.
4. Conflict Detection: After sorting by time, check if adjacent schedule items overlap (previous end_time > next start_time). If so, list the conflicting groups in the brief summary.
5. Declined Schedule: Mark as "Declined" but do not include in busy time slots or conflict detection.
6. To-Do Sorting: Sort by due date in ascending order. Mark overdue items as "Overdue," and place items without deadlines at the end.

Permissions Table

References

• lark-shared, Authentication, permissions (Must read)
• lark-calendar, Detailed usage of +agenda
• lark-task, Detailed usage of +get-my-tasks