Skip to content

brycewang-stanford/Auto-Empirical-Research-Skills / skills/33-Galaxy-Dawn-claude-scholar/skills/obsidian-project-memory

obsidian-project-memory

Verified

This 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.

references/SCHEMA.md

View on GitHub
# Obsidian Project Knowledge Base Schema

## Repository-local memory files

- `.claude/project-memory/registry.yaml` — registry keyed by `project_id`
- `.claude/project-memory/<project_id>.md` — compact project memory snapshot used on project turns

Note: `registry.yaml` is currently JSON-formatted on disk for historical compatibility.

Optional per-project registry fields:
- `note_language` — note language for generated/synced notes. Supported values: `en`, `zh-CN`.

Language resolution priority:
1. project config in `.claude/project-memory/registry.yaml`
2. environment variable `OBSIDIAN_NOTE_LANGUAGE`
3. default `en`

## Vault layout

```text
Research/{project-slug}/
  00-Hub.md
  01-Plan.md
  Knowledge/
  Papers/
  Experiments/
  Results/
    Reports/
  Writing/
  Daily/
  Archive/
```

## Role of each top-level location

- `00-Hub.md` — project homepage, current state, must-remember numbers, key links
- `01-Plan.md` — active goals, tasks, open questions, next actions
- `Knowledge/` — stable project understanding such as background, research questions, method survey, data protocol, source inventory
- `Papers/` — paper notes, literature summaries, related-work assets
- `Experiments/` — experiment designs, runbooks, ablations, mechanism studies
- `Results/` — canonical durable findings, diagnostics, figure/table indexes, cross-experiment conclusions
- `Results/Reports/` — internal experiment round reports and batch retrospectives with stable naming
- `Writing/` — paper drafting, slides, proposal text, rebuttal material
- `Daily/` — daily logs, lightweight sync queue, scratch notes, meeting fragments
- `Archive/` — inactive or historical material that should not stay in the main working surface

## Minimum note types

- `project`
- `daily`
- `paper`
- `experiment`
- `result`
- `results-report`
- `synthesis`
- `meta`
- `writing`
- `task`

## Main design rule

This schema is intentionally small. Prefer a few durable notes over many placeholder notes.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall