obsidian-research-log

Synchronizes daily research progress, TODOs, and meeting notes into Obsidian daily notes and plan files.

Updated Oct 7, 2022
One-click install
npx skills add https://github.com/tamagusko/linux-cfg --skill obsidian-research-log-tamagusko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-research-log
Source: https://github.com/tamagusko/linux-cfg/tree/main/dotfiles/claude/skills/obsidian-research-log
Command: npx skills add https://github.com/tamagusko/linux-cfg --skill obsidian-research-log-tamagusko

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research progress scattered across conversations, TODOs, and meeting notes gets lost unless it is consistently written into a durable note system. This Skill keeps Obsidian daily notes, plan notes, and hub pages synchronized with actual project work. ## Core Features & Use Cases - Daily note logging: Appends dated progress blocks to Daily/YYYY-MM-DD.md while preserving chronology instead of rewriting history. - Plan maintenance: Converts vague TODOs into concrete checkbox lists in 01-Plan.md and updates the recent progress block in 00-Hub.md. - Knowledge promotion: Routes durable meeting outcomes and findings into Knowledge/, Experiments/, Results/, or Writing/ notes instead of creating parallel folders. - Use Case: After a research standup, ask the assistant to log the discussion: it appends a dated entry to today's daily note, turns agreed action items into checkboxes in the plan, and links to the touched experiment notes. ## Quick Start Log today's research progress and meeting outcomes into my Obsidian daily note and update the project plan checkboxes.

Frequently Asked Questions about obsidian-research-log

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

FAQPage Schema
How do I keep Obsidian daily notes updated with research progress?

Append dated blocks to Daily/YYYY-MM-DD.md for each work session rather than rewriting past entries. Link each daily entry to the experiments, papers, results, or writing notes it touched so chronology and context stay connected.

How to convert meeting notes into project tasks in Obsidian?

Keep temporary meeting notes in the daily note first, then turn durable commitments into concrete checkbox items in 01-Plan.md. Summarize lasting decisions into Knowledge/, Writing/, or the plan instead of creating a separate Meetings folder.

When should a daily note entry be moved to a permanent note?

Promote content when it will still matter after several days or weeks. Daily logs capture process, while durable findings belong in Knowledge/, Experiments/, Results/, or Writing/ notes that serve as canonical references.

Does this skill work with other Obsidian project management setups?

It is designed as a supporting skill under obsidian-project-memory and writes to .claude/project-memory files alongside the vault notes. It assumes a vault structure with Daily/, 01-Plan.md, and 00-Hub.md but avoids imposing extra folder hierarchies.

What are the limitations of daily-note-based research logging?

Daily notes alone fragment durable knowledge across dates, making it hard to find later. The skill mitigates this by promoting lasting content into canonical notes, but it depends on consistent judgment about what is temporary versus durable.