Agent Skills
› mohitagw15856/pm-claude-skills
› delta-briefing
delta-briefing
GitHub用于生成差异化的周期性简报，避免内容重复。通过对比上次状态与当前数据，聚焦新增、变更和已解决事项，并输出机器可读的状态记录供下次比对使用。
触发场景
需要制作周报或月报时
报告内容开始重复时
设置定期监控摘要时
安装
npx skills add mohitagw15856/pm-claude-skills --skill delta-briefing -g -y
SKILL.md
Frontmatter
{
"name": "delta-briefing",
"description": "Make a recurring brief report what changed since the last edition instead of restating everything. Use when a weekly or monthly report keeps repeating itself, when setting up a scheduled monitor or digest, or when asked to make a recurring update delta-aware. Produces a changes-first brief plus the state record the next run will diff against."
}
Delta Briefing Skill
The failure mode of every recurring report is that edition 6 reads like edition 5. This skill structures a recurring brief around the delta: read the last edition's state, diff the world against it, lead with what changed, and save state for the next run.
What This Skill Produces
- A changes-first brief: new / changed / resolved / unchanged-but-watched
- A state record (compact, machine-readable) that the next edition diffs against
- An explicit "nothing changed" edition format — short, honest, and still useful
Required Inputs
Ask for (if not already provided):
- The brief's subject and audience (competitive landscape, product metrics, account health…)
- The previous edition or state record — if none exists, this run is the baseline: say so in the output and produce the first state record
- Current sources for this cycle
- Where state lives between runs (a file next to the brief, a Brain folder — see BRAIN.md if using this library's memory)
Delta Method
- Load last state. Parse the previous state record (or previous edition if that's all there is). List the items it tracked and their status.
- Re-observe. Gather this cycle's facts from the sources — independently of the old state, so removals are caught too.
- Diff into four buckets:
- New — present now, absent last time
- Changed — tracked before, materially different now (state what moved, old → new)
- Resolved / gone — tracked before, no longer present or no longer a concern
- Watching — unchanged but still worth tracking (compressed to one line each)
- Judge materiality. A delta makes the brief only if the audience would act differently knowing it. Trivia goes to the state record, not the brief.
- Write state for next time. Every tracked item, its current status, the date, and the sources read.
Output Format
[Brief name] — [date] (edition [n], previous: [date])
TL;DR: [1-2 sentences: the most consequential delta, or "no material changes"]
New since last edition
- [item] — [why it matters, one line]
Changed
- [item]: [old] → [new] — [implication]
Resolved
- [item] — [how it closed]
Still watching (one line each)
- [item] — [status]
State record (for the next run)
{ "edition": n, "date": "YYYY-MM-DD", "sources": ["..."],
"items": [ { "id": "...", "status": "...", "note": "..." } ] }
If nothing material changed: say exactly that in three lines — TL;DR ("no material changes"), what was checked, next edition date. Do not pad.
Quality Checks
- The brief opens with the delta, not with background the audience read last time
- Every "Changed" item shows both the old and the new value
- Removals were checked by re-observing, not just re-confirming last edition's list
- A state record exists at the end, complete enough that the next run needs no other memory
- The baseline edition (no previous state) is labelled as a baseline, not presented as a delta
Anti-Patterns
- Do not restate unchanged items at full length — one line in "Still watching" or nothing
- Do not fabricate a delta to make a quiet cycle look productive — "nothing changed" is a valid, valuable edition
- Do not diff against memory or vibes — only against the stored state record
- Do not let the state record and the brief disagree — the record is written from the brief's facts
- Do not track everything forever — items resolved two editions ago leave the state record
版本历史
- a38bc30 当前 2026-07-05 11:33
