How do I install the Obsidian Project Kb Core skill?

Run npx skillmds@latest add gabrielmoreira/obsidian-project-kb-core in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Obsidian Project Kb Core safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Obsidian Project Kb Core?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Obsidian Project Kb Core free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Obsidian Project Kb Core?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Obsidian Project Kb Core by gabrielmoreira

Name: Obsidian Project Kb Core
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

Obsidian Project Kb Core

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.

gabrielmoreira Updated Sep 9, 2026 17 repo stars

File contents

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

---name: obsidian-project-kb-coredescription: 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`

Frequently asked questions