brycewang-stanford/Auto-Empirical-Research-Skills / skills/33-Galaxy-Dawn-claude-scholar/skills/obsidian-research-log
obsidian-research-log
VerifiedUse 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.
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/.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Unverified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |