Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

daily-brief-planner每日简要计划

Agent Skill

daily-brief-planner 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

20,874

周安装

749

GitHub Stars

公开资料未说明

下载量

10,418
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:daily-brief-planner(每日简要计划)
来源仓库:https://github.com/sixtysecondsapp/use60
仓库路径:skills/daily-brief-planner
安装命令:
npx skills add https://github.com/sixtysecondsapp/use60 --skill 'Daily Brief Planner'
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/sixtysecondsapp/use60 --skill 'Daily Brief Planner'

简介

: string -- 1-2 句话的当天状态总结

  • 获胜
  • :字符串数组(仅限晚上)——今天的积极信号
  • 响应格式
  • 早上的例子
  • 早上好!您的一天一目了然。
  • 日程(4次会议)
  • 09:30 团队站立
  • 10:00 Sarah Chen 进行演示(Acme Corp - 4.5 万美元提案)
  • 14:00 与 Mike Ross 进行 Discovery 通话(NewTech - 28K 美元资格)
  • 16:00 内部管道回顾
  • 优先优惠 (3)
  • Acme Corp 4.5 万美元提案于周五结束 - 自周二以来没有回复
  • TechFlow Inc 价值 28,000 美元的合格冠军陷入黑暗(9 天)
  • DataBridge 6.2 万美元谈判合同待审核
  • 联系方式 (2)
  • Sarah Chen (Acme) 最后一次联系:4 天 发送定价跟进
  • James Park (TechFlow) 最后一次联系:9 天 重新接触冠军
  • 今天到期的任务 (3)
  • [!] 将修改后的提案发送给 Acme(逾期)
  • [ ] 为 NewTech 准备发现问题
  • [ ] 更新管道预测
  • 晚上的例子
  • 结束你的一天。事情是这样的。
  • 今天的结果
  • 举行了 4 次会议 |已完成 5 项任务 |触及 3 笔交易
  • 胜利
  • Acme Corp 进入谈判阶段
  • 新技术发现电话会议进展顺利——周四预订了演示
  • 需要注意(不是今晚 - 明天)
  • TechFlow 仍然黑暗 - 考虑执行赞助商外展
  • DataBridge 合同审查已逾期 2 天
  • 明天预览
  • 09:00 与 Acme Corp 进行后续通话
  • 11:00 NewTech 演示准备(星期四)
  • 14:00 与销售经理1:1
  • 质量检查表
  • 在返回简报之前,请验证:
  • 正确检测到时间模式并且问候语匹配
  • 时间表显示今天的所有会议(不仅仅是前几个)
  • 优先优惠仅限 3-5 件(不得超过 5 件)
  • 每笔交易都有明确的“警报”纳入理由
  • 联系人链接到有效交易(无孤立联系人)
  • 任务按优先级排序,逾期项目已标记
  • 任何部分均不超过 5 项(修剪至最重要)
  • 每个项目最多可容纳 1-2 行
  • 夜间模式包括明天预览和胜利
  • 下午模式显示进度(完成的项目数)
  • 摘要是 1-2 句话,而不是段落
  • 包含用于可点击导航的所有实体 ID
  • 没有捏造的数据——如果某个字段未知,则忽略它
  • 错误处理
  • 今天没有会议
  • 在日程部分显示“今天没有安排会议”。不要跳过这一部分——缺席会议本身就是有用的信息。建议:“重点管道工作的好日子。”
  • 没有交易正在进行中
  • 显示“没有正在进行的交易”并将重点转移到联系人和任务上。如果任务也为空,请温和地提示:“您的管道已畅通无阻。考虑勘探或安排发现调用。”
  • 部分数据(部分获取失败)
  • 使用任何可用的数据来构建简报。清楚地记下哪些部分的数据不完整:“交易健康评分不可用 - 仅显示截至日期的交易。”
  • 今天没有到期任务
  • 显示“今天没有到期任务”,但检查是否有逾期任务。如果存在逾期任务,请强调:“今天没有到期任务,但有 3 个任务逾期。”
  • 未提供一天中的时间
  • 从当前时间戳确定。如果时间戳也不可用,则默认为早晨模式(最全面、最安全的默认值)。
  • 非常忙碌的一天(10+次会议)
  • 当日程排得满满的时,按时间段分组:
  • 上午时段(中午 12 点之前):X 次会议
  • 下午时段(12pm-5pm):Y 会议
  • 显示最重要的 3 个(按关联交易价值)并总结其余的。
  • 周末/节假日
  • 如果日期是周末或已知假期,请调整:“今天是星期六 - 快速浏览一下星期一即将发生的事情。”而是获取周一的日程安排和本周的结转项目。
  • 过时数据警告
  • 如果整个管道中最近的交易更新已超过 48 小时,请添加注释:“您的管道数据已超过 2 天没有更新。请考虑检查交易阶段。”
  • 每周安装量
  • 存储库
  • 六十秒应用程序/use60
  • 第一次看到
  • 安全审计
  • Gen Agent Trust Hub 通行证
  • 套接字通行证
  • 斯尼克通行证

