Back to Details

weekly-prep-brief

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Weekly Prep Brief

每周准备简报

Generate a single comprehensive weekly briefing that covers every external customer or prospect call in the next 7 days, with per-meeting account and contact research from Common Room.
生成一份涵盖未来7天内所有外部客户或潜在客户通话的综合性每周简报，其中包含来自Common Room的每场会议客户账户及联系人调研信息。

Briefing Process

简报生成流程

Step 1: Get the Week's External Meetings

步骤1：获取本周外部会议

Option A — Calendar connected: Use the 
~~calendar
connector to fetch all meetings scheduled in the next 7 days (or a user-specified range). Filter to keep only external meetings — those with attendees from outside your organization. Discard internal-only meetings, one-on-ones with colleagues, and recurring internal syncs.
Identify for each external meeting:
  • Company name
  • Meeting date and time
  • External attendee names and email addresses
Option B — No calendar connected: Ask the user: "To build your weekly prep brief, I'll need your upcoming external calls. Please list them: company name, date/time, and attendee names."
Accept freeform input and parse it into a structured list before proceeding.
选项A — 已连接日历： 使用
~~calendar
连接器获取未来7天（或用户指定时间段）内的所有会议。筛选保留仅包含外部参会者的会议——即有组织外人员参与的会议。剔除仅内部会议、与同事的一对一会议以及重复性内部同步会议。
为每场外部会议确认以下信息：
  • 公司名称
  • 会议日期和时间
  • 外部参会者姓名及邮箱地址
选项B — 未连接日历： 询问用户：“为了生成您的每周准备简报，我需要您即将到来的外部通话信息。请列出以下内容：公司名称、日期/时间以及参会者姓名。”
接收自由格式输入并将其解析为结构化列表后再继续。

Step 2: Confirm the Meeting List

步骤2：确认会议列表

Present the identified meetings to the user for confirmation before beginning research:
"Here are the external calls I found for this week. Let me know if anything's missing or should be excluded:
  • [Company] — [Day], [Time] — [Attendees]
  • ..."
This prevents wasted research on cancelled or incorrect meetings.
在开始调研前，将识别出的会议列表呈现给用户确认：
“以下是我找到的您本周的外部通话。如果有遗漏或需要排除的内容，请告知我：
  • [公司名称] — [日期], [时间] — [参会者]
  • ...”
这可以避免在已取消或错误的会议上浪费调研资源。

Step 3: Research Each Meeting

步骤3：调研每场会议

For each confirmed external meeting, run in parallel where possible:
  1. Account research — full account snapshot using the account-research skill
  2. Contact research — profile for each external attendee using the contact-research skill
Common Room data is the primary source. After CR research, run a quick recency check for each company — this is supplementary, not primary:
  • Search 
    "[company name]" news
    scoped to the last 7 days
  • For executive attendees, search their name for recent public posts or interviews
  • Only include findings that are genuinely noteworthy (funding, leadership changes, major press). Don't pad the brief with generic news.
Depth calibration:
  • For high-priority accounts (large accounts, open opportunities, renewal risk), produce full depth research
  • For lower-priority or short meetings, produce abbreviated snapshots (3–4 bullets each)
对于每场已确认的外部会议，尽可能并行执行以下操作：
  1. 账户调研 — 使用account-research技能生成完整的客户账户快照
  2. 联系人调研 — 使用contact-research技能生成每位外部参会者的个人资料
Common Room数据为主要数据源。完成Common Room调研后，为每家公司进行快速时效性检查——这是补充性调研，而非主要调研：
  • 搜索
    "[公司名称]" news
    ，范围限定为过去7天
  • 对于高管参会者，搜索其近期的公开帖子或采访
  • 仅纳入真正值得关注的发现（融资、领导层变动、重大新闻）。不要用通用新闻填充简报。
调研深度校准：
  • 对于高优先级账户（大型客户、未结商机、续约风险账户），生成全面深度的调研内容
  • 对于低优先级或短时长会议，生成精简版快照（每项3–4条要点）

Step 4: Synthesize the Weekly Brief

步骤4：合成每周简报

Compile all per-meeting research into a single structured document, sorted by meeting date/time.
Open with a brief week-level overview that flags:
  • Any accounts with urgent signals (at-risk, trial expiring, expansion opportunity)
  • Any meetings that need special preparation or executive involvement
  • Total external call count and estimated time commitment
