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.
Profile →npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill obsidian-research-log --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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.md` - `01-Plan.md` - `00-Hub.md` recent progress block - `.claude/project-memory/<project_id>.md`
What does the obsidian-research-log skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill obsidian-research-log --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Auto-Empirical-Research-Skills, a repository with 3,244 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.