briefing

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Briefing Skill

简报Skill

Compile a daily briefing from brain context.

Filing rule: When the briefing creates or updates brain pages, follow
skills/_brain-filing-rules.md
.

从brain上下文整合每日简报。

归档规则： 当简报创建或更新brain页面时，请遵循
skills/_brain-filing-rules.md
。

Contract

约定

Every fact in the briefing includes an inline
```
[Source: slug, updated DATE]
```
citation.
Meeting participants are resolved against the brain; gaps are explicitly flagged.
Active deals and action items include deadlines and recency context.
The briefing is read-only: no brain pages are created or modified unless the user explicitly requests it.
Stale alerts surface pages relevant to today's context, not just all stale pages.

简报中的每个事实都包含内联引用
```
[Source: slug, 更新日期]
```
。
会议参与者需与brain中的信息匹配；信息缺失需明确标记。
活跃交易和行动项需包含截止日期及最新动态上下文。
简报为只读模式：除非用户明确要求，否则不得创建或修改brain页面。
过期提醒仅展示与今日上下文相关的页面，而非所有过期页面。

Phases

执行阶段

Hot memory pulse (v0.32). Before composing anything else, run:
bash
```
gbrain recall --since-last-run --supersessions --pending --rollup --json
```
Fold the result into the briefing under a "Brain pulse" section at the top:
1. Contradictions resolved overnight — the
```
--supersessions
```
  output. Lead with these because they're new corrections to your model of the world.
2. Top mentions —
```
top_entities
```
  from
```
--rollup
```
  (top 5 entity slugs by fact count in the window).
3. New facts since last briefing — group the
```
facts
```
  array under each entity from the rollup; include
```
kind
```
  ,
```
notability
```
  , and
```
confidence
```
  .
4. Pending consolidation footer — when
```
pending_consolidation_count > 0
```
  , note
```
N facts await dream-cycle consolidation
```
  so the operator can decide whether to run
```
gbrain dream
```
  before reading further.
The
```
--since-last-run
```
flag advances
```
~/.gbrain/recall-cursors/<source>.json
```
so the next briefing picks up exactly where this one left off. If you're running this as a cron job, pass
```
--source <slug>
```
or set
```
GBRAIN_SOURCE
```
explicitly — cron doesn't start in your repo-root cwd, so dotfile resolution may miss the right source. Thin-client installs (
```
gbrain init --mcp-only
```
) route through the remote brain transparently.
Today's meetings. For each meeting on the calendar:
- Search gbrain for each participant by name
- Read their pages from gbrain for compiled_truth context
- Summarize: who they are, recent timeline, relationship to you
Active deals. List deal pages in gbrain filtered to active status:
- Deadlines approaching in the next 7 days
- Recent timeline entries (last 7 days)
Time-sensitive threads. Open items from timeline entries:
- Items with deadlines in the next 48 hours
- Follow-ups that are overdue
Recent changes. Pages updated in the last 24 hours:
- What changed and why (read timeline entries from gbrain)
People in play. List person pages in gbrain sorted by recency:
- Updated in last 7 days
- Have high activity (many recent timeline entries)
Stale alerts. From gbrain health check:
- Pages flagged as stale that are relevant to today's meetings

热记忆脉冲（v0.32）。在生成任何内容之前，运行：
bash
```
gbrain recall --since-last-run --supersessions --pending --rollup --json
```
将结果整合到简报顶部的“Brain脉冲”部分：
1. 夜间已解决的矛盾 ——
```
--supersessions
```
  的输出。优先展示这些内容，因为它们是对您认知模型的最新修正。
2. 高频提及对象 ——
```
--rollup
```
  中的
```
top_entities
```
  （统计周期内事实数量排名前5的实体slug）。
3. 上次简报以来的新事实 —— 将
```
facts
```
  数组按汇总中的每个实体分组；包含
```
kind
```
  、
```
notability
```
  和
```
confidence
```
  信息。
4. 待合并提示 —— 当
```
pending_consolidation_count > 0
```
  时，标注
```
N条事实等待梦周期合并
```
  ，以便操作者决定是否在继续阅读前运行
```
gbrain dream
```
  。
```
--since-last-run
```
标志会更新
```
~/.gbrain/recall-cursors/<source>.json
```
，确保下一次简报能精准接续本次的结束点。如果通过cron作业运行此命令，请传入
```
--source <slug>
```
或显式设置
```
GBRAIN_SOURCE
```
——cron不会在您的仓库根目录启动，因此点文件解析可能无法找到正确的源。瘦客户端安装（
```
gbrain init --mcp-only
```
）会透明地通过远程brain处理请求。
今日会议。针对日历中的每个会议：
- 通过姓名在gbrain中搜索每位参与者
- 从gbrain中读取他们的页面，获取compiled_truth上下文
- 总结：他们的身份、近期动态、与您的关系
活跃交易。列出gbrain中状态为活跃的交易页面：
- 未来7天内即将到期的截止日期
- 近期动态条目（过去7天内）
时间敏感线程。来自时间线条目的待办事项：
- 未来48小时内到期的事项
- 已逾期的跟进任务
近期变更。过去24小时内更新的页面：
- 变更内容及原因（读取gbrain中的时间线条目）
重点关联人员。按更新时间排序列出gbrain中的人员页面：
- 过去7天内更新过
- 活跃度高（近期时间线条目较多）
过期提醒。来自gbrain健康检查：
- 标记为过期且与今日会议相关的页面

GBrain-Native Context Loading

