weekly-debrief

Original：🇨🇳 Chinese

Translated

Generate a weekly work report for a given week: aggregate 7 daily reports into trends and reflection, save as local Markdown. Only read the daily report md, never touch the original transcript. Triggered when the user says '週報', '這週做了什麼', 'weekly summary', or '補上週的週報'. ⚠️ Here '週報' means personal work review; content-type '週報' (newsletter/social post) for external release is not covered by this skill. Requires daily-debrief and mission-log to be installed together (missing daily reports will be auto-generated first). English triggers: "weekly debrief", "weekly summary", "wrap up my week", "backfill last week".

15installs

Sourcetingyulu/myr2d2

Added on2026-09-13

NPX Install

npx skill4agent add tingyulu/myr2d2 weekly-debrief

SKILL.md Content (Chinese)

View Translation Comparison →

/weekly-debrief — Weekly Report

Condense a week of daily reports into one page: main threads, trends, reflection. Only read the 7 md files under

journal/daily/

— cheap, fast, and unaffected by transcript retention.

🤖 R2-D2 moment: a single mission is one record; a campaign is what seven records look like — the one who can see supply-line problems is always the latter.

Usage

/weekly-debrief [week]

— no argument = current week (up to now);

last

= previous week;

YYYY-Www

= specified week; any

YYYY-MM-DD

= the week containing that day. Weeks start on Monday.

Actions

Inventory the 7 daily report files for that week (
```
journal/daily/
```
):
- If a day is missing and still within the transcript retention window → generate it first via the /daily-debrief flow (self-healing);
- If there is genuinely nothing to backfill → mark "X/X no record (beyond retention)" in the weekly report, don't pretend it's fine.

Write the weekly report, based only on the 7 daily reports, with the following template:

markdown

# YYYY-Www 週報(MM-DD ~ MM-DD)
## 本週主線
- <跨多日的工作線,含起訖與結果>
## 數字與趨勢
總 sessions/tokens|最花 token 的專案|與上週比(若上週檔在)
## Reflection
- 這週最值得留的一課:
- 重複出現的卡點:
- 下週優先:

Save and verify: write to
```
journal/weekly/YYYY-Www.md
```
, then read it back to confirm.
Also write a notification digest
```
journal/weekly/YYYY-Www.digest.txt
```
(plain text, zero markdown, same format as step 5 of daily-debrief, but with the sessions list replaced by "one line per day").
Post-generation action (optional): same as daily-debrief, if
```
config.env
```
exists execute
```
JOURNAL_POST_CMD
```
, put the link at the very top of the message.
Report in conversation: same as step 7 of daily-debrief, post the full report URL as a bare link.

Iron Rules

✅ Only read daily report md: never touch raw transcripts or raw skeleton; if a daily report is wrong, fix the daily report first, then rerun the weekly report.
🔁 Idempotent: any week can be regenerated; self-healing gaps takes priority over erroring out.
🚫 Two points make a trend: if last week's file doesn't exist, don't write "compared to last week", don't fabricate a baseline.