weekly-report-writer

Generate structured weekly progress reports from Obsidian Markdown notes.

248|30|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/cafe3310/public-agent-skills --skill weekly-report-writer-cafe3310
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weekly-report-writer
Source: https://github.com/cafe3310/public-agent-skills/tree/main/skills/weekly-report-writer
Command: npx skills add https://github.com/cafe3310/public-agent-skills --skill weekly-report-writer-cafe3310

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill solves the difficulty of manually consolidating scattered work notes, previous reports, and project context into a consistent weekly summary.

Core Features & Use Cases

  • Document Synthesis: Collects and combines dated Markdown notes, previous reports, templates, and project background documents into a structured report.
  • Progress Tracking: Preserves ongoing tasks, completed items, risks, and ideas by tracing project continuity across reporting periods.
  • Use Case: A developer using an Obsidian vault can generate a detailed personal log and a team-facing weekly update from daily notes and prior summaries.

Quick Start

Use the weekly-report-writer skill to create my weekly report from my Obsidian notes between the specified start and end dates.

Frequently Asked Questions about weekly-report-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a weekly report from scattered Obsidian notes?

To generate a weekly report from Obsidian notes, you need a tool that traces linked notes, discovers dated documents, and aggregates task statuses to synthesize a continuity-aware summary from your specified date range.

What is the best way to consolidate daily Markdown notes into a project status summary?

Consolidating daily Markdown notes into a project status summary involves tracing document continuity across periods, preserving completed items and risks, and applying template handling to structure the aggregated background context.

Can I track ongoing tasks and risks across previous weekly reports in a Markdown vault?

Yes, tracking ongoing tasks across previous weekly reports in a Markdown vault requires tracing project continuity to preserve incomplete items, risks, and ideas while generating a new periodic update.

Does weekly report generation work with linked-note tracing in knowledge management workflows?

Weekly report generation works with linked-note tracing by discovering connected documents within a knowledge base, combining project background context with dated notes to produce continuity-aware structured summaries.

How to create a team-facing weekly update from personal Obsidian daily logs?

Creating a team-facing weekly update from personal Obsidian logs requires synthesizing daily notes and prior summaries, aggregating task statuses, and separating detailed personal logs from broader team communication.

What do I need to prepare before automating weekly report generation from a knowledge base?

Before automating weekly report generation, you need dated Markdown notes, previous reports, and project templates organized within your knowledge base to enable document discovery and continuity-aware status aggregation.