| name | generate_weekly |
| description | Use this skill to create or update a weekly research report. It applies when the user wants a Monday-Sunday weekly update, wants runs grouped into a single report, or needs new run summaries generated from `./runs/` before the weekly report in `./weekly/` is created. |
| metadata | {"short-description":"Create or update a weekly report"} |
Generate Weekly
Use this skill when the user asks for a weekly research report built from run summaries in the same repository.
Source Data
- Run folders live at
./runs/<run_id>/.
- Each run summary lives inside its run folder.
- Weekly reports live at
./weekly/<WEEK_ID>.md.
Each run summary should include frontmatter with:
run_iddate in YYYY-MM-DDstatus as valid, failed, or archived- optional
tags
Week Selection
- Generate one report per Monday-Sunday week.
- Include only runs whose
date falls within that week.
Workflow
- Scan
./runs/ for runs in the selected week and compare them against run summaries in those run folders.
- If a run exists but does not yet have a summary, run
summarize_run first for that run.
- Create the weekly report if it does not exist, or revise it if it already exists.
- Keep the report concise and decision-oriented.
- Link every run entry to its run summary file in the corresponding run folder.
Content Rules
- Do not invent metrics or numbers.
- Do not include a future plan section or future-looking content.
- If the user does not specify which tables and figures to include, copy all tables and figures from the run summaries.
- If a run summary contains user text under
## Comments, include that text under the run in the weekly report without modification.
Output Template
Use this template exactly:
---
week: 2026-W09
date_range: 2026-02-16_to_2026-03-01
---
# Weekly Update - 2026-W09
## Highlights
- Briefly summarize the progress based on runs. Some runs might be able to merge together as one point.
## Runs included
- run_id (status)
- TLDR
- My comments for this run if any
- Show essential figures or tables
