obsidian-todo-collector

Name: obsidian-todo-collector
Availability: InStock
Author: cafe3310

Extract unfinished tasks from Obsidian notes into a centralized tracking summary.

248|30|Updated Feb 18, 2026

Search Tags:#task management #workflow automation #knowledge management #obsidian #todo extraction #note processing

Ready to run

npx skills add https://github.com/cafe3310/public-agent-skills --skill obsidian-todo-collector

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: obsidian-todo-collector
Source: https://github.com/cafe3310/public-agent-skills/tree/main/skills_parked/obsidian-todo-collector
Command: npx skills add https://github.com/cafe3310/public-agent-skills --skill obsidian-todo-collector

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill solves the problem of manually searching through large Obsidian knowledge bases to find unfinished tasks and planning items by automatically collecting them into a centralized tracking document.

Core Features & Use Cases

Obsidian Task Scanning: Scans dated Obsidian notes within a specified time range and identifies unfinished events, work items, and planning tasks.
Incremental Progress Tracking: Creates and updates an unfinished events summary document with source links, processing status, and completion states.
Use Case: When a knowledge base contains daily logs and project notes with scattered pending items, use this Skill to build a consolidated follow-up list for ongoing management.

Quick Start

Use the obsidian-todo-collector skill to organize unfinished tasks from my Obsidian notes between the specified start date and end date.

Frequently Asked Questions about obsidian-todo-collector

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

FAQPage Schema

How do I extract unfinished tasks from Obsidian notes into a centralized summary?▼

To extract unfinished tasks from Obsidian notes, this Skill scans dated documents within a specified time range, identifies pending events and planning items, and compiles them into a centralized tracking summary with source links and completion states.

Can I track incremental progress of pending planning items across daily Obsidian logs?▼

Yes, you can track incremental progress of pending planning items by continuously updating the centralized summary document, which preserves source references and processing statuses for ongoing task follow-up across daily logs.

Does this task scanning tool require python3 to process my Obsidian knowledge base?▼

Yes, this task scanning tool requires python3 installed in your environment to perform document pre-checking and extract unfinished tasks from your Obsidian knowledge base documents.

What is the best way to consolidate scattered pending work items from project logs?▼

The best way to consolidate scattered pending work items is to automate extraction across project logs and dated notes, generating a consolidated follow-up list that includes source links and processing status for management.

How does incremental task extraction handle previously processed notes?▼

Incremental task extraction handles previously processed notes by updating the existing unfinished events summary, tracking processing status and completion states to avoid duplicating already managed items while adding newly identified pending tasks.

Are there limitations when scanning large Obsidian knowledge bases for unfinished events?▼

A limitation when scanning large Obsidian knowledge bases is that the extraction requires specifying a defined start and end date range to query notes, meaning un-dated documents or items outside the range will not be collected.