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/SCRIPT-VS-AGENT.md

View on GitHub
# Script vs Agent Boundary

Use this guide to decide whether a task belongs in `project_kb.py` or must remain agent-driven.

## Good fit for the script

These tasks are low-freedom, deterministic, and should behave the same every time:

- detect whether a repo is bound to a project vault
- bootstrap the standard vault structure
- sync repo-driven state into daily, hub, plan, memory, and auto-sync notes
- list or suggest the canonical notes to read for a question shape
- archive, purge, or rename a single note with direct-link repair in explicit index notes
- maintain source inventory and codebase overview

Current script-facing commands:
- `detect`
- `bootstrap`
- `sync`
- `lifecycle`
- `query-context`
- `find-canonical-note`
- `note-lifecycle`

## Must stay with the agent

These tasks require semantic judgment and should not be hard-coded into the script:

- deciding whether a new Markdown file is durable knowledge or raw material
- deciding whether to promote, merge, or stage a new Markdown file
- deciding which existing note is the canonical note when multiple semantic candidates exist
- synthesizing background from many project documents
- interpreting experimental meaning or result significance
- deciding whether a note should be split or merged based on conceptual overlap
- deciding whether a result is stable enough for `Results/`

## Practical rule

If the task can be framed as:

- “find”, “move”, “rename”, “archive”, “sync”, or “suggest reads”

it is probably script-suitable.

If the task can be framed as:

- “understand”, “interpret”, “decide meaning”, “summarize”, “merge concepts”, or “promote to durable knowledge”

it should remain agent-driven.
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: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated 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: 323kUpdated Claude CodeCodexVerifiedInstall