Daily Briefing | [Day, Month Date]【免费下载链接】knowledge-work-pluginsOpen source repository of plugins primarily intended for knowledge workers to use in Claude Cowork项目地址: https://gitcode.com/GitHub_Trending/kn/knowledge-work-plugins#1 Priority[Most important thing to do today][Why it matters and what to do about it]Todays NumbersOpen PipelineClosing This MonthMeetings TodayAction Items$[X]$[X][N][N]Todays Meetings[Time] — [Company] ([Meeting Type])Attendees:[Names]Context:[One-line: deal status, last touch, whats at stake]Prep:[Quick action before this meeting][Time] — [Company] ([Meeting Type])Attendees:[Names]Context:[One-line context]Prep:[Quick action]Runcall-prep [company]for detailed meeting prepPipeline AlertsNeeds AttentionDealStageAmountAlertAction[Deal][Stage]$[X][Why flagged][What to do]Closing This WeekDealClose DateAmountConfidenceBlocker[Deal][Date]$[X][H/M/L][If any]Email PrioritiesNeeds ResponseFromSubjectReceived[Name Company][Subject][Time]Waiting On ReplyToSubjectSentDays Waiting[Name Company][Subject][Date][N]Suggested Actions[Action]— [Why now][Action]— [Why now][Action]— [Why now]Runcall-prep [company]before your meetingsRuncall-follow-upafter each call模板要点解读 - **#1 Priority** 置于顶部是全天的锚点动作确保每天先处理最重要的事 - **Todays Numbers** 给出四个关键数字未结管道总额、本月待收金额、今日会议数、行动项数量 - **Todays Meetings** 按时间排列每条包含参会人、一句上下文交易状态/最近接触/利害关系与会前准备动作 - **Pipeline Alerts** 拆成需要关注与本周收尾两组分别给出告警原因与应对动作、信心度H/M/L与阻碍因素 - **Email Priorities** 区分需要回复与等待对方回复两类后者标注已等待天数 - **Suggested Actions** 固定给出当天最值得做的 3 个动作及为什么现在做。 模板中的 call-prep 与 call-follow-up 对应仓库内的关联技能call-prep[sales/skills/call-prep/SKILL.md](https://link.gitcode.com/i/ad5ea57abe8379527c4be2d242128b2f)负责单场会议的深度准备账户快照、参会人研究、建议议程、发现性问题、潜在异议call-follow-up 对应仓库中的 call-summary 技能[sales/skills/call-summary/SKILL.md](https://link.gitcode.com/i/50621850e48075eb952ca024ec20a7f2)用于会后提取行动项、更新 CRM、起草跟进邮件。三者组合构成会前准备 → 晨间统筹 → 会后跟进的完整闭环。 --- ## 五、执行流程三段式工作流 daily-briefing 的执行严格遵循**采集上下文 → 优先级排序 → 生成简报**三步。 ### Step 1采集上下文Gather Context **有连接器时**按以下顺序自动采集Calendar → Get todays eventsFilter to external meetings (non-company attendees)Pull: time, title, attendees, descriptionCRM → Query your pipelineOpen opportunities owned by youFlag: closing this week, no activity 7 days, slipped datesGet: overdue tasks, upcoming tasksEmail → Check priority messagesUnread from opportunity contact domainsSent messages with no reply (3 days)Enrichment → Check signals (if available)Funding, hiring, news on open accounts注意其中的过滤与告警规则——并非全量拉取而是聚焦高价值信号外部会议排除公司内部参会人、本人拥有的未结机会、本周收尾/7 天以上无活动/日期已滑移的交易、逾期与临近任务、机会联系人域名的未读邮件、3 天以上未回复的外发邮件。 **没有连接器时**改为向用户提三个问题Ask user:What meetings do you have today?What deals are you focused on? Any closing soon or needing attention?Anything urgent I should know about?Work with whatever they provide.### Step 2优先级排序Prioritize 这是技能的核心决策逻辑按固定优先级从高到低排序Priority ranking:URGENT: Deal closing today/tomorrow not yet wonHIGH: Meeting today with high-value opportunityHIGH: Unread email from decision-makerMEDIUM: Deal closing this weekMEDIUM: Stale deal (7 days no activity)LOW: Tasks due this weekSelect #1 Priority:If meeting with $50K deal today → prep thatIf deal closing today → focus on closeIf urgent email from buyer → respond firstElse → highest-value stale deal该排序规则的逻辑与仓库中 pipeline-review 技能[sales/skills/pipeline-review/SKILL.md](https://link.gitcode.com/i/98ea14f9cd568bf87ad20cb164163b4e)的多因子加权框架一脉相承关闭日期 30%、交易规模 25%、阶段 20%、活动度 15%、风险 10%核心思想一致**时间紧迫性优先于规模决策人信号优先于一般任务**。特别地今天有 $50K 交易的会议 → 优先准备该会议给出了一个明确的金额阈值作为决策锚点。 ### Step 3生成简报Generate Briefing 按数据可得性组装各区块而非一律全量输出Assemble sections based on available data:#1 Priority — Always include (even if simple)Todays Numbers — If CRM connected, otherwise skipTodays Meetings — From calendar or user inputPipeline Alerts — If CRM connectedEmail Priorities — If email connectedSuggested Actions — Always include top 3 actions规则很明确**#1 Priority 与 Suggested Actions 永远输出**哪怕数据很简单而 Todays Numbers、Pipeline Alerts、Email Priorities 仅在对应连接器已接入时才出现。这保证了简报在数据缺失时也不会出现空表或占位噪音。 --- ## 六、快速模式Quick Mode与收尾模式End of Day Mode 除标准晨报外技能还提供两种派生形态配合不同时段的场景。 ### 6.1 快速模式 说 **quick brief** 或 **tldr my day** 即可获得精简版适合时间紧张的早晨 markdown # Quick Brief | [Date] **#1:** [Priority action] **Meetings:** [N] — [Company 1], [Company 2], [Company 3] **Alerts:** - [Alert 1] - [Alert 2] **Do Now:** [Single most important action]快速模式只保留四个要素首要动作、会议清单公司名列表、告警要点、现在立刻做的单一行动。6.2 收尾模式当天最后一场会议后说wrap up my day或end of day summary生成日终总结# End of Day | [Date] **Completed:** - [Meeting 1] — [Outcome] - [Meeting 2] — [Outcome] **Pipeline Changes:** - [Deal] moved to [Stage] **Tomorrows Focus:** - [Priority 1] - [Priority 2] **Open Loops:** - [ ] [Unfinished item needing follow-up]【免费下载链接】knowledge-work-pluginsOpen source repository of plugins primarily intended for knowledge workers to use in Claude Cowork项目地址: https://gitcode.com/GitHub_Trending/kn/knowledge-work-plugins创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考