SKILL.md

Available Context & Tools

@_platform-references/org-variables.md @_platform-references/capabilities.md

Daily Brief Planner

Goal

Generate a time-aware daily briefing that gives the sales rep a complete situational picture in 30 seconds or less. The briefing is not a plan (that is the Daily Focus Planner's job) -- it is a status report that answers: "Where do I stand right now?"

Research from the Harvard Business Review shows that reps who start with a structured daily overview are 27% more productive and 19% more likely to hit quota, because they avoid the "inbox drift" problem -- reacting to whatever arrives first instead of working strategically.

Why Daily Briefings Matter

The Information Asymmetry Problem

Sales reps juggle 15-30 active relationships, 5-15 open deals, and dozens of tasks. Without a structured briefing:

  • 41% of selling time is spent on non-revenue activities (Salesforce State of Sales, 2024)
  • Reps check 4-6 tools before their first call, wasting 30-45 minutes each morning
  • Critical signals (stale deal, missed follow-up, important meeting today) get buried

The Briefing Solution

A well-structured briefing compresses 30 minutes of tool-hopping into a 30-second scan. It surfaces:

  1. Time-sensitive items -- meetings happening today, tasks due today
  2. Risk signals -- deals going dark, contacts not engaged
  3. Momentum indicators -- deals advancing, meetings booked, tasks completed

Time-Aware Mode Design

The briefing adapts its psychology, content, and structure to the time of day. Each mode has a distinct purpose. Consult references/brief-templates.md for the full template structure, formatted examples for each mode, and special Monday/Friday templates.

Morning Mode (before 12pm) -- "Set the Trajectory"

Psychology: The rep is fresh, planning-oriented, and open to structure. This is the highest-leverage moment for the briefing because it shapes the entire day's direction.

Content priorities (in order):

  1. Today's schedule -- Every meeting with time, attendees, linked deal, and a one-line prep note. Meetings are the backbone of a sales day; missing or arriving unprepared to one is the most expensive mistake.
  2. Priority deals snapshot -- 3-5 deals that need attention today. Selection criteria:

- Closing this week (urgency) - Health score dropped below 60 (risk) - No activity in 7+ days (stale) - Stage advancement opportunity (momentum)

  1. Contacts needing attention -- People who haven't been touched in 7+ days and are linked to active deals.
  2. Tasks due today -- Grouped by priority. Overdue tasks highlighted first.
  3. One-line energy boost -- A quick summary that sets a positive, focused tone.

Greeting: "Good morning! Here's your day at a glance."

Afternoon Mode (12pm-5pm) -- "Course Correct"

Psychology: The rep has been in the field for hours. Energy dips. They need a quick recalibration -- what landed, what slipped, what still needs doing before end of day.

Content priorities (in order):

  1. Progress check -- Meetings completed, tasks closed, deals updated. Acknowledge momentum. Seeing progress sustains energy (the Progress Principle, Amabile & Kramer).
  2. Remaining schedule -- Only what is left today. Do not repeat morning meetings.
  3. Unfinished priority actions -- Tasks or follow-ups that were due by now but remain open. Flag them as "still needs your attention."
  4. Emerging alerts -- Anything that changed since morning: new meeting invite, deal stage change, contact replied.
  5. Re-prioritized deal list -- Recalculate based on what happened this morning. A deal that got a positive call this morning drops in urgency; one that was supposed to get a call but didn't rises.

Greeting: "Here's your afternoon check-in."

Evening Mode (after 5pm) -- "Capture and Close"

Psychology: The rep is winding down. They want closure on today and a preview of tomorrow so they can mentally detach without anxiety.

Content priorities (in order):

  1. Day summary -- What got done: meetings held, tasks completed, deals touched. Quantify it ("You had 4 meetings, completed 6 tasks, and moved 2 deals forward").
  2. Wins -- Any positive signals: deal advanced, meeting booked, proposal sent, reply received. Always lead with wins; it ends the day on a positive note.
  3. Learnings / flags -- Things that need attention but not tonight: a deal that went dark, a contact who raised a concern, a task that slipped.
  4. Tomorrow preview -- First 2-3 meetings of tomorrow, any high-priority tasks due tomorrow, and one focus area.
  5. Sign-off -- A brief, encouraging close.

Greeting: "Wrapping up your day. Here's how it went."

Required Capabilities

  • Calendar: To fetch today's (and optionally tomorrow's) meetings
  • CRM: To fetch deal pipeline status, health scores, and contact engagement data
  • Tasks: To fetch pending, due, and overdue tasks

