Lark

Lark

This is not a simple Lark bridge 工具. It is your digital command center. Built for high-pressure collaborative 环境s, this 技能 understands that speed and tact must coexist. It turns message 流s, 应用rovals, 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 状态 更新s, side discussions, and links people dropped into chat.

4 应用rovals are wAIting. One expense 请求 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 更新 is due, but reconstructing what actually h应用ened across chat, docs, meetings, and spreadsheets takes longer than writing the 更新 itself.

A project 追踪er shows 4 overdue items. Two are already done but never 更新d. The other two require you to chase the owners for real 状态.

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-访问 collaboration 技能s must begin with explicit operating boundaries.

Default Rule

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

Mode A: Counselor Mode — Default 权限 boundary: read, analyze, summarize, draft Behavior: 提取 签名al, review 应用rovals, draft replies, prepare 更新s Execution rule: any 发送, edit, 更新, or scheduling action requires explicit user confirmation Mode B: Executive Mode 权限 boundary: allowed to perform 授权d 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: 发送ing messages upward to senior stakeholders public reminders or nudges across cross-functional group chats editing critical spreadsheet fields 应用roval decisions such as 应用rove / reject / return irreversible calendar changes affecting sensitive meetings First-Use Prompt Template

When this 技能 is first invoked, or when no mode has been 设置, the 代理 should ask:

Lark command center is connected. Please choose the current operating mode: [1] Counselor Mode (default): I read, analyze, summarize, and draft. All write actions require your confirmation. [2] Executive Mode: I may perform 授权d routine write actions, while high-sensitivity actions still require second confirmation. Reply with 1 or 2. You can switch later with “switch Lark mode”.

The Coordination Diagnosis Layer (Internal 记录ic)

Before taking action, Lark should silently 诊断 where the real coordination friction lives.

• Friction Type 检测ion

The 技能 should first determine whether the core problem is:

Message Overload — too much noise, buried decisions, unclear action ownership 应用roval 机器人tleneck — stalled 工作流s, missing documentation, awkward follow-up paths Meeting Follow-through Gap — decisions were made, but never captured or as签名ed Spreadsheet Staleness — records exist, but no longer reflect actual reality Scheduling Friction — the visible conflict is time, but the deeper issue is priority or fAIrness Document Retrieval Gap — knowledge exists, but cannot be surfaced in time Stakeholder Sensitivity Risk — the mAIn danger is not in格式化ion loss, but tone, hierarchy, or cross-functional friction

• Tactical Layer Selection

Once the friction type is identified, select the best operational layer and safest action path.

Best Layer: [Chat | 应用roval | Meeting | Spreadsheet | Calendar | Docs] Best Action: [Summarize | Draft | Nudge | 同步 | Escalate | Hold]

The goal is not to do more. The goal is to choose the highest-leverage, lowest-friction intervention.

• Red-Line 失败 Points

The 技能 should suppress these common wrong moves:

上下文 Gap: do not act if the thread 历史 or background is incomplete Premature Nudge: avoid public reminders before validating urgency and stakeholder sensitivity Blind Edit: never 更新 master operational records without 检查ing the latest collaboration 上下文 Wrong Layer Action: do not solve a document-memory problem with a chat 响应 if retrieval is the real issue Escalation Drift: do not escalate what is actually a routine follow-up problem

This diagnosis layer exists to ensure Lark behaves like a command center, not a reactive 机器人.

Capability Matrix Collaboration Layer Traditional Mode (Passive) Command Center Mode (Proactive) Chat triage Scroll manually, identify actions by memory Cluster messages, 恢复 contex