Skill

obsidian-project-kb-core

Manages project-scoped Obsidian knowledge bases: bootstraps structure, routes notes to folders, maintains hub/plan/index/registry, handles lifecycles, runs lints and checks.

Markdown

documentation

developer-tools

npx claudepluginhub galaxy-dawn/claude-scholar --plugin claude-scholar

Tool Access

This skill uses the workspace's default tool permissions.

Preview

This is the **main workflow authority** for project-scoped Obsidian knowledge maintenance.

Supporting Assets

references/BINDING-LAYER.mdreferences/DAILY-PROMOTION.mdreferences/DIRECTORY-SCHEMA.mdreferences/HUB-PLAN-INDEX.mdreferences/LIFECYCLE.mdreferences/LINT.mdreferences/REGISTRY.mdscripts/kb_canvas_check.pyscripts/kb_common.pyscripts/kb_index_check.pyscripts/kb_link_check.pyscripts/kb_lint.pyscripts/kb_registry_check.pyscripts/kb_scaffold.pyscripts/project_kb.py

SKILL.md

Similar Skills

obsidian

Integrates Claude with Obsidian vaults for note creation, task management, knowledge organization, and project docs using CLI (1.12+), MOCs, properties.

7 files

delphine-l-claude-global

obsidian-vault-manager

Manages Obsidian vault structure by organizing documents into service and work-log layers, adding files with auto-categorization and metadata, processing meeting notes, running health checks, and committing via Git.

5 tools

oh-my-obsidian

wiki

3.2k

Sets up persistent Obsidian wiki vault from one-sentence description, scaffolds structure, maintains cross-references, and manages hot cache for knowledge compounding.

7 files1 tool

claude-obsidian

Stats

Stars3472

Forks320

Last CommitApr 24, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Obsidian Project KB Core

This is the main workflow authority for project-scoped Obsidian knowledge maintenance.

Default project root:

Research/{project-slug}/

Default structure:

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