About obsidian-research-log
A supporting skill for Obsidian project workflows that keeps planning and daily progress aligned. It helps turn commitments into durable notes while preserving chronology and avoiding duplicate planning pages.
Key features
- 01Synchronizes plans and daily logs
- 02Turns TODOs into checklists
- 03Preserves dated log entries
- 04Links notes to canonical pages
- 05Routes durable meeting knowledge
Use cases
- 01Recording dated project progress
- 02Turning commitments into plan checklists
- 03Linking daily work to research notes
- 04Moving lasting meeting outcomes into project knowledge
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/obsidian-research-login Claude Code to confirm it loaded.
Details
From the project READMEObsidian Research Log
Use this skill to keep project planning and daily progress synchronized.
Role in the workflow
This is a supporting skill under obsidian-project-memory.
Prefer a small number of durable updates over creating extra planning folders.
Default targets
Daily/YYYY-MM-DD.md01-Plan.md00-Hub.mdrecent progress block.claude/project-memory/<project_id>.md
Rules
- Convert vague TODOs into concrete checkbox lists in
01-Plan.mdwhen they become durable commitments. - Preserve chronology in
Daily/: append dated blocks instead of rewriting history. - Link daily notes to touched experiments, papers, results, and writing notes when the destination is already canonical.
- If a meeting note is only temporary, keep it in
Daily/first. - If meeting output becomes durable project knowledge, summarize and route it into
Knowledge/,Writing/, or01-Plan.mdinstead of creating a defaultMeetings/folder. - Prefer updating existing canonical notes over spawning parallel task notes.
Main judgment rule
Daily logs are for process.
If a note will still matter after several days or weeks, promote the durable part into Knowledge/, Experiments/, Results/, or Writing/.
Comments
Markdown supported