lark-task

Run lark-cli task +create with --summary for the title, plus optional --assignee, --due, and --tasklist-id flags. When creating a task for yourself, first get your open_id via lark-cli auth status and pass it as the assignee.

Use lark-cli task +get-my-tasks --complete=false to fetch only pending tasks assigned to you. You can add --due-end to bound the due date, and the command paginates automatically up to 20 pages by default.

Use +search only when you have an actual query keyword like a task name. For scope-only filters such as "created by me" or "this year", prefer +get-related-tasks or +get-my-tasks, which list tasks without requiring a search keyword.

Yes, use lark-cli task +upload-attachment with --resource-id (task GUID or applink) and --file pointing to a local file. Each call uploads one file up to 50 MB, and the path must be relative to the current working directory.

Reminders require the task to have a due date set first. Also, repeat rules and start times must satisfy ordering constraints: the start time must be earlier than or equal to the due time.

Use lark-task for task center items, tasklists, assignments, and deadlines. If the context involves meeting minutes or a minute_token, todos belong to the lark-minutes skill instead, and task commands should not be used.