GBrain原生上下文加载

Before generating any briefing, load context from gbrain systematically.

在生成任何简报之前，需系统地从gbrain加载上下文。

Before a meeting

会议前准备

For every attendee on the calendar invite:

```
gbrain search "<attendee name>"
```
-- find their brain page
```
gbrain get <slug>
```
-- load compiled truth, recent timeline, relationship context
If no page exists, note the gap ("No brain page for Sarah Chen -- consider enrichment")

针对日历邀请中的每位参会者：

```
gbrain search "<参会者姓名>"
```
—— 找到他们的brain页面
```
gbrain get <slug>
```
—— 加载compiled_truth、近期时间线、关系上下文
如果页面不存在，需标注信息缺口（"Sarah Chen无brain页面——建议补充信息"）

Before an email reply

邮件回复前准备

Before drafting or triaging any email:

```
gbrain search "<sender name>"
```
-- load sender context
Read their compiled truth to understand who they are, what they care about, and your relationship history. This turns a cold reply into an informed one.

在起草或分类任何邮件之前：

```
gbrain search "<发件人姓名>"
```
—— 加载发件人上下文
读取他们的compiled_truth，了解其身份、关注点及您与他们的关系历史。这能让您从陌生回复转变为知情回复。

Daily briefing queries

每日简报查询

Run these queries to populate the briefing sections:

```
gbrain query "active deals status"
```
-- deal pipeline snapshot
```
gbrain query "meetings this week"
```
-- recent meeting pages with insights

gbrain query "pending commitments follow-ups"

-- open threads and action items

gbrain search --type person --sort updated --limit 10

-- people in play

运行以下查询来填充简报各部分：

```
gbrain query "active deals status"
```
—— 交易管道快照
```
gbrain query "meetings this week"
```
—— 带有洞察的近期会议页面

gbrain query "pending commitments follow-ups"

—— 待处理线程和行动项

gbrain search --type person --sort updated --limit 10

—— 重点关联人员

Output Format

输出格式

DAILY BRIEFING -- [date]
========================

MEETINGS TODAY
- [time] [meeting name]
  Participants: [name] (slug: people/name, [key context])

ACTIVE DEALS
- [deal name] -- [status], deadline: [date]
  Recent: [latest timeline entry]

ACTION ITEMS
- [item] -- due [date], related to [slug]

RECENT CHANGES (24h)
- [slug] -- [what changed]

PEOPLE IN PLAY
- [name] -- [why they're active]

每日简报 -- [日期]
========================

今日会议
- [时间] [会议名称]
  参会者：[姓名]（slug: people/name, [关键上下文]）

活跃交易
- [交易名称] -- [状态]，截止日期：[日期]
  近期动态：[最新时间线条目]

行动项
- [事项] -- 截止日期 [日期]，关联 [slug]

近期变更（24小时内）
- [slug] -- [变更内容]

重点关联人员
- [姓名] -- [活跃原因]

Back-Linking During Briefing

简报中的反向链接

If the briefing creates or updates any brain pages (e.g., new meeting prep pages, updated entity pages), the back-linking iron law applies: every entity mentioned must have a back-link from their page. See

skills/_brain-filing-rules.md

如果简报创建或更新了任何brain页面（例如，新的会议准备页面、更新的实体页面），需遵循反向链接铁则：提及的每个实体必须从其页面添加反向链接。详见

skills/_brain-filing-rules.md

。

Citation in Briefings

简报中的引用

When presenting facts from brain pages, include inline citations:

"Jane is CTO of Acme [Source: people/jane-doe, updated 2026-04-01]"
This lets the user trace any claim back to the brain page and assess freshness

在展示来自brain页面的事实时，需包含内联引用：

"Jane是Acme的CTO [Source: people/jane-doe, updated 2026-04-01]"
这能让用户追溯任何声明的来源brain页面，并评估信息的时效性

Anti-Patterns

反模式

Briefing without brain queries. Never generate a briefing from memory alone; always query gbrain for current data.
Uncited facts. Every claim must include
```
[Source: slug, updated DATE]
```
. A fact without a citation is unverifiable.
Stale context presented as current. If a page hasn't been updated in 30+ days, flag the staleness explicitly rather than presenting it as fresh.
Modifying brain pages unprompted. The briefing is read-only by default. Do not create or update pages unless the user explicitly requests it.
Ignoring coverage gaps. When a meeting participant has no brain page, say so. Silence about gaps hides ignorance.

未查询brain的简报。绝不能仅依靠记忆生成简报；务必查询gbrain获取最新数据。
无引用的事实。每个声明都必须包含
```
[Source: slug, 更新日期]
```
。无引用的事实无法验证。
将过期上下文作为当前内容展示。如果页面30天以上未更新，需明确标记其过期状态，而非当作新鲜内容展示。
未经提示修改brain页面。默认情况下简报为只读模式。除非用户明确要求，否则不得创建或更新页面。
忽略信息缺口。当会议参与者无brain页面时，需明确说明。对信息缺口保持沉默会掩盖认知盲区。

Tools Used

使用的工具

Search gbrain by name (query)
Read a page from gbrain (get_page)
List pages in gbrain by type (list_pages)
Check gbrain health (get_health)
View timeline entries in gbrain (get_timeline)

通过名称搜索gbrain（query）
从gbrain读取页面（get_page）
按类型列出gbrain中的页面（list_pages）
检查gbrain健康状态（get_health）
查看gbrain中的时间线条目（get_timeline）