Weekly Report Automation: Let Grok Bot Draft Every Friday

Work traces from GitHub, documents, calendar and todos → a structured weekly draft → human review before sending

Who

Solo founders or small-team leads who need to report progress weekly to themselves, partners, or community

You get

Every Friday, auto-collect traces and output a structured weekly draft; human only trims, adds reasoning, and final-approves

You need

Steps

1. Set up the routine

   Configure a scheduled trigger in grok-bot for every Friday. Select data sources to connect (GitHub, docs, calendar, todos), granting read-only permissions only—no write or email-sending access. Set the trigger to a fixed time each Friday.

2. Collect this week's traces

   List this week's work traces by source: from GitHub, merged PRs and closed issues; from docs, newly created or modified titles; from calendar, meeting titles without attendees; from todos, completed and deferred items. Attach an accessible link to each trace.

3. Compare with last week's plan

   Read the 'next week plan' list from last week's report and compare item by item with actual progress this week. Mark each as: completed, partially completed, or not done.

4. Generate the draft

   Feed the collected traces and comparison results into the prompt below to have grok-bot output a structured weekly draft. Save the output to out/weekly-{{date}}.md.

   Execution prompt · Source text。grok-bot conversation input to generate weekly draft

   Copy prompt

   你是 {{名字}} 的周报助理。现在是 {{日期}}，请整理本周（周一到今天）的进展。
   数据源：{{数据源列表}}；上周周报：{{上周周报路径}}。
   
   按下面结构输出，每条事实附链接，没有链接的不写：
   1. 本周完成（最多 5 条，按影响排序）
   2. 上周计划对照：每条标 完成 / 部分 / 未做，未做的写一句原因（不知道原因就写「待补」）
   3. 卡点（需要别人帮忙的）
   4. 下周计划（最多 3 条）
   
   规则：
   - 不写营收、用户数、客户名等经营与隐私信息
   - 不夸大，不写「大幅提升」这类没有数据支撑的词
   - 读者是 {{读者}}，按这个读者决定写多细

5. Human review and send

   Manually review the draft: remove content that should not be external, add reasoning for editorial decisions, check for private information (names, client names), confirm no revenue figures or internal paths before sending. If this week's traces are fewer than 2 items, write only 'No substantial progress this week' instead of fabricating content.

You are a weekly report automation setup assistant. The user wants to follow the recipe at https://github.com/sit-in/awesome-grokbot-playbooks/blob/main/examples/weekly-review.md to build a grok-bot workflow that auto-generates a weekly report draft every Friday. First confirm: 1) the user's prepared list of data sources; 2) where last week's report is stored; 3) who the reader is (self/partner/community); 4) grok-bot access permissions and scheduled trigger capability. Only proceed to configuration after confirmation.