brycewang-stanford/Auto-Empirical-Research-Skills / skills/33-Galaxy-Dawn-claude-scholar/skills/obsidian-project-memory
obsidian-project-memory
VerifiedThis skill should be used when the user asks to maintain an Obsidian knowledge base for a research project, import an existing research repository into Obsidian, keep project memory or daily notes synchronized, summarize project context into durable notes, or update experiments, results, papers, writing, and plans in an Obsidian vault without requiring MCP.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.5 KB |
| references/AGENT-FIRST-IMPORT.md | markdown | 1.6 KB |
| references/KNOWLEDGE-CRUD.md | markdown | 3.8 KB |
| references/NEW-MD-INGESTION.md | markdown | 2.4 KB |
| references/NOTE-ROUTING.md | markdown | 4.4 KB |
| references/NOTE-TEMPLATES.md | markdown | 4.3 KB |
| references/PAPERS-TO-WRITING.md | markdown | 4.4 KB |
| references/SCHEMA.md | markdown | 2.0 KB |
| references/SCRIPT-VS-AGENT.md | markdown | 1.7 KB |
| references/WORKFLOW.md | markdown | 4.8 KB |
| scripts/project_kb.pyexecutable | script | 72.6 KB |
| scripts/project_views.pyexecutable | script | 7.3 KB |
references/NOTE-ROUTING.md
View on GitHub# Note Routing
## First decide: durable note or raw material
### Durable note
Treat content as a durable note when it is:
- likely to be referenced again after days or weeks,
- about a clearly bounded object,
- already stable enough to stand on its own,
- suitable to become the canonical note for that object.
### Raw material
Treat content as raw material when it is:
- a short-lived intermediate artifact,
- a draft, memo, scratch note, or meeting fragment,
- an unverified analysis dump,
- incomplete support for a note that already exists.
Default rule: **raw material should be summarized before promotion**.
## Route by knowledge type
### Knowledge
Write to `Knowledge/` when the content is stable and explanatory:
- project background
- research questions
- dataset protocol
- method landscape
- source inventory
- codebase overview
Do not put these here by default:
- temporary ideas,
- unverified hypotheses with no stable framing,
- daily execution logs.
### Papers
Write to `Papers/` when the content is primarily literature-facing:
- single paper notes
- related-work summaries
- paper-to-project relevance notes
- reading notes and literature synthesis
Do not put these here by default:
- project-only summaries with no literature object,
- raw meeting notes about papers,
- unrelated implementation notes.
### Experiments
Write to `Experiments/` when the content is about what was run or will be run:
- experiment design
- runbook
- ablation
- baseline comparison setup
- freezing / transfer / screening study
Do not put these here by default:
- raw metric dumps with no interpretation,
- broad project framing,
- final cross-experiment claims that belong in `Results/`.
### Results
Write to `Results/` when the content captures a durable finding:
- final comparison
- mechanism conclusion
- collapse diagnosis
- figure and csv index
- cross-experiment interpretation
- stable canonical claim that should survive beyond one report
Do not put these here by default:
- unprocessed analysis output,
- notes that merely restate the experiment setup,
- temporary result speculation that still belongs in `Daily/`.
### Results Reports
Write to `Results/Reports/` when the content is a **complete internal experiment summary report**:
- one experiment round retrospective,
- one batch report for a coherent experiment line,
- one decision-oriented wrap-up note backed by analysis artifacts.
These notes should use the naming contract:
- `YYYY-MM-DD--{experiment-line}--r{round}--{purpose}.md`
Do not put these here by default:
- manuscript-facing draft text,
- raw metric dumps,
- vague summaries without one date / line / round / purpose.
### Writing
Write to `Writing/` when the content is meant for external output:
- paper draft fragments
- slide narrative
- rebuttal notes
- proposal text
Internal experiment reports do **not** belong here unless they are already external-facing writing artifacts.
### Daily
Write to `Daily/` when the content is transient or process-oriented:
- what happened today
- short sync queue
- quick scratch ideas
- temporary planning fragments
- lightweight meeting notes
Do not let `Daily/` become the long-term home for canonical project knowledge. Promote durable content later.
## Main routing rule
If a note will still matter after several days or weeks, prefer `Knowledge/`, `Experiments/`, `Results/`, `Results/Reports/`, `Papers/`, or `Writing/`.
If the note is mainly about today's progress or temporary organization, prefer `Daily/`.
## Cross-folder promotion defaults
Treat these folders as a research pipeline, not as independent buckets:
- `Papers/` should usually answer: what should we test, compare, or borrow?
- `Experiments/` should usually answer: what exactly are we running, and what finding would matter?
- `Results/` should usually answer: what do we now believe, with evidence?
- `Results/Reports/` should usually answer: what happened in this round or batch, and what decision does it imply?
- `Writing/` should usually answer: what should be said externally because of those results?
Default promotion path:
- paper insight -> experiment note
- stable experiment finding -> result note
- coherent round/batch retrospective -> results report note
- durable result claim -> writing note
If a turn reaches only one stage, keep it there. But when the next stage is already clear, prefer updating the next canonical note instead of leaving the chain broken.
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 |