larkcowork/lark-cowork-plugins/inbox-zero

inbox-zero

Pragmatic workflow for processing a mail backlog down to zero unread. Quick triage only (not full clear) → lark-mail-triage subagent or /inbox.

Verbs (the installed lark-* skills): mail +triage is the list/search verb (date/from/subject/message_id; --query full-text, --filter exact-match JSON; prints a dense table natively — no --format needed). Also mail +messages (read bodies by IDs), mail +draft-create, mail +reply, mail +send. There is NO +archive verb. Folder discovery → atomic lark-mail skill. Atomic shapes + token flags: connectors/LARK-RECIPES.md.

Workflow

1. Survey. mail +triage --max <n> --filter '{"folder":"INBOX"}'

to scan unread; or atomic lark-mail skill (is:unread query). Folders → Lark UI to find names, pass as --filter JSON.

1. Bulk-archive noise. Identify newsletters/automated/no-action.

Show count + sample, ask "archive these <N>? (y/n)". On yes → atomic lark-mail skill (no +archive verb in raw CLI; label/move via the atomic skill).

1. Classify remaining via lark-mail-triage subagent: Urgent

(today) / Important (this week) / FYI (read only).

1. Process Urgent — draft reply per item via subagent, user

confirms each send.

1. Defer Important — offer lark-task items "Reply to <sender>

re: <subject>" + due date.

1. Skim FYI — collapse to one-line summary, mark read.
2. Report: started / archived / replied / tasked / read / remaining.

Hard rules

• Confirmation gate at every batch action (archive, reply, task) —

never bulk-mutate without echo + confirm.

• Resolve senders via lark-contact before showing names.
• Archive in chunks ≤20 with confirmation between batches.
• Stop on auth error — surface lark-cli auth login, exit cleanly.
• Don't classify VIP mail as noise — sender in contact-frequency

top-10 (30d) → bump to Important minimum.

Output

End state: one short report block. Not a wall of mail.