Inputs

  • meetings: from execute_action("get_meetings_for_period", {period: "today"}) and optionally {period: "tomorrow"} for evening mode
  • deals: from execute_action("get_pipeline_deals", {filter: "stale"}) combined with {filter: "closing_soon"}
  • contacts: from execute_action("get_contacts_needing_attention", {days_since_contact: 7})
  • tasks: from execute_action("list_tasks", {filter: "today"})
  • time_of_day: "morning" | "afternoon" | "evening" (derived from current time or sequence context)

Data Gathering Strategy

Parallel Fetches (all modes)

Execute these simultaneously to minimize latency:

  1. execute_action("get_meetings_for_period", {period: "today"})
  2. execute_action("get_pipeline_deals", {filter: "closing_soon", period: "this_week", include_health: true, limit: 10})
  3. execute_action("get_contacts_needing_attention", {days_since_contact: 7, limit: 10})
  4. execute_action("list_tasks", {status: "pending", filter: "today", limit: 15})

Additional Fetches by Mode

  • Evening mode only: execute_action("get_meetings_for_period", {period: "tomorrow"})
  • Afternoon mode: execute_action("list_tasks", {status: "completed", filter: "today"}) to show progress

Priority Deal Selection Methodology

Not all deals deserve a spot in the briefing. Use this scoring to rank. See references/priority-rules.md for the complete scoring model with worked examples, tiebreaker rules, and research backing for each weight.

SignalWeightRationale
Closes this week+40Urgency drives action
Health score < 60+30At-risk deals need intervention
No activity in 7+ days+25Stale deals die silently
Value > 2x average deal+20High-value deals justify extra attention
Stage = Negotiation/Proposal+15Late-stage deals are closest to revenue
Champion went dark+35Losing your champion is the #1 deal killer

Selection rules:

  • Show 3-5 deals maximum. More than 5 creates decision paralysis.
  • Always include at least 1 closing-soon deal if any exist.
  • If fewer than 3 deals qualify, that is fine -- do not pad with low-priority deals.
  • Never show a deal that was updated in the last 24 hours unless it has a meeting today.

Contact Attention Thresholds

When silence becomes dangerous depends on deal stage. See references/priority-rules.md for the full contact priority scoring model and special escalation rules.

Deal StageDays Without Contact Before AlertRisk Level
Discovery / Qualification10 daysMedium
Demo / Evaluation7 daysHigh
Proposal / Negotiation5 daysCritical
Closed Won (post-sale)14 daysLow
No active deal21 daysLow

Special escalation: If a contact is the identified champion or economic buyer on a deal closing this month, the threshold drops to 3 days.

Information Density Principles

The briefing must be scannable in 30 seconds. Apply these formatting rules:

The 3-5-1 Rule

  • 3: Maximum 3 sections visible without scrolling
  • 5: Maximum 5 items per section
  • 1: Each item is 1 line (2 lines maximum for deals with context)

Hierarchy of Information

Each item follows: Entity Name | Key Metric | Action Signal

Examples:

  • "Acme Corp ($45K) | Closing Friday | No reply since Tuesday"
  • "10:00 AM - Demo with Sarah Chen (Acme) | Deal: $45K Proposal stage"
  • "Follow up with James Park | Last contact: 8 days ago | Deal: TechFlow $28K"

What NOT to Include

  • Meeting descriptions (too long, not useful in a scan)
  • Full task descriptions (title only)
  • Deal history or change log
  • Contacts not linked to active deals (unless explicitly stale and valuable)

Output Contract

Return a SkillResult with data.daily_brief:

  • greeting: string -- time-appropriate opening
  • time_of_day: "morning" | "afternoon" | "evening"
  • schedule: array of today's meetings

- time: string (formatted time, e.g., "10:00 AM") - title: string - attendees: array of strings - deal_id: string | null - deal_name: string | null - prep_note: string (one-line context, e.g., "Follow up on pricing discussion")

  • priority_deals: array of 3-5 deals needing attention

- id: string - name: string - value: number - stage: string - days_stale: number - health_score: number | null - close_date: string | null - alert: string (one-line reason for inclusion)

  • contacts_needing_attention: array of contacts to follow up with

