Automatic Weekly Report Generation: Every Friday 17:00, automatically summarize and hand it in
💡 One-sentence summary: Use WorkBuddy to build a weekly report production line that delivers on schedule — gather a week's materials, compose them in a three-part structure, and deliver automatically every Friday 17:00.
Searching for "AI weekly report" mostly turns up templates and sample essays, but what really gives people headaches is never "how to phrase it"—it's "what did I actually do this week": commits are in the repo, meeting conclusions are in the minutes, data is in spreadsheets. This lesson breaks down the WorkBuddy weekly report scenario: first let it read your week's materials, manually run a submittable version, then configure it as a scheduled task in the official scenario—automatically summarizing every Friday 17:00—and finally choose the delivery method; you only review and forward.
This is Lesson 1 of Route 1 in "Scenario Practice," based on WorkBuddy v5.9.3, with content drawing on the official "10 Getting-Started Tips," the "Scheduled Tasks" feature documentation, and practical cases. It is also the template lesson for the whole column: the "scenario prompt + scheduled task" combination, once learned, can be applied to recurring tasks like daily reports and briefings.
- The complete mechanics of scheduled tasks (three sources, 7 repeat rules, run records) are covered in 3.3 Scheduled Tasks; this lesson only covers how to use them for the weekly report scenario
- Can't write prompts clearly? Go back to 3.1 Requirements-Asking Methodology to review the three-element formula
What You Can Do After This Lesson
- Write a weekly report prompt complete with all three elements, consolidating a week's code commits, meeting minutes, and spreadsheet data into a structured weekly report (this week's progress / risks / next week's plan)
- First run it manually and confirm the output is submittable, then configure it as a WorkBuddy scheduled weekly report task for every Friday 17:00—after that, it delivers automatically on schedule
- Know how to send the weekly report out: push to WeCom, upload to Tencent Docs and convert to an online document, or send the file directly to WeChat
- When a task doesn't run, check the run records to locate the cause (computer offline, stuck waiting for confirmation, connector not authorized) instead of just waiting
Why Use WorkBuddy Instead of Web-Based AI?
| Capability | Web-Based AI | WorkBuddy |
|---|---|---|
| Get a week's materials | ❌ Dig through records yourself, copying and pasting piece by piece into the chat box | ✅ Directly reads commit records, minutes, and spreadsheets in the workspace |
| Scheduled execution | ❌ You have to remember to ask every Friday | ✅ Scheduled tasks run automatically on time, and the "Weekly Work Report" template is built in |
| Deliverable file output | ❌ Just a block of text in the chat box, formatting is on you | ✅ Generates a document output that can be uploaded to the cloud or shared to WeChat/WeCom |
| Results proactively delivered | ❌ You have to go back and dig through the conversation to copy | ✅ Can be pushed to WeCom, and the App also receives a "Scheduled Task:" notification |
| Remembers your format requirements | ❌ You have to re-describe the template every time | ✅ The prompt is stored in the scheduled task—configure once, use every week |
Your Current Struggles
- Friday 17:00 is the busiest moment of the week: rushing work, aligning, replying to messages—and you still have to save brainpower to write the weekly report
- Figuring out what you did all week relies entirely on memory: digging through chat logs, repos, spreadsheets, and after half an hour you still haven't squeezed out the first line
- Frantically searching "AI writes my weekly report" at the last minute yields template-speak like "completed various tasks this week," which your boss sees through at a glance
- You finally get a version written smoothly, and next week you start from scratch—the format requirements have to be explained all over again
When to Use This Technique
When you need to:
- Submit a weekly report or daily report on a fixed schedule (weekly, daily, or biweekly)
- Consolidate a week's scattered materials—commit records, meeting minutes, data spreadsheets—into a structured report
- Generate the weekly report automatically on schedule even when you're away from the computer around Friday's end of day
And you don't want to:
- Personally dig through a week's records and piece together words every Friday
- Repeat the same format requirements every week
- Forget to write the weekly report and get @-mentioned by your boss in the group chat on Monday
🎒 Preparation Before Starting
- Studied 3.3 Scheduled Tasks: Let WorkBuddy Work on Its Own on Time—this lesson uses its creation, permissions, and run records directly without repeating them
- Can write prompts using the three-element formula from 3.1 Requirements-Asking Methodology: what to do + what you have + how it should be
- WorkBuddy client is logged in with credits remaining: every scheduled task run consumes credits, and document-summarization tasks consume more than simple reminder tasks
- Know where your weekly report materials are: local directories (e.g., D:/Project/), or authorized connectors like Tencent Docs
- 15 minutes; ideally follow along and set it up before Friday so you can receive your first automatic weekly report this week
Follow Along
Step 1: Create a "Weekly Report" task and gather a week's materials into the workspace
Why: Slow weekly report writing is usually not a writing-skill problem—it's scattered materials. The official advice when discussing workspaces is to "create separate spaces by task type, e.g., invoice organizing, weekly reports, photos to process"—give the weekly report a fixed place first.
Steps:
- Create a new task, click "Select Workspace" at the bottom-left of the input box, and set the directory to where your materials are (e.g., D:/Project/).
- Meeting notes and data tables scattered elsewhere this week—just drag them into the conversation—up to 50 files, with support for Word, Excel, PDF, Markdown, and TXT.
- To cite a specific file by name, use @ in the task description to reference it.
You should see: the new task appears in the task list on the left, with the workspace pointing to the materials directory; WorkBuddy reads the files from there during execution.
- My workspace points to the weekly report materials directory, and it can reach all the materials that need to be summarized this week
Step 2: First manually have the AI write the weekly report and get the first version working
Why: The first item of the official usage advice—after creating a new task, do a trial run first to confirm the results meet expectations before scaling up the execution frequency. If you go straight to scheduling and the prompt goes off track, you burn credits for nothing every week.
Operation: Send the official weekly report scenario prompt as-is (replace the path with yours):
Summarize all code commit records under D:/项目/ this week, categorize them by module, and count each module's
number of commits and main changes, then generate a concise weekly report.This is the original text of the automation scenario from the official "10 getting-started tips," ready to use for teams that manage code. After the first version comes out, use another round of conversation to lock down the structure—the three-part format comes from the official weekly report template:
Organize the weekly report into three sections: this week's progress, risks, and next week's plan.
List progress by module, describe risks with their impact and responses, and specify items and timing for next week's plan.You should see: a weekly report document appears in the "Artifacts" tab of the results area, structured in three sections—this week's progress, risks, and next week's plan; the "Workspace Files" tab shows where it was saved to disk.
💡 This is the unique value of WorkBuddy
A web-based AI can only access what you manually copy and paste; WorkBuddy directly reads the week's files in the workspace—commit records, notes, tables—and then summarizes them into a document. According to third-party testing, tossing a few reference materials to WorkBuddy yields a first draft in ten minutes (source: a hands-on article from the Tencent Cloud community, not an official statement).
- I manually ran a three-part weekly report, read it through, and confirmed the content and structure are deliverable
Step 3: Configure the prompt as a scheduled task for every Friday at 17:00
Why: A successful manual run only solves "writing it well"—a scheduled task solves "on time." Tip 9 of the official 10 tips is "make good use of automation and let WorkBuddy keep working on its own." Weekly reports happen to meet the official criteria for automation: highly repetitive, clear rules, no real-time human intervention needed.
Operation (choose one of three; the first two are the most reliable):
Option A (recommended): Create from a template
- Go to "Scheduled Tasks" in the left navigation bar, click the dropdown arrow next to "New" in the top right corner, and select "New from Template."
- Select the "Weekly Work Report" template—the edit window will automatically fill in the name, prompt, and execution time.
- Replace the prompt with the polished version from Step 2, adjust the time as needed, and click OK.
Option B: Create manually
Click "New" to create manually, paste the prompt from Step 2 into the "Prompt" box, and then configure each item:
| Configuration item | Value used in this lesson | Description |
|---|---|---|
| Repeat | Weekly → check Friday | Weekly/bi-weekly allows checking multiple weekdays in one rule |
| Time | 17:00 | The time of the official weekly report scenario |
| Workspace | Materials directory (e.g., D:/项目/) | The task reads and writes files here |
| Permissions | Full access | Unattended execution without confirmation prompts (officially recommended) |
| Push messages to WeCom | As needed (see Step 4) | Only supports WebSocket long connections |
Note: You can only click OK after the name and prompt are filled in.
Option C: Create with a single sentence
The lazy approach—according to the official instructions, you can directly describe a recurring need in a normal conversation, and WorkBuddy will likewise create a scheduled task for you:
Help me create a scheduled task: every Friday at 17:00, summarize all code commit records under D:/项目/ this week,
categorize them by module, count each module's number of commits and main changes, and generate a concise weekly report,
covering three sections: this week's progress, risks, and next week's plan.You should see: a new card appears in the scheduled task list showing the execution rule and the next execution time—check it against the card, and only wrap up once the weekday and time are correct.
- My scheduled weekly report task is set up, and the next execution time on the card is this Friday 17:00
Step 4: Choose a delivery method—push, upload, or share
Why: The weekly report artifact is generated in your computer's workspace, and your boss won't come to your computer to read it. Three ways to send it—choose based on your reporting habits:
| Delivery method | How to operate | Best for |
|---|---|---|
| Push to WeCom | Turn on the "Push messages to WeCom" switch in the edit window | The team receives reports in WeCom |
| Upload to Tencent Docs | Artifact card "⋯" → Upload to cloud → Tencent Docs | The weekly report should become a shared team document |
| Send file to WeChat/WeCom | Preview the artifact → share icon in the top right corner → Send file | Send directly to a specific person |
Two details:
- WeCom push only supports WebSocket long connections; after binding the bot, be sure to send it any message in WeCom to complete the final confirmation, otherwise the results can't be pushed out.
- When uploading to Tencent Docs, a Markdown artifact is created as a smart document by default, with content and formatting consistent with the original file, and it can be co-edited afterwards.
You should see: after the task completes, you receive the weekly report in your chosen channel—a WeCom message, an online document link, or a WeChat file.
- I selected at least one delivery method and completed its required prerequisite action (e.g., messaging the bot)
Step 5: Accept the first automatic run and learn to read the run records
Why: Being configured doesn't mean everything's fine. You should verify the first automatic run, and know where to look when problems occasionally arise later.
Steps:
- Don't want to wait until Friday: click the "Run" button on the task card to execute immediately once, without affecting the original schedule.
- After Friday 17:00 (or after the trial run), click the task card to enter the run page: past runs are displayed on a timeline, and the page opens with the artifacts of the most recent run by default.
- If something goes wrong, go to the "Run Records" tab: click a failed record to see the cause and handling suggestions. Failure causes listed officially include: connector not authorized, login expired, computer offline causing a missed execution time, model queue retries exhausted, etc.
You should see: every run has a status, run time, and duration; for a task whose last run failed, a red failure indicator appears next to the card title, and hovering shows the cause. Model queue failures aren't immediately declared dead—they're automatically re-queued and retried, and only marked as failed after multiple retries still fail.
💡 Let the results come to you
On the desktop app, enable "Settings > General > Scheduled Task Artifact Notifications" so a system notification reminds you when an artifact is generated; once the WorkBuddy app is linked to the current computer, the app also receives notifications when a scheduled task completes, awaits confirmation, or fails, with titles starting with "Scheduled Task:".
- I've looked at at least one run record and can say where to check the cause when a run fails
📋 Magic Prompt
How do you write a weekly work report that isn't just a running log? First lock down the structure (this week's progress, risks, next week's plan), then let the AI fill in real substance. The two prompts below cover both the "programmer version" and the "general version," with placeholders marked in 【】—replace them with yours and they're ready to run; for the version that creates a scheduled task with a single sentence, see Step 3 Option C.
📝 Weekly Code Commit Report (Programmer Version)
Expected result: reads the week's commit records from the local project directory, tallies them by module, and produces a three-part weekly report ready to post directly in a group chat.
## Role
You are the team's technical lead, submitting a concise weekly report to management every week.
## Task
Summarize all code commit records under 【project directory, e.g., D:/项目/】 this week, categorize by module,
Count the number of commits and main changes for each module, and generate a concise weekly report.
## Input Information
### Required Fields
- Project directory: [local path, e.g., D:/项目/]
- Reporting period: [e.g., Month 11 Day 2 to Month 11 Day 6]
### Optional Fields
- Excluded directories: [e.g., dependencies, build output directories?]
- Supplementary materials: [paths to this week's meeting notes, data spreadsheets?]
## Output Specification
- A Markdown document, in three parts: this week's progress, risks, next week's plan
- Progress grouped by module: module name + number of commits + a one-line summary of the main changes
## Constraints
- ✅ Only summarize commit records that actually exist; do not fabricate workload
- ✅ Keep the whole text under 500 characters, ready to send directly to your manager
- ❌ Do not paste large chunks of code diffs
- ❌ Do not use uninformative phrasing like "completed a large amount of work"📝 General Work Weekly Report (Materials-Summary Edition)
Expected result: non-coding roles can use it too — it consolidates a week's worth of notes, spreadsheets, and documents into the same three-part weekly report.
## Role
You are my office assistant, skilled at organizing scattered materials into a weekly report your manager can grasp at a glance.
## Task
Read the materials I provide for this week and consolidate them into a work weekly report.
## Input Information
### Required Fields
- Materials: [paths to meeting notes, data spreadsheets, project documents, or files dragged in directly]
- Reporting period: [e.g., Month 11 Day 2 to Month 11 Day 6]
### Optional Fields
- Report audience: [e.g., direct manager / department weekly meeting?]
- Focus areas: [e.g., progress on a particular project?]
## Output Specification
- In three parts: this week's progress, risks, next week's plan
- Group progress by project or item, with one sentence per entry stating the outcome clearly
## Constraints
- ✅ Every progress entry can be traced back to its source material
- ✅ For risks, state the impact clearly and suggest a response
- ❌ Do not invent items not present in the materials
- ❌ Do not use vague phrasing like "continuing to push forward"Checkpoints ✅
- I first ran a weekly report manually end to end and confirmed the three-part structure and content were submittable before setting up the schedule
- The scheduled task's repeat rule is "Weekly · Friday · 17:00", and the card shows the next execution time
- For the unattended task I chose Full Access permission, and the prompt contains no dangerous actions such as file deletion or financial operations
- I know that during local task execution I must not shut down the computer or exit the client — at that Friday 17:00 moment the machine has to be online
- I have chosen one delivery method and verified it works: WeCom push / upload to Tencent Docs / send file to WeChat
- When something goes wrong, I check the run history for the officially listed failure causes instead of deleting the task and rebuilding it
Pitfall Reminders
❌ Setting up a schedule without a test run burns credits for nothing every week
Symptom: the weekly report auto-generated on Friday has the wrong structure and hollow content, and it took three weeks of runs to notice.
Cause: the prompt was never validated. Every scheduled-task run consumes credits, and document-summarization tasks consume more than simple reminder tasks; an off-target prompt wastes one run on schedule every week.
Correct approach: the official recommendation is to click Run for a trial run right after creating a task, confirm the result meets expectations, and only then scale up the execution frequency. The manual end-to-end run in Step 2 is exactly this.
❌ Friday 17:00 arrives, but the task doesn't run
Symptom: no weekly report is generated at the scheduled time, and the run history shows a failure or no record at all.
Cause: two most common ones — ① the computer was shut down or the client exited during local task execution; "computer offline causing a missed execution time" is one of the officially listed failure causes; ② the permission was left at the default, the task got stuck waiting for confirmation, and you weren't at the computer.
Correct approach: for local tasks, make sure the computer and client are online during the execution window; for unattended tasks, choose Full Access permission. If you truly need it to run while the machine is off, use a cloud task — but the cloud sandbox cannot access local files, so the prompt must not contain local paths like D:/项目/.
❌ The prompt only says "help me write a weekly report"
Symptom: the output is a generic template like "completed some work this week, will keep trying next week" that would work with anyone's name filled in.
Cause: two of the three elements are missing — "what materials" and "what quality" — it doesn't know where the materials are or what structure is required, so it can only make things up.
Correct approach: complete it using the three-element formula — what to do (summarize this week's materials into a weekly report), what materials (material paths or dragged-in files), what quality (three-part structure + word-count constraint). Just fill in the placeholders in the magic prompt above and it's ready to use.
❌ WeCom push is enabled, but the weekly report never arrives
Symptom: the task clearly ran successfully, but nothing is received in WeCom.
Cause: after binding the bot, no message was sent to it in WeCom to complete the final confirmation, so the scheduled task can't find a push recipient; or the assistant uses a URL callback connection — scheduled-task push only supports WebSocket persistent connections.
Correct approach: following the guide, send the bot a message and then click "Sent"; for URL callbacks, unbind and reconnect as instructed. Also note the official statement: a push failure does not affect the task's own execution — the weekly report output is still in the workspace.
Advanced Tips (Optional)
🔧 Tencent Docs weekly report template. After authorizing the Tencent Docs connector, you can use the official wording directly: "Create a weekly report template in Tencent Docs containing three parts: this week's progress, risks, and next week's plan" — the weekly report lands directly in an online document for team collaborative editing. For connector setup and more commands, see C3 Tencent Docs Connector.
🔧 Set up daily, biweekly, and monthly reports together. There are 7 repeat rules: interval, one-time, daily, weekly, biweekly, monthly, yearly; the official automation examples even include "automatically generate a work daily report every day at 9:00". Note that automated tasks have quotas (starting from 3 on the trial edition; see 2.6 Credits and Pricing); configure all execution dates for the same task in a single rule rather than splitting them into multiple tasks.
🔧 If the materials aren't local, connect a connector first. If the weekly report materials are online (Tencent Docs, QQ Mail, etc.), complete authorization in the connector first, and the prompt can then reference those sources; the connector's own reads and writes don't consume credits — credits are consumed when WorkBuddy understands and summarizes the external data. For a full overview of connectors, see 5.2 Connectors and MCP.
Lesson Summary
✅ AI weekly reports in three steps: pull materials into the workspace → run a three-part weekly report manually end to end → set it up as a scheduled task for every Friday 17:00.
✅ Use the official weekly report template for the structure: this week's progress, risks, next week's plan — fix the structure first, then fill in the materials, and the rambling log disappears.
✅ Test-run before scheduling: the first item in the official usage recommendations; an off-target prompt on a schedule means wasting credits on time every week.
✅ Choose Full Access for unattended tasks; during local task execution, do not shut down the computer or exit the client.
✅ Three delivery options: WeCom push (WebSocket persistent connection only), upload to Tencent Docs (Markdown is created as a smart document by default), send file to WeChat.
✅ Check the run history on failure: connector not authorized, login expired, computer offline missing the execution time, model queue retries exhausted.
Key configuration recap:
| Configuration item | Value used in this lesson | Description |
|---|---|---|
| Repeat + Time | Weekly · Friday · 17:00 | the time for the official weekly report scenario |
| Workspace | materials directory (e.g., D:/项目/) | local tasks read and write files here |
| Permission | Full Access permission | unattended runs don't stall on confirmation |
| Message Push | WeCom (as needed) | persistent connection only; send the bot a message first |
| Prompt | three-part weekly report structure | stored in the task, configured once and used weekly |
Next Lesson Preview
The most common material for weekly reports is meeting notes — the next lesson turns that into a one-stop pipeline too. In the next lesson you'll learn A2 Meeting Notes: A One-Stop Pipeline from Recording and Transcription to Structured Notes.
You will learn:
- The complete workflow of transcribing a recording first, then organizing it
- The official meeting-notes prompt: meeting topic, key conclusions, action items, owners, deadlines
- Supported formats and file limits for audio-to-text, and per-minute billing rules