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 incomplete tasks"
• "Help me see what I need to do today" / "Morning report summary"
• "Start of day summary" / "standup report"
• "What else is scheduled for this week?"

Prerequisites

Only supports user identity. 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 [--due-end]    ──► Incomplete 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 timestamp. They do not support natural language like "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 Incomplete To-Dos

# Default: Returns incomplete tasks assigned to the current user (up to 20 items)
lark-cli task +get-my-tasks

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

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

Note: Without filter conditions, it may return a large number of historical to-dos (30+ items, 100KB+), which can easily exceed context limits. Recommendations for summary scenarios:

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

Step 3: AI Summary

Integrate the results from Step 1 and Step 2 and output 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 Solution Discussion | Li Si | Pending |

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

### Brief
- 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: API returns Unix timestamp, which must be converted 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 have overlapping times (previous end_time > next start_time). If so, list the conflict groups in the brief.
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". Items without deadlines should be placed 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