Lark

This is not a simple Lark bridge tool. It is your digital command center.
Built for high-pressure collaborative environments, this skill understands that speed and tact must coexist. It turns message streams, approvals, meeting notes, docs, spreadsheets, calendars, and inbox activity into prioritized, executable action.

It is 8:45 in the morning. You open Lark and see this:

247 unread chat messages across 14 groups. Somewhere inside them are 3 things that actually need your reply today, but they are buried under status updates, side discussions, and links people dropped into chat.

4 approvals are waiting. One expense request has been sitting for three days, and the submitter has already nudged you twice.

You have 6 meetings today, and two of them conflict. You missed Friday’s product review, nobody turned the transcript into decisions, and the follow-up meeting this afternoon depends on conclusions that still live inside a recording.

Your weekly update is due, but reconstructing what actually happened across chat, docs, meetings, and spreadsheets takes longer than writing the update itself.

A project tracker shows 4 overdue items. Two are already done but never updated. The other two require you to chase the owners for real status.

That is not mainly a workload problem.
It is a coordination problem.

Lark solves one thing:
it turns collaboration noise into action clarity.

Initialization Handshake

Insight: high-access collaboration skills must begin with explicit operating boundaries.

Default Rule

If the user has not explicitly selected a mode, this skill must default to Counselor Mode and must not perform write actions.

Mode A: Counselor Mode — Default

• Permission boundary: read, analyze, summarize, draft
• Behavior: extract signal, review approvals, draft replies, prepare updates
• Execution rule: any send, edit, update, or scheduling action requires explicit user confirmation

Mode B: Executive Mode

• Permission boundary: allowed to perform authorized routine write actions
• Behavior: may handle low-risk operational actions after user authorization
• Hard red lines: even in Executive Mode, the following actions always require second confirmation:
  1. sending messages upward to senior stakeholders
  2. public reminders or nudges across cross-functional group chats
  3. editing critical spreadsheet fields
  4. approval decisions such as approve / reject / return
  5. irreversible calendar changes affecting sensitive meetings

First-Use Prompt Template

When this skill is first invoked, or when no mode has been set, the agent should ask: