daily-progress

Automate daily progress logging and sync Plan/Docs into an Obsidian Vault.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/leessju/claude-skills --skill daily-progress
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daily-progress
Source: https://github.com/leessju/claude-skills/tree/main/daily-progress
Command: npx skills add https://github.com/leessju/claude-skills --skill daily-progress

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually logging daily progress for multiple projects and keeping Plan/Docs in sync with an Obsidian Vault is error-prone and time-consuming. This Skill automates the collection of daily activity and ensures Plan/Docs across projects are consistently synchronized into a single, organized Vault view.

Core Features & Use Cases

  • Detects changes in a configured Projects folder and aggregates daily activity into a unified Obsidian daily progress log.
  • Synchronizes per-project Plan/Docs into the Vault while preserving Obsidian-style links to each project ([[ProjectName]]).
  • Respects ignore rules to skip system and noisy folders and preserves existing Vault entries, updating only new progress.

Quick Start

Configure origin and vault paths, then run the daily-progress workflow using /daily-progress:origin {path} and /daily-progress:vault {path}.

Frequently Asked Questions about daily-progress

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

FAQPage Schema
How do I automate daily project logs and sync them to an Obsidian vault?

Automate daily project logs by configuring origin and vault paths, then run the workflow to collect daily activity and synchronize Plan/Docs into the Obsidian vault. It aggregates changes from a Projects folder into a unified daily progress log while preserving Obsidian-style links.

Do I need a local configuration file to sync project docs into Obsidian?

Yes, you need a local configuration file at ~/.claude/daily-progress.json with origin and vault fields defined. This file specifies the source directories for your projects and the destination Obsidian vault for centralized progress logging.

Does the daily progress sync overwrite existing Obsidian vault entries?

No, the daily progress sync preserves existing Obsidian vault entries and only adds new progress records. It updates the vault by appending new activity logs and synchronizing project Plan/Docs without destructively modifying your current notes.

Can I exclude specific folders from the multi-project daily activity collection?

Yes, you can exclude specific folders from daily activity collection using ignore rules. The workflow respects these configurations to skip system and noisy directories, ensuring only relevant project changes are aggregated into the Obsidian vault.

What is the best way to maintain centralized review logs for multiple projects?

The best way to maintain centralized review logs is to automate collection from a configured origin directory into a single Obsidian vault. This approach synchronizes per-project Plan/Docs and aggregates daily activity into an organized view for consistent tracking.

How do I configure origin and vault paths for daily progress logging?

Configure origin and vault paths by running the workflow commands /daily-progress:origin {path} and /daily-progress:vault {path}. This sets the source project directories and the target Obsidian vault for automated daily progress synchronization.