- id: string - name: string - company: string - days_since_contact: number - linked_deal: string | null - suggested_action: string

  • tasks: array of pending tasks for today

- id: string - title: string - priority: "high" | "medium" | "low" - due_date: string - is_overdue: boolean - deal_id: string | null

  • progress: object (afternoon/evening only)

- meetings_completed: number - tasks_completed: number - deals_touched: number

  • tomorrow_preview: array (evening only) of tomorrow's key meetings/priorities

- time: string - title: string - deal_name: string | null

  • summary: string -- 1-2 sentence summary of the day's status
  • wins: array of strings (evening only) -- positive signals from today

Response Formatting

Morning Example

Good morning! Here's your day at a glance.

SCHEDULE (4 meetings)
  09:30  Team standup
  10:00  Demo with Sarah Chen (Acme Corp - $45K Proposal)
  14:00  Discovery call with Mike Ross (NewTech - $28K Qualified)
  16:00  Internal pipeline review

PRIORITY DEALS (3)
  Acme Corp       $45K  Proposal   Closes Friday - no reply since Tue
  TechFlow Inc    $28K  Qualified  Champion went dark (9 days)
  DataBridge      $62K  Negotiation  Contract review pending

CONTACTS TO REACH (2)
  Sarah Chen (Acme)      Last contact: 4 days  Send pricing follow-up
  James Park (TechFlow)  Last contact: 9 days  Re-engage champion

TASKS DUE TODAY (3)
  [!] Send revised proposal to Acme (overdue)
  [ ] Prepare discovery questions for NewTech
  [ ] Update pipeline forecast

Evening Example

Wrapping up your day. Here's how it went.

TODAY'S RESULTS
  4 meetings held | 5 tasks completed | 3 deals touched

WINS
  Acme Corp moved to Negotiation stage
  NewTech discovery call went well - demo booked for Thursday

NEEDS ATTENTION (not tonight - tomorrow)
  TechFlow still dark - consider exec sponsor outreach
  DataBridge contract review now 2 days overdue

TOMORROW PREVIEW
  09:00  Follow-up call with Acme Corp
  11:00  Demo prep for NewTech (Thursday)
  14:00  1:1 with sales manager

Quality Checklist

Before returning the briefing, verify:

  • Time mode correctly detected and greeting matches
  • Schedule shows ALL today's meetings (not just the first few)
  • Priority deals limited to 3-5 (never more than 5)
  • Every deal has a clear "alert" reason for inclusion
  • Contacts are linked to active deals (no orphan contacts)
  • Tasks sorted by priority, overdue items flagged
  • No section exceeds 5 items (trim to most important)
  • Each item fits on 1-2 lines maximum
  • Evening mode includes tomorrow preview and wins
  • Afternoon mode shows progress (completed items count)
  • Summary is 1-2 sentences, not a paragraph
  • All entity IDs included for clickable navigation
  • No fabricated data -- if a field is unknown, omit it

Error Handling

No meetings today

Show "No meetings scheduled today" in the schedule section. Do NOT skip the section -- the absence of meetings is itself useful information. Suggest: "Good day for focused pipeline work."

No deals in pipeline

Show "No active deals in pipeline" and shift emphasis to contacts and tasks. If tasks are also empty, provide a gentle prompt: "Your pipeline is clear. Consider prospecting or scheduling discovery calls."

Partial data (some fetches fail)

Build the briefing with whatever data is available. Clearly note which sections have incomplete data: "Deal health scores unavailable -- showing deals by close date only."

No tasks due today

Show "No tasks due today" but check for overdue tasks. If overdue tasks exist, surface them with emphasis: "No tasks due today, but 3 tasks are overdue."

Time of day not provided

Determine from the current timestamp. If timestamp is also unavailable, default to morning mode (the most comprehensive and safest default).

Very busy day (10+ meetings)

When schedule is overwhelming, group by time block:

  • Morning block (before 12pm): X meetings
  • Afternoon block (12pm-5pm): Y meetings Show the top 3 most important (by linked deal value) and summarize the rest.

Weekend / holiday

If the date is a weekend or known holiday, adjust: "It's Saturday -- here's a quick look at what's coming Monday." Fetch Monday's schedule and this week's carry-over items instead.

Stale data warning

If the most recent deal update is more than 48 hours old across the entire pipeline, add a note: "Your pipeline data hasn't been updated in 2+ days. Consider reviewing deal stages."

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

34.28%
按下载量换算3,571

Claude

30.22%
按下载量换算3,148

Cursor

19.67%
按下载量换算2,049

Gemini CLI

8.8%
按下载量换算917

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills