obsidian-project-kb-core — Claude Code skill
This skill manages a project-scoped Obsidian research vault: it builds the structure, routes notes, and keeps indexes, the registry, and checks up to date.
npx skills add Galaxy-Dawn/claude-scholar --skill obsidian-project-kb-core -a claude-codeWhat obsidian-project-kb-core does
The skill binds the current repository to Research/{project-slug}/ and bootstraps a project vault with 00-Hub.md, 01-Plan.md, 02-Index.md, plus Sources/, Knowledge/, Experiments/, Results/Reports/, Writing/, Daily/, Maps/, Archive/, and _system/. Notes are routed into these areas, while durable project knowledge stays under the project root.
It maintains the hub, plan, index, and _system/registry.md. It also handles note lifecycle actions such as creating, updating, renaming, archiving, purging, promoting, and repairing links. Scripts in scripts/ cover scaffolding, registry consistency, link checks, index checks, canvas checks, and lint aggregation. Agents handle note routing and semantic decisions for daily entries, sources, and stable results.
The repository must bind to the project root because .claude/project-memory/* is used only as the runtime binding layer. Check where the working notes live before running the skill.
What it helps with
- bootstrap an Obsidian research project
- route notes into the project sections
- maintain the hub, plan, and index
- keep the note registry consistent
- run link and structure checks
Example prompts for the agent
- Bind the current repository to
Research/{project-slug}/and bootstrap the project skeleton. - Route these notes into
Sources/,Knowledge/,Experiments/, andWriting/, then update02-Index.md. - Run the registry, link, index, and canvas checks from
scripts/, then aggregate the lint report.
How to install obsidian-project-kb-core
1Skills CLI (Vercel)
npx skills add Galaxy-Dawn/claude-scholar --skill obsidian-project-kb-core -a claude-code2Manually: put the files in place
~/.claude/skills/obsidian-project-kb-core/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/obsidian-project-kb-core/
1Skills CLI (Vercel)
npx skills add Galaxy-Dawn/claude-scholar --skill obsidian-project-kb-core -a codex2Manually: put the files in place
.agents/skills/obsidian-project-kb-core/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Galaxy-Dawn/claude-scholar --skill obsidian-project-kb-core -a cursor2Manually: put the files in place
.cursor/skills/obsidian-project-kb-core/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Galaxy-Dawn/claude-scholar obsidian-project-kb-core2Manually: put the files in place
.github/skills/obsidian-project-kb-core/SKILL.md1Skills CLI (Vercel)
npx skills add Galaxy-Dawn/claude-scholar --skill obsidian-project-kb-core -a gemini-cli2Platform CLI
gemini skills install https://github.com/Galaxy-Dawn/claude-scholar --path skills/obsidian-project-kb-coreManually: put the files in place
.devin/skills/obsidian-project-kb-core/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Galaxy-Dawn/claude-scholar --skill obsidian-project-kb-core -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about obsidian-project-kb-core
How do I install obsidian-project-kb-core in Claude Code?
Run npx skills add Galaxy-Dawn/claude-scholar --skill obsidian-project-kb-core -a claude-code, then run npx skills add Galaxy-Dawn/claude-scholar --skill obsidian-project-kb-core -a claude-code again. Use the resulting skill file at ~/.claude/skills/obsidian-project-kb-core/SKILL.md.
What does obsidian-project-kb-core do?
It creates and maintains a project-scoped Obsidian knowledge base under Research/{project-slug}/. The skill routes notes, updates the hub, plan, index, and registry, and runs structural checks.
Where does the project's durable knowledge live?
It lives inside the current Research/{project-slug}/ root. .claude/project-memory/* is reserved for the repository's runtime binding layer.
Source text
SKILL.md · MIT
---
name: obsidian-project-kb-core
description: Use this as the main Claude Scholar skill for a vault-first, project-scoped Obsidian research knowledge base rooted at Research/{project-slug}/. It owns bootstrap, routing, daily logging, hub/plan/index maintenance, registry updates, lifecycle actions, and lint orchestration.
---
# Obsidian Project KB Core
This is the **main workflow authority** for project-scoped Obsidian knowledge maintenance.
Default project root:
```text
Research/{project-slug}/
```
Default structure:
```text
00-Hub.md
01-Plan.md
02-Index.md
Sources/
Knowledge/
Experiments/
Results/
Reports/
Writing/
Daily/
Maps/
Archive/
_system/
```
## Core rules
- Keep all durable project knowledge inside the current `Research/{project-slug}/`.
- Keep repo-local `.claude/project-memory/*` only as the runtime binding layer.
- `_system/registry.md` is the only visible project registry.
- `02-Index.md` is a human navigation note, not a registry mirror.
- `Maps/` is a derived-artifact area; do not generate non-essential canvases by default.
- `Results/Reports/` is the default subdirectory for round and batch experiment reports.
## Responsibilities
- detect and bind the current repo to a project root
- bootstrap the project skeleton
- route notes into `Sources / Knowledge / Experiments / Results / Results/Reports / Writing / Daily / Maps / Archive`
- update `00-Hub.md`, `01-Plan.md`, `02-Index.md`
- update `_system/registry.md`, `_system/schema.md`, `_system/lint-report.md`
- handle note lifecycle actions: create, update, rename, archive, purge, promote, and link repair
- run deterministic health checks through helper scripts
## Deterministic helpers
Use the scripts under `scripts/` for:
- scaffold
- registry consistency
- link checks
- index checks
- canvas checks
- lint aggregation
Use agents for:
- note routing
- daily promotion decisions
- source vs knowledge judgment
- stable-result judgment
- semantic Hub and Index updates
## Read next
- `references/DIRECTORY-SCHEMA.md`
- `references/HUB-PLAN-INDEX.md`
- `references/REGISTRY.md`
- `references/DAILY-PROMOTION.md`
- `references/LIFECYCLE.md`
- `references/LINT.md`
- `references/BINDING-LAYER.md`
© Galaxy-Dawn · MIT · Galaxy-Dawn/claude-scholar
