weekly-prep-brief by anthropics/knowledge-work-plugins
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill weekly-prep-brief生成一份全面的每周简报,涵盖未来 7 天内所有外部客户或潜在客户通话,并包含来自 Common Room 的每次会议账户和联系人研究。
选项 A — 日历已连接: 使用 ~~calendar 连接器获取未来 7 天(或用户指定的时间范围)内安排的所有会议。筛选并仅保留外部会议——即包含组织外部参会者的会议。丢弃纯内部会议、与同事的一对一会议以及定期的内部同步会议。
为每个外部会议识别:
选项 B — 日历未连接: 询问用户:"为了构建您的每周准备简报,我需要您即将进行的外部通话信息。请列出:公司名称、日期/时间以及参会者姓名。"
接受自由格式的输入,并在继续之前将其解析为结构化列表。
在开始研究之前,将识别出的会议呈现给用户进行确认:
"这是我为您找到的本周外部通话。请告知是否有遗漏或需要排除的会议:
- [公司] — [星期几],[时间] — [参会者]
- ..."
这可以避免对已取消或错误的会议进行无效研究。
对于每个确认的外部会议,尽可能并行运行:
Common Room 数据是主要来源。完成 CR 研究后,对每家公司进行一次快速的近期动态检查——这是补充性的,而非主要来源:
"[公司名称]" 新闻,时间范围限定在过去 7 天内广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
深度校准:
将所有针对会议的研究汇编成一份单一的结构化文档,按会议日期/时间排序。
开头提供一个简要的周度概览,突出显示:
# 每周准备简报 — [日期] 所在周
## 周度概览
[2–4 个要点:关键主题、标记的优先级、通话数量]
---
## [星期一 / 星期二 / 等]
### [公司名称] — [时间]
**参会者:** [姓名和职位]
**会议类型:** [发现 / QBR / 续约 / 扩展 / 等 — 尽可能推断]
**公司快照**
[4–5 个要点:账户状态、重要信号、近期活动]
**参会者资料**
- **[姓名]** ([职位]): [2–3 个要点:关于他们的信号、角色、对话角度]
- [每位参会者重复此格式]
**本周重要信号**
[2–3 个与此特定通话最相关的信号]
**本周新闻** [如果发现值得注意的新闻]
[仅包含真正值得注意的发现 — 融资、领导层变动、重大新闻报道]
**建议目标**
[1–2 句话:在此会议中要完成什么]
---
[按日期/时间排序,为每个会议重复此格式]
如果 Common Room 为某个特定会议的账户或参会者返回的数据有限,请使用压缩格式代替完整模板:
### [公司名称] — [时间] ⚠️ 数据有限
**参会者:** [姓名和职位(如果已知)]
**可用数据:** [Common Room 实际返回的内容]
**网络搜索结果**
[来自网络搜索的发现 — 公司新闻、参会者 LinkedIn 个人资料]
**注意:** Common Room 关于此账户的数据有限。销售代表可能需要在通话前直接在 CR 中查看或向同事收集背景信息。
不要根据稀疏的数据生成完整的会议准备部分(公司快照、信号亮点、谈话要点、建议目标)。一个简短而诚实的部分比一个虚构的完整部分更有用。
references/briefing-guide.md — 简报结构指南、优先级逻辑以及如何处理边缘情况(已取消的会议、没有数据的新账户等)的指南每周安装次数
76
代码仓库
GitHub Stars
8.8K
首次出现
14 天前
安全审计
安装于
codex73
opencode72
github-copilot72
kimi-cli72
amp72
gemini-cli72
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.
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:
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.
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.
For each confirmed external meeting, run in parallel where possible:
Common Room data is the primary source. After CR research, run a quick recency check for each company — this is supplementary, not primary:
"[company name]" news scoped to the last 7 daysDepth calibration:
Compile all per-meeting research into a single structured document, sorted by meeting date/time.
Open with a brief week-level overview that flags:
# Weekly Prep Brief — Week of [Date]
## Week Overview
[2–4 bullets: key themes, flagged priorities, call count]
---
## [Monday / Tuesday / etc.]
### [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]
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:
### [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.
references/briefing-guide.md — guidelines for structuring briefings, prioritization logic, and how to handle edge cases (cancelled meetings, new accounts with no data, etc.)Weekly Installs
76
Repository
GitHub Stars
8.8K
First Seen
14 days ago
Security Audits
Gen Agent Trust HubPassSocketPassSnykWarn
Installed on
codex73
opencode72
github-copilot72
kimi-cli72
amp72
gemini-cli72
React 组合模式指南:Vercel 组件架构最佳实践,提升代码可维护性
106,200 周安装
Apify Actor 输出模式生成工具 - 自动化创建 dataset_schema.json 与 output_schema.json
245 周安装
rclone 文件传输技能:命令行工具配置与使用教程,支持 AWS S3、Google Drive 等云存储
245 周安装
AI 产品需求文档生成器 | 自动撰写 PRD 和功能规格说明书工具
245 周安装
阿里云AI音频TTS语音克隆测试指南 - 最小可行性测试与验证方法
245 周安装
Symfony质量检查工具:优化架构、安全执行复杂变更的PHP开发助手
245 周安装
本地代码变更审查指南 - 自动化代码质量与安全审计工具
245 周安装