Obsidian research log
Use this skill when the user is discussing daily research work, TODOs, plans, standups, meetings, milestones, or general project progress that should be reflected in Obsidian daily notes, plan notes, and hub updates.From its SKILL.md
npx -y skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill obsidian-research-logAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
SKILL.md
1.5 KB, 277 tokens by cl100k_base, as published. Nobody here has run it
Obsidian 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/.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.