将每场会议的调研内容整理为一份结构化文档，按会议日期/时间排序。
开头添加简短的本周概览，标注：
  • 任何带有紧急信号的账户（高风险、试用到期、拓展机会）
  • 任何需要特殊准备或高管参与的会议
  • 外部通话总数及预估时间投入

Output Format

输出格式

undefined
undefined

Weekly Prep Brief — Week of [Date]

Weekly Prep Brief — Week of [Date]

Week Overview

Week Overview

[2–4 bullets: key themes, flagged priorities, call count]
[2–4 bullets: key themes, flagged priorities, call count]

[Monday / Tuesday / etc.]

[Monday / Tuesday / etc.]

[Company Name] — [Time]

[Company Name] — [Time]

Attendees: [Names and titles] Meeting type: [Discovery / QBR / Renewal / Expansion / etc. — inferred if possible]
Company Snapshot [4–5 bullets: account status, top signals, recent activity]
Attendee Profiles
  • [Name] ([Title]): [2–3 bullets on their signals, persona, conversation angle]
  • [Repeat per attendee]
Top Signals This Week [2–3 most relevant signals for this specific call]
This Week's News [If notable news found] [Only genuinely noteworthy findings — funding, leadership changes, major press]
Recommended Objectives [1–2 sentences: what to accomplish in this meeting]
[Repeat per meeting, sorted by date/time]
undefined
Attendees: [Names and titles] Meeting type: [Discovery / QBR / Renewal / Expansion / etc. — inferred if possible]
Company Snapshot [4–5 bullets: account status, top signals, recent activity]
Attendee Profiles
  • [Name] ([Title]): [2–3 bullets on their signals, persona, conversation angle]
  • [Repeat per attendee]
Top Signals This Week [2–3 most relevant signals for this specific call]
This Week's News [If notable news found] [Only genuinely noteworthy findings — funding, leadership changes, major press]
Recommended Objectives [1–2 sentences: what to accomplish in this meeting]
[Repeat per meeting, sorted by date/time]
undefined

When a Meeting Has Sparse Data

当会议数据稀疏时

If Common Room returns limited data for a particular meeting's account or attendees, use a compressed format for that meeting instead of the full template:
undefined
如果Common Room返回的某场会议的账户或参会者数据有限，使用压缩格式展示该会议内容，而非完整模板：
undefined

[Company Name] — [Time] ⚠️ Limited Data

[Company Name] — [Time] ⚠️ Limited Data

Attendees: [Names and titles if known] Data available: [What Common Room actually returned]
Web Search Results [Findings from web search — company news, attendee LinkedIn profiles]
Note: Common Room has limited data on this account. The rep may want to check directly in CR or gather context from colleagues before this call.

Do not generate a full meeting prep section (company snapshot, signal highlights, talking points, recommended objectives) from sparse data. A short honest section is more useful than a fabricated full one.
Attendees: [Names and titles if known] Data available: [What Common Room actually returned]
Web Search Results [Findings from web search — company news, attendee LinkedIn profiles]
Note: Common Room has limited data on this account. The rep may want to check directly in CR or gather context from colleagues before this call.

不要用稀疏数据生成完整的会议准备内容（公司快照、信号重点、沟通要点、建议目标）。简短且真实的内容比编造的完整内容更有用。

Quality Standards

质量标准

  • Keep each meeting section scannable — reps read these in the morning, often on mobile
  • Always sort by date/time ascending
  • Flag urgent situations prominently (risk, trial expiration, open opps) — don't bury them
  • If a meeting has very thin Common Room data, use the sparse-data format above — never fill the full template with guesses
  • Total brief should be readable in 10–15 minutes for a week with 4–6 meetings
  • Every fact must come from a tool call — no invented deal context, activity, or signals
  • 保持每场会议内容易于扫描——销售代表通常在早上阅读，且经常使用移动设备
  • 始终按日期/时间升序排序
  • 突出标注紧急情况（风险、试用到期、未结商机）——不要将其隐藏在内容中
  • 如果某场会议的Common Room数据非常少，使用上述稀疏数据格式——绝不要用猜测内容填充完整模板
  • 对于有4–6场会议的一周，整个简报应在10–15分钟内读完
  • Every fact must come from a tool call — no invented deal context, activity, or signals

Reference Files

参考文件

  • references/briefing-guide.md
     — guidelines for structuring briefings, prioritization logic, and how to handle edge cases (cancelled meetings, new accounts with no data, etc.)
  • references/briefing-guide.md
     — 简报结构指南、优先级逻辑以及边缘情况处理方式（已取消会议、无数据的新客户等）