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/NEW-MD-INGESTION.md
View on GitHub# New Markdown Ingestion
Use this guide when a new Markdown file appears and should be considered for the knowledge base.
## Three-step decision
### 1. Classify
Classify the file as one of:
- `knowledge`
- `paper`
- `experiment`
- `result`
- `writing`
- `daily`
### 2. Decide: durable note or raw material
Treat it as a **durable note** only if it is already:
- complete enough to stand on its own,
- stable in scope,
- likely to be referenced later.
Otherwise treat it as **raw material**.
### 3. Choose the action
Choose one of these:
- **promote**
- use only when the file is already a stable, complete, long-lived note
- **merge**
- use when it supplements an existing canonical note for the same object
- **stage-to-daily**
- use when it is still unstable, incomplete, or not worth promoting yet
Default answer: **summarize first, then route**.
## Examples
### New paper summary
- likely classification: `paper`
- if complete and stable -> promote to `Papers/`
- if partial reading notes for an existing paper note -> merge
### New experiment plan
- likely classification: `experiment`
- if it defines a distinct experiment line -> promote to `Experiments/`
- if it refines an existing experiment -> merge into that note
### New result memo
- likely classification: `result`
- if it contains a durable conclusion with evidence -> promote to `Results/`
- if it is a full internal experiment summary report -> promote to `Results/Reports/` using the stable naming contract
- if it is still exploratory -> stage in `Daily/` or merge into the existing experiment note first
### New meeting note
- likely classification: `daily`
- default -> stage in `Daily/`
- promote only if the meeting produced a stable decision that belongs in `Knowledge/`, `Experiments/`, or `Writing/`
### New scratch idea
- likely classification: `daily` or `knowledge`
- default -> stage in `Daily/`
- promote later only if it becomes a stable research question, method direction, or experiment plan
### Cross-stage routing hint
When a new file is about papers, experiments, results, or writing, do not stop at file classification alone. Also ask whether it clearly implies the next durable handoff:
- paper note -> should an experiment note be updated?
- experiment note -> is there already a stable finding that belongs in `Results/`?
- result memo -> does a writing note need an update?
If that next handoff is already clear, prefer updating the downstream canonical note in the same turn.
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 | Verified | 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: 323k | 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: 323k | 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: 323k | Updated | Claude CodeCodex | Verified | Install |