weekly-report-writer

Original：🇨🇳 Chinese

Translated

This skill drafts weekly reports by synthesizing the progress documented in the Obsidian vault. It is suitable for scenarios where users want to generate weekly summaries based on recently created files, previous reports, and project background documents.

2installs

Sourcecafe3310/public-agent-skills

Added on2026-03-06

NPX Install

npx skill4agent add cafe3310/public-agent-skills weekly-report-writer

SKILL.md Content (Chinese)

View Translation Comparison →

Weekly Report Writer (Weekly Report Writing Assistant)

Overview

This skill automates the creation process of weekly/biweekly reports. It finds all relevant documents within a specified date range, reads their content, and synthesizes information based on templates or a hierarchical structure. It pays special attention to project continuity (tracking task status from the previous report) and content depth (traceability via links).

When to Use

When the user requests:

"Write my weekly report" or "Draft a summary of this week".
Summarize progress between two dates.
Create a new report based on the previous report and a set of new documents.

This skill is especially effective in document knowledge bases, such as Obsidian vaults.

Workflow

Follow this workflow to generate reports.

Step 1: Collect User Input

Before starting, confirm the following information with the user:

Start date: The start of the reporting period.
End date: The end of the reporting period.
Whether repository filenames include date prefixes: Confirm the file naming convention (e.g.
```
YYYY-MM-DD-description.md
```
).
Previous report path: The file path of the last weekly report. This is critical for tracking ongoing tasks.
Vault directory: The root directory of the document repository (e.g. their Obsidian vault path).
(Optional) Report template path: If the user has a specific template, provide its path.
(Optional) Project background path: The path of the document that summarizes all projects of the larger organization (if available).

Step 2: Locate Documents

Log lookup: Use the

vault directory

and date range provided by the user to find all Markdown files that match the date range.

Step 3: Confirm File List with User

Present the list of found files (logs + detected templates) to the user. Ask the user to confirm the list and provide feedback on any files that should be focused on or skipped. Generally, excerpted documents, original voice transcription logs, etc. should be skipped; Daily work summaries, meeting minutes, project updates, etc. should be focused on.

Step 4: Read, Deep Traceability and Synthesis

After confirmation, read the content of all files. Pay attention to the following during the process: Several notes:

Link tracking: When reading daily summaries/logs, if you encounter a "key item" pointing to another document that includes
```
[[document link]]
```
, you should use the tool to read the linked document. The reason is that daily summaries are usually just one sentence ("Completed..."), while high-quality weekly reports require specific deliverables, methods and data from the source document.
Information synthesis: During the process, pay attention to the following when synthesizing information:
- Track projects in the "previous report" and highlight their progress.
- Identify to-do (
```
🟥
```
  ), completed (
```
🟩
```
  ), in progress (
```
🟨
```
  ) and new ideas (
```
💡
```
  ), and mark each item.
- To-do inheritance: Any
```
🟥
```
  (to-do) or
```
🟨
```
  (in progress) items in the previous report must be carried over to the "to-do/backlog" section of the new report, unless they are already included in the new report and clearly marked as
```
🟩
```
  (completed).

Step 5: Draft Report (Hierarchical Output)

Draft the report. If a specific template is found in Step 2, follow it strictly. Otherwise, use the standard hierarchical structure:

Part 1: Personal Status Sync

This is a personal log.
Audience: Self / Knowledge base.
Content: Detailed technical background, links to in-depth documents, personal thoughts (
```
💡
```
) and specific status updates. Keep the
```
[[Wiki Link]]
```
format.

Part 2: Team External Sync

This is the "part you are responsible for" in the team report.
Audience: Managers / Team members.
Content: High-level summary.
- Key progress: What was delivered? (Focus on value).
- Risks/Blockers: What support is needed?
- Next steps: What are the short-term plans?
- Mentions: Use the
```
@user
```
  format to mark responsible persons.

Report filename: Use the filename convention of the document library, and keep it consistent with the style of previous report filenames.

Step 6: Gap Analysis

After the draft is generated, conduct a round of "gap check" for high-value deliverables. Remind the user to "check the draft, and supplement if there are omissions". Then edit and update the draft according to